Cacheable resource share on React sites
58.3% of audited sites (5,575) mark 80% or more of their subresources as cacheable and reach 81% good LCP (1.4s median), compared to 68% good LCP (1.9s median) on the 9.5% caching under 20% of resources.
58.3% of React sites use 80%+ cacheable resources cacheable resource share, and 81% of those sites have a good LCP, against 79% of all React sites.
LCP pass rate
Sites with 80%+ cacheable resources cacheable resource share have a good LCP most often: 81%, against 79% of all React sites. Sites with under 20% cacheable resources cacheable share have it least often, at 68%.
Cacheable resource share usage
80%+ cacheable resources is the most used: 58.3% of React sites.
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): 670 ms median for 80%+ cacheable resources against 906 ms for under 20% cacheable resources. Overall median field LCP is 1.5s for 80%+ cacheable resources (TTFB 670 ms, load delay 416 ms, load duration 164 ms, render delay 178 ms) versus 2.0s for under 20% cacheable resources.
Cacheable resource share per platform
Wix sets the cacheable resource share to 80%+ cacheable resources on 68% of its sites, and 92% of Wix sites have a good LCP, against 79% of all sites.
Cacheable resource share or the platform
Does the platform explain the cacheable resource share difference?
On Wix, 93% of sites with 80%+ cacheable resources cacheable resource share have a good LCP, against 90% 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 69% 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%, 81% and 80% pass field LCP (1.4s and 1.5s median). When cacheability falls to 20% to 49% (3.5%), good LCP drops to 72% (1.7s median), and below 20% cacheable (9.5%, 906 sites) good LCP drops to 68% (1.9s median).
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 (81% good LCP) versus 9.5% caching under 20% (68% good LCP).
By Arjen Karel · 9,570 crawled React sites (1,979 with desktop Chrome field data, October 2026). How we measured.