Streaming SSR & Progressive Flushing vs 103 Early Hints
103 sends Link headers before 200 OK; Streaming SSR flushes actual 200 OK HTML bytes early.
Structured Comparison Matrix
| Dimension | Streaming SSR & Progressive Flushing | 103 Early Hints |
|---|---|---|
| Mental Model | Streams the HTML <head> and shell immediately over HTTP/2+ while slow backend queries run, then flushes deferred <template> chunks for out-of-order DOM replacement. | Sends an interim HTTP 103 frame with Link preload headers while the server is still rendering HTML, overlapping subresource fetches with origin think time. |
| Maturity & Domain | Baseline · Widely · Network & Performance Chrome 43+ · Firefox 65+ · Safari 10.1+ | Baseline · Newly · Network & Performance Chrome 103+ · Firefox 120+ · Safari 18.2+ |
| Prerequisites | ||
| When Not to Use | When not to use Streaming SSR: On static or edge-cached pages that render in under 15 ms, full-response caching with s-maxage is simpler and avoids open long-lived connections; if client hydration cost dominates, compare against Resumability vs Hydration. | When not to use 103: On static pages served from CDN edge cache in under 20 ms, 103 adds an extra header frame with near-zero overlap benefit. |
Engine Mechanics & Trade-Offs
Flushes the HTML <head> and shell immediately over HTTP/2+ while slow data queries resolve, then streams deferred <template> chunks + inline swap scripts.
Key Pitfalls: Proxy buffering eating your stream: Reverse proxies (Nginx, misconfigured CDNs, or synchronous compression) often buffer the first 4–64 KB before forwarding, defeating Streams API Backpressure and turning streaming back into buffered SSR. Locked HTTP 200 status codes: Once the <head> flushes, you cannot retroactively s
Emits an interim 103 HTTP frame with Link preload/preconnect headers during server think time, feeding the preload scanner before byte 0 of HTML arrives.
Key Pitfalls: Mismatched crossorigin on fonts: Omitting crossorigin in the 103 Link header causes the browser to fetch the font twice, once anonymously in 103, once with CORS in CSS. Over-hinting non-critical scripts: Pushing 12 low-priority chunks in 103 saturates the initial TCP/QUIC congestion window and delays the 200 OK HTML it