64.8% of responses on the typical site are cacheable

LCP INP CLS

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,271

sites measured

all-device field data

64.8% of responses on the typical site are cacheable.

The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv

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

0ms 63ms 125ms 188ms 250ms

200ms

0 17781 35561

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 · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv

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

Cacheable responsesSitesPassing INPINP

0 21,737 90% 84ms

0–10 20,273 95% 86ms

10–20 15,946 96% 85ms

20–30 9,394 95% 86ms

30–40 6,325 93% 88ms

40–50 5,480 91% 93ms

50–60 7,987 93% 92ms

60–70 13,272 94% 89ms

70–80 23,090 94% 91ms

80–90 35,561 97% 86ms

90–100 25,559 98% 83ms

100 647 96% 75ms

Good Needs Improvement Poor Faded rows: under 100 sites

Cacheable responses 64.8%. p75 84.2%. p99 98.1%. At the low end (0): INP 84ms. At the high end (100): INP 75ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv

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, 85% of sites pass the LCP. Where it is high, 93% 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 189,915 sites, representing millions of real page loads · How we measured