Cacheable resource share on Wix sites

68.0% of audited sites (3,821) mark 80% or more of their subresources as cacheable and reach 95% good LCP (1.2s median), compared to 100% good LCP (1.1s median) on the 0.1% caching under 20% of resources.

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes · Wix sites only
Wix Scoped to 5,623 sites out of 203,892 analyzed (cms) Compare with all sites →

68.0% of Wix sites use 80%+ cacheable resources cacheable resource share, and 95% of those sites have a good LCP, against 94% of all Wix sites.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices 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: 95%, against 94% of all Wix sites. Sites with 50% to 79% cacheable resources cacheable share have it least often, at 93%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites5,33394%1.2s
Under 20% cacheable resources 0.1%3100%1.1s
80%+ cacheable resources 68.0%3,60995%1.2s
50% to 79% cacheable resources 31.7%1,70993%1.2s
20% to 49% cacheable resources 0.2%1283%1.6s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Cacheable resource share usage

80%+ cacheable resources is the most used: 68.0% of Wix sites.

80%+ cacheable resources 68.0% 50% to 79% cacheable resources 31.7%
80%+ cacheable resources 68.0% 50% to 79% cacheable resources 31.7% 20% to 49% cacheable resources 0.2% Under 20% cacheable resources 0.1%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices 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 50% to 79% cacheable resources sits in time to first byte (TTFB): 411 ms median for 80%+ cacheable resources against 446 ms for 50% to 79% cacheable resources. Overall median field LCP is 1.2s for 80%+ cacheable resources (TTFB 411 ms, load delay 456 ms, load duration 140 ms, render delay 149 ms) versus 1.2s for 50% to 79% cacheable resources.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All Wix sites 3,945419 ms455 ms455 mslab 455 ms1.2s
50% to 79% cacheable resources 1,227446 ms451 ms451 mslab 451 ms1.2s
80%+ cacheable resources 2,707411 ms456 ms456 mslab 456 ms1.2s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Cacheable resource share per framework

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

FrameworkCacheable resource share on its sitesGood LCP
All Wix sites 5,621 sites80%+ cacheable resources 68%50% to 79% cacheable resources 32%94%
React 5,620 sites80%+ cacheable resources 68%50% to 79% cacheable resources 32%94%
80%+ cacheable resources 50% to 79% cacheable resources 20% to 49% cacheable resources Under 20% cacheable resources
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Cacheable resource share or the framework

Does the framework explain the cacheable resource share difference?

On React, 95% of sites with 80%+ cacheable resources cacheable resource share have a good LCP, against 93% of React sites with 50% to 79% cacheable resources. Within React, 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 3,821 sites (68.0%) with 80%+ cacheable resources and 1,784 sites (31.7%) at 50% to 79%, 95% and 93% pass field LCP (1.2s and 1.2s median). When cacheability falls to 20% to 49% (0.2%), good LCP drops to 83% (1.6s median), and below 20% cacheable (0.1%, 3 sites) good LCP drops to 100% (1.1s median).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices 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, 68.0% cache 80%+ of resources (95% good LCP) versus 0.1% caching under 20% (100% good LCP).

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