66.5% 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.

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

all-device field data

66.5% of responses on the typical site are cacheable.

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

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

0ms 750ms 1500ms 2250ms 3000ms

2.5s

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 (≤2.5s) Needs improvement Poor (>4s) Site count

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

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

Cacheable responsesSitesPassing LCPLCP

0 9,115 85% 1.3s

0–10 10,556 74% 1.7s

10–20 8,437 78% 1.7s

20–30 4,946 82% 1.5s

30–40 3,352 83% 1.5s

40–50 2,809 79% 1.6s

50–60 4,223 83% 1.5s

60–70 7,001 85% 1.5s

70–80 12,116 86% 1.5s

80–90 18,521 86% 1.4s

90–100 13,483 83% 1.5s

100 351 94% 1.1s

Good Needs Improvement Poor Faded rows: under 100 sites

Cacheable responses 66.5%. p75 84.5%. p99 98.1%. At the low end (0): LCP 1.3s. At the high end (100): LCP 1.1s. computed

The State of Web Vitals · Q1 2026 · 94,910 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, 94% 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