Course contentsShow
← React
Lesson 1378 of 2,39634. Suspense FundamentalsFree lesson

Granularity Tradeoff: Too Coarse

How wrapping the entire app in one Suspense causes everything to wait for the slowest component.

Granularity Tradeoff: Too Coarse

You'll learn why wrapping your entire app in a single Suspense boundary creates a poor loading experience.

The All-or-Nothing Problem

When you place one Suspense boundary around your entire application, every suspending component forces the entire UI to disappear and show the fallback. It doesn't matter if only a small widget is loading data—your whole app vanishes behind a spinner.

This is the "too coarse" granularity problem: the boundary is too big, encompassing too much UI that doesn't need to wait.

Why This Feels Bad

Imagine a restaurant where the kitchen won't serve anyone's meal until every single order is ready. If one table ordered a well-done steak, everyone waits—even those who ordered quick salads. That's what a single app-level Suspense boundary does.

<Suspense fallback={<AppSpinner />}>
  <Header />           {/* Ready instantly */}
  <Sidebar />          {/* Ready instantly */}
  <FastWidget />       {/* Ready instantly */}
  <SlowDataPanel />    {/* Takes 3 seconds */}
  <Footer />           {/* Ready instantly */}
</Suspense>

Even though only SlowDataPanel is loading, the entire app shows <AppSpinner /> and hides Header, Sidebar, FastWidget, and Footer. Everything waits for the slowest component.

The User Experience Cost

Users lose context. Navigation disappears. Fast-loading content doesn't appear even though it's ready. The perceived performance is far worse than it needs to be.

Key Takeaway: A single Suspense boundary around your entire app forces everything to wait for the slowest component, creating an unnecessarily jarring and slow experience.