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

Why does a lazy-loaded feature need a loading state?

Short interview answer

Fetching the chunk takes real time on a real network, and without a fallback the user sees nothing, or a broken interaction, during that gap — the loading state communicates that something is happening rather than looking frozen.

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