Cacheable resource share on React sites

58.3% of audited sites (5,575) mark 80% or more of their subresources as cacheable and reach 88% good LCP (1.3s median), compared to 64% good LCP (2.2s median) on the 9.5% caching under 20% of resources.

Field data PhoneDesktopAll Scope All sites October 2026 edition · Phone field outcomes · React sites only
React Scoped to 9,570 sites out of 210,902 analyzed (frameworks) Compare with all sites →

58.3% of React sites use 80%+ cacheable resources cacheable resource share, and 88% of those sites have a good LCP, against 84% of all React sites.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with 80%+ cacheable resources cacheable resource share have a good LCP most often: 88%, against 84% of all React sites. Sites with under 20% cacheable resources cacheable share have it least often, at 64%.

SitesGood, needs improvement, poor LCPMedian
All React sites5,48884%1.4s
80%+ cacheable resources 58.3%3,13788%1.3s
50% to 79% cacheable resources 28.8%1,60686%1.4s
20% to 49% cacheable resources 3.5%21269%2.0s
Under 20% cacheable resources 9.5%53364%2.2s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Cacheable resource share usage

80%+ cacheable resources is the most used: 58.3% of React sites.

80%+ cacheable resources 58.3% 50% to 79% cacheable resources 28.8%
80%+ cacheable resources 58.3% 50% to 79% cacheable resources 28.8% Under 20% cacheable resources 9.5% 20% to 49% cacheable resources 3.5%
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

LCP phase breakdown by share of cacheable subresources

Across the four LCP sub-parts in Chrome's field data, the largest gap between 80%+ cacheable resources and under 20% cacheable resources sits in time to first byte (TTFB): 453 ms median for 80%+ cacheable resources against 1110 ms for under 20% cacheable resources. Overall median field LCP is 1.3s for 80%+ cacheable resources (TTFB 453 ms, load delay 439 ms, load duration 127 ms, render delay 168 ms) versus 2.2s for under 20% cacheable resources.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All React sites 4,169502 ms433 ms433 mslab 439 ms1.4s
Under 20% cacheable resources 3941110 ms382 ms261 ms382 mslab 377 ms2.2s
50% to 79% cacheable resources 1,190488 ms429 ms429 mslab 435 ms1.4s
80%+ cacheable resources 2,427453 ms439 ms439 mslab 448 ms1.3s
20% to 49% cacheable resources 158855 ms451 ms222 ms451 mslab 455 ms2.0s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Cacheable resource share per platform

Wix sets the cacheable resource share to 80%+ cacheable resources on 68% of its sites, and 94% of Wix sites have a good LCP, against 84% of all sites.

PlatformCacheable resource share on its sitesGood LCP
All React sites 9,570 sites80%+ cacheable resources 58%50% to 79% cacheable resources 29%84%
Wix 5,824 sites80%+ cacheable resources 68%50% to 79% cacheable resources 31%94%
WordPress 2,342 sites80%+ cacheable resources 46%Under 20% cacheable resources 31%50% to 79% cacheable resources 16%63%
80%+ cacheable resources 50% to 79% cacheable resources Under 20% cacheable resources 20% to 49% cacheable resources
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Cacheable resource share or the platform

Does the platform explain the cacheable resource share difference?

On Wix, 95% of sites with 80%+ cacheable resources cacheable resource share have a good LCP, against 93% of Wix sites with 50% to 79% cacheable resources. Within Wix, sites with 80%+ cacheable resources and 50% to 79% cacheable resources have a good LCP about equally often. On WordPress, 64% of sites with 80%+ cacheable resources cacheable resource share have a good LCP, against 68% of WordPress sites with 50% to 79% cacheable resources. Within WordPress, sites with 80%+ cacheable resources and 50% to 79% cacheable resources have a good LCP about equally often.

How subresource Cache-Control coverage speeds up repeat visits and CDN edge hits

Cacheable resource share tracks the percentage of page requests carrying valid Cache-Control or Expires headers. Across 5,575 sites (58.3%) with 80%+ cacheable resources and 2,756 sites (28.8%) at 50% to 79%, 88% and 86% pass field LCP (1.3s and 1.4s median). When cacheability falls to 20% to 49% (3.5%), good LCP drops to 69% (2.0s median), and below 20% cacheable (9.5%, 906 sites) good LCP drops to 64% (2.2s median).

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding cacheable resource share

Ensure at least 80% of subresources return explicit Cache-Control max-age headers so browsers and CDN edges serve static assets without origin round-trips. Across all audited sites, 58.3% cache 80%+ of resources (88% good LCP) versus 9.5% caching under 20% (64% good LCP).

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals HTML compression → Cache strategy mix → HTTP protocol mix → HTTP protocol → By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, October 2026) · How we measured