103 Early Hints
103 Early Hints is an interim HTTP status sent before 200 OK while the origin server is still querying databases or rendering SSR HTML. It carries Link: rel=preload and rel=preconnect headers so the browser fetches critical CSS and fonts during server think time.
103 Early Hints: Overlapping Server Think Time
Observe how an interim 103 frame starts CSS and font fetches before the 200 OK HTML arrives.
Client requests /dashboard. The origin needs 350ms to query the database and render SSR HTML.
GET /dashboard HTTP/2- serverThinkTimeMs
- 350
- htmlBytesReceived
- 0
- clientIdle
- true
Under the Hood
Without Early Hints, a 400 ms SSR database query leaves the client's network card sitting idle, waiting for byte zero of HTML so the Preload Scanner can discover <link rel="stylesheet">. 103 acts like a restaurant handing you the breadbasket while the kitchen still cooks your entrée.
- The browser sends a navigation
GETover HTTP/2 & HTTP/3. - The CDN edge immediately flushes a
103 Early Hintsframe containingLinkheaders for critical CSS, fonts, or API origins. - The browser's speculative fetcher opens TLS connections and downloads those assets in parallel with origin SSR execution.
- When
200 OKHTML finally arrives, render-blocking stylesheets are already sitting in the memory cache.
HTTP/2 103 Early Hints
Link: </assets/critical.css>; rel=preload; as=style
Link: </assets/inter.woff2>; rel=preload; as=font; crossorigin
Link: <https://api.example.com>; rel=preconnectProblem Genealogy
- 2015 (HTTP/2 Server Push): Attempted to push unsolicited bytes down the pipe, but broke browser caches when clients already held the asset; eventually removed from Chromium.
- 2017 (RFC 8297
103 Early Hints): Replaced blind pushing with a politeLinkhint, letting the client skip assets it already cached. - 2022–2025 (Multi-Engine Rollout): Chrome, Firefox, and Safari converged on
103over HTTP/2 and HTTP/3.
Production Pitfalls
- Mismatched
crossoriginon fonts: Omittingcrossoriginin the103Linkheader causes the browser to fetch the font twice, once anonymously in103, once with CORS in CSS. - Over-hinting non-critical scripts: Pushing 12 low-priority chunks in
103saturates the initial TCP/QUIC congestion window and delays the200 OKHTML itself.
- When not to use
103: On static pages served from CDN edge cache in under 20 ms,103adds an extra header frame with near-zero overlap benefit.
Connections & Logical Next Steps
103 Early Hints feed the same speculative preload queue before the HTML parser even starts.
Browsers only honor 103 informational responses over HTTP/2 or HTTP/3.
103 sends Link headers before 200 OK; Streaming SSR flushes actual 200 OK HTML bytes early.