1
At a glance the headline numbers for Cacheable responses
The share of responses that carry cacheable headers.
64.8%
on the typical site
half of sites sit at or below
84.2%
1 in 4 sites exceed this
the top quarter
98.1%
the heaviest 1%
the long tail
185,486
sites measured
desktop field data
64.8% of responses on the typical site are cacheable.
The State of Web Vitals · Q2 2026 · 189,915 sites · desktop field datacorewebvitals.io/state-of-cwv
2
Cacheable responses the value at each percentile across all sites
Cacheable responses 64.8%. p75 84.2%. p99 98.1%. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · desktop field datacorewebvitals.io/state-of-cwv
3
Why this matters for the Core Web Vitals, and where to start fixing it
This is the share of responses a browser is allowed to keep. Everything outside that share gets re-downloaded on the next visit. Repeat visitors are in your field data too, and for them cacheability is the difference between reading from disk and crossing the network.
Uncacheable static assets are almost always an accident: a missing header on a font, a no-cache default on an image bucket. If a file has a hash in its name, there is no reason it should ever be fetched twice.
Related signals HTML compression → Cache strategy mix → HTTP protocol mix → HTTP protocol → 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.