2026-09-19 · 6 min read · Rahul Chitturi
- http
- performance
- preload
A server can send 103 Early Hints with Link fields while it prepares the final response. A supporting client may start connecting or preloading resources sooner, but the 103 is interim metadata rather than the page's final status and headers.
Performance regressions appear when the hinted URL, resource type, credentials mode, or final HTML differs from the actual dependency. Unsupported intermediaries may suppress the hint, while a badly behaved client or application can mistake it for completion.
Trace interim and final messages separately
Capture when the origin emits 103, what each proxy forwards, when hinted fetches begin, and when the final response arrives. The client must continue waiting after 103 and handle a final redirect or error normally.
- Limit hints to resources likely needed by the final representation.
- Keep preload as-values and cross-origin settings accurate.
- Use absolute trust rules for every hinted authority.
- Do not place cookies or sensitive data in hinted URLs.
Avoid duplicate and wasted downloads
The Link hint and the eventual HTML reference must identify a compatible fetch. Differences in URL spelling, content negotiation, integrity metadata, credentials mode, or resource type can prevent reuse and cause a second download.
Hints are optional optimization. Correctness cannot depend on them, and a final response that changes its decision should remain valid even if the client already started a speculative fetch.
Measure the production path
Use Flashman's URL tool for hinted targets, timestamp converter for response and fetch timelines, diff for interim versus final Link fields, and hash for public asset integrity fixtures.
Test supported and unsupported clients, direct origin and every proxy, final 200 and error responses, redirects, cross-origin assets, CSP, preload reuse, cache hits, negotiated variants, duplicate hints, connection failure, and measured page impact.