Streaming and Incremental Rendering
You'll learn how async Server Components enable React to send HTML to the browser progressively, rather than waiting for everything to finish.
The Core Idea
Traditional server-side rendering blocks: the server waits until every component has finished rendering, then sends the entire HTML document at once. With async Server Components, React can stream the response—sending early parts of the page immediately while slower components are still fetching data.
Think of it like a restaurant: instead of waiting until all dishes are ready before bringing out any food, the server brings appetizers first, then mains, then dessert as each becomes ready. Users see content faster, even if some parts are still loading.
How It Works
When you mark components as async and use await for data fetching, React can:
- Start streaming HTML immediately for components that resolve quickly
- Send placeholders (from Suspense boundaries) for slower components
- Incrementally inject the finished HTML for each async component as it resolves
- Hydrate progressively on the client
The browser receives and displays partial content while the server is still working on other parts. This dramatically improves Time to First Byte and Largest Contentful Paint.
The Stream vs The Block
Without streaming: Server waits 3 seconds → sends all HTML → user sees page.
With streaming: Server sends layout at 0.1s → user sees structure → sends product list at 0.5s → sends reviews at 3s → complete.
Users perceive the page as much faster because they see something almost instantly.
Key Takeaway: Async Server Components unlock streaming SSR, allowing HTML to flow to the client incrementally as each component's data resolves, rather than blocking until everything is ready.