The State of Web Vitals

Cacheable responses

The share of responses that carry cacheable headers.

Field data PhoneDesktopAll Scope All sites Q1 2026 edition · Desktop field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for Cacheable responses

The share of responses that carry cacheable headers.

66.5%
on the typical site
half of sites sit at or below
84.5%
1 in 4 sites exceed this
the top quarter
98.1%
the heaviest 1%
the long tail
94,910
sites measured
desktop field data

66.5% of responses on the typical site are cacheable.

The State of Web Vitals · Q1 2026 · 94,910 sites · desktop field datacorewebvitals.io/state-of-cwv
2

Distribution & median INP site count and median INP at each level of cacheable responses

0ms 63ms 125ms 188ms 250ms
200ms
0 9261 18521
0 0–10 10–20 20–30 30–40 40–50 50–60 60–70 70–80 80–90 90–100 100
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · desktop field datacorewebvitals.io/state-of-cwv
3

Passing INP by cacheable responses which level passes the INP most often

Cacheable responsesSitesPassing INPINP
0 9,115 98% 44ms
0–10 10,556 99% 46ms
10–20 8,437 99% 48ms
20–30 4,946 99% 48ms
30–40 3,352 98% 53ms
40–50 2,809 97% 55ms
50–60 4,223 98% 56ms
60–70 7,001 99% 56ms
70–80 12,116 99% 55ms
80–90 18,521 99% 49ms
90–100 13,483 99% 45ms
100 351 100% 39ms
Good Needs Improvement Poor Faded rows: under 100 sites

Cacheable responses 66.5%. p75 84.5%. p99 98.1%. At the low end (0): INP 44ms. At the high end (100): INP 39ms. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · desktop field datacorewebvitals.io/state-of-cwv
4

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.

How does caching affect the Core Web Vitals?

Cacheable share correlates with the LCP. Where the cacheable share is low, 87% of sites pass the LCP. Where it is high, 96% do. The rise is gradual.

Go fix it TTFB: cache duration → Configure Cloudflare for passing the Core Web Vitals →
Related signals HTML compression → Cache strategy mix → HTTP protocol mix → HTTP protocol → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured