Shopify cacheable resource share and the Core Web Vitals
60.7% of audited sites (5,006) mark 80% or more of their subresources as cacheable and reach 97% good LCP (1.2s median), compared to 100% good LCP (1.4s median) on the <0.1% caching under 20% of resources.
60.7% of Shopify sites use 80%+ cacheable resources cacheable resource share, and 97% of those sites have a good LCP, against 96% of all Shopify sites.
LCP pass rate
Sites with 80%+ cacheable resources cacheable resource share have a good LCP most often: 97%, against 96% of all Shopify sites. Sites with 50% to 79% cacheable resources cacheable share have it least often, at 94%.
Cacheable resource share usage
80%+ cacheable resources is the most used: 60.7% of Shopify 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 element render delay: 265 ms median for 80%+ cacheable resources against 359 ms for 50% to 79% cacheable resources. Overall median field LCP is 1.2s for 80%+ cacheable resources (TTFB 381 ms, load delay 558 ms, load duration 220 ms, render delay 265 ms) versus 1.5s for 50% to 79% cacheable resources.
Cacheable resource share per framework
jQuery sets the cacheable resource share to 80%+ cacheable resources on 54% of its sites, and 94% of jQuery sites have a good LCP, against 96% of all sites.
Cacheable resource share or the framework
Does the framework explain the cacheable resource share difference?
On jQuery, 96% of sites with 80%+ cacheable resources cacheable resource share have a good LCP, against 91% of jQuery sites with 50% to 79% cacheable resources. Within jQuery, sites with 80%+ cacheable resources have a good LCP more often. On Vue, 96% of sites with 80%+ cacheable resources cacheable resource share have a good LCP, against 94% of Vue sites with 50% to 79% cacheable resources. Within Vue, 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,006 sites (60.7%) with 80%+ cacheable resources and 3,214 sites (39.0%) at 50% to 79%, 97% and 94% pass field LCP (1.2s and 1.5s median). When cacheability falls to 20% to 49% (0.3%), good LCP drops to 80% (1.3s median), and below 20% cacheable (<0.1%, 1 sites) good LCP drops to 100% (1.4s 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, 60.7% cache 80%+ of resources (97% good LCP) versus <0.1% caching under 20% (100% good LCP).
By Arjen Karel · 8,246 crawled Shopify sites (8,062 with all devices Chrome field data, October 2026). How we measured.