1
At a glance the headline numbers for Preloaded fonts
How many fonts the page preloads.
0
on the typical site
half of sites sit at or below
0
1 in 4 sites exceed this
the top quarter
7
the heaviest 1%
the long tail
180,899
sites measured
all-device field data
The typical site preloads 0 fonts.
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
2
Distribution & median INP site count and median INP at each level of preloaded fonts
0ms 63ms 125ms 188ms 250ms
200ms
0 78408 156815
0–0 1+
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
3
Passing INP by preloaded fonts which level passes the INP most often
Preloaded fontsSitesPassing INPINP
0–0 156,815 85ms
1+ 24,084 95ms
Good Needs Improvement Poor Faded rows: under 100 sites
Preloaded fonts 0. p75 0. p99 7. At the low end (0–0): INP 85ms. At the high end (1+): INP 95ms. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
4
Why this matters for the Core Web Vitals, and where to start fixing it
Fonts are discovered late by design. The browser must download the CSS, parse it, and find rendered text that actually uses an @font-face before it requests the font file. A preload skips that whole chain and starts the download with the HTML.
Preload the one or two fonts that render above-the-fold text, and stop there. Every preloaded font competes with the LCP image for early bandwidth. A preloaded font that is not used above the fold made the page slower for nothing.
Related signals Page weight & requests → Responsive image markup → Image loading attribute → Media source → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.