Cacheable resource share on Wix sites
The share of responses that carry cacheable headers.
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.
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%.
Cacheable resource share usage
80%+ cacheable resources is the most used: 68.0% of Wix 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 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.
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.
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.
By Arjen Karel · 5,621 crawled Wix sites (728 with desktop Chrome field data, October 2026). How we measured.