Skip to content
Performance·Intermediate·Conceptual·1 min read

What's the downside of splitting too aggressively?

Short interview answer

Each split point becomes a separate network request. Splitting many small pieces can add more request and coordination overhead than it saves in bundle size, especially for code that's needed almost immediately anyway.

Key takeaway

Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.

← Back to Code splitting and lazy loading

Related questions