Cacheable resource share on Wix sites

The share of responses that carry cacheable headers.

Field data PhoneDesktopAll Scope All sites October 2026 edition · Desktop 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 93% of those sites have a good LCP, against 92% of all Wix sites.

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

SitesGood, needs improvement, poor LCPMedian
All Wix sites72892%1.2s
20% to 49% cacheable resources 0.2%1100%994ms
80%+ cacheable resources 68.0%49793%1.2s
50% to 79% cacheable resources 31.8%23090%1.3s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop 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.8%
80%+ cacheable resources 68.0% 50% to 79% cacheable resources 31.8% 20% to 49% cacheable resources 0.2%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop 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): 322 ms median for 80%+ cacheable resources against 415 ms for 50% to 79% cacheable resources. Overall median field LCP is 1.2s for 80%+ cacheable resources (TTFB 322 ms, load delay 476 ms, load duration 269 ms, render delay 138 ms) versus 1.3s for 50% to 79% cacheable resources.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All Wix sites 376343 ms478 ms259 ms478 mslab 462 ms1.2s
80%+ cacheable resources 249322 ms476 ms269 ms476 mslab 461 ms1.2s
50% to 79% cacheable resources 127415 ms483 ms236 ms483 mslab 472 ms1.3s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop 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 92% of React sites have a good LCP, against 92% 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%92%
React 5,620 sites80%+ cacheable resources 68%50% to 79% cacheable resources 32%92%
80%+ cacheable resources 50% to 79% cacheable resources 20% to 49% cacheable resources
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop 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, 93% of sites with 80%+ cacheable resources cacheable resource share have a good LCP, against 90% 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.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop 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 (728 with desktop Chrome field data, October 2026) · How we measured