Streaming server-side rendering sends HTML in chunks as page sections become ready, allowing the browser to display available content without waiting for the slowest data source. section 5.2.1
Streaming SSR addresses the blocking behavior of all-at-once rendering:
- Traditional SSR waits for every data request and the complete HTML response. section 5.2.1
- Streaming sends ready sections immediately, reducing the delay before visible content appears. section 5.2.1
- Streaming SSR addresses server blocking, while Islands architecture addresses client-side hydration blocking. section 5.2.1
Product page with inventory and reviews
A product page can display available content while inventory and reviews arrive separately instead of waiting for both services. Equivalent pages measured with Nordnet showed 32% lower Time to First Byte and 40% better Total Blocking Time. section 5.2.1
Table 5.1 Web rendering approaches
|
Rendering approach
|
Category
|
Waits for
|
Trade-offs
|
|
Server-Side Rendering
|
All-at-once
|
All data before sending HTML
|
Response blocked by server’s slowest data source
|
|
Client-Side Rendering
|
All-at-once
|
All JavaScript before rendering
|
User sees blank screen or loading indicator
|
|
Streaming SSR
|
Progressive
|
Nothing; sends chunks as ready
|
Added complexity
|
|
Islands
|
Progressive
|
Nothing; hydrates components independently
|
Architectural constraints
|
Compare Streaming SSR with all-at-once server-side rendering, client-side rendering, and Islands architecture. section 5.2.1
























