Shipping daily
Changelog →

Kolaboro / Engineering / Early Hints and priority hints

Early Hints and priority hints

How pages tell the browser about critical files before the HTML is ready (103 Early Hints from Link headers) and which element to paint first (fetchpriority), with LCP measured before and after on five templates.

Updated 19 Nov 2026

Every HTML page now sends a Link header that preloads the site stylesheets and the main font. Cloudflare turns Link preload headers into a 103 Early Hints response that browsers can act on while the worker is still building the page.

fetchpriority: Lighthouse names the largest element of each template below. On all five it is text (a heading or the lead paragraph) painted at the first contentful paint, so no image needs a higher priority there; images below the first screen keep loading="lazy".

Link: </k/site.css?v=3a6e94c8e7>; rel=preload; as=style, </k/ds-site.css?v=dd003cfe8e>; rel=preload; as=style, </k/fonts/archivo-latin.woff2>; rel=preload; as=font; type="font/woff2"; crossorigin

Measured

TemplateLCP beforeLCP afterChangeRunsLCP element
Home1,393 ms1,316 ms-77 ms6= FCP (6/6)
Project page1,404 ms1,182 ms-222 ms6= FCP (5/6)
Market page1,416 ms1,276 ms-140 ms6= FCP (5/6)
Project list1,614 ms1,564 ms-50 ms6= FCP (6/6)
Developer page1,402 ms1,252 ms-150 ms6= FCP (6/6)

Lighthouse 13.6.0, mobile, median of the runs, live site, 19 Nov 2026. Lab numbers move by 100 to 300 ms between runs.

A 103 Early Hints response was observed from Cloudflare for these pages after the change.

Limits

Early Hints are sent only when Cloudflare has the feature on for the zone and the browser supports them (Chrome and Edge do; Safari and Firefox ignore them). Lighthouse runs on a simulated slow phone, so the difference in a real browser on a fast connection is smaller.

Other changes went live between the two measurements, so the difference is not caused by Early Hints alone.

More engineering

Protect my purchase