Shopify LCP image byte weight and the Core Web Vitals

41.7% of audited sites (2,882) keep their LCP hero image under 40 KB and pass LCP at 97% (1.3s median), whereas the 3.2% shipping hero images over 300 KB drop to 94% (1.5s median).

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

41.7% of Shopify sites use an LCP image under 40 KB LCP image byte weight, and 97% of those sites have a good LCP, against 96% of all Shopify sites.

The State of Web Vitals · October 2026 · Shopify: 8,246 crawled sites · 8,062 with all devices field data · 6,910 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with an LCP image under 40 KB LCP image byte weight have a good LCP most often: 97%, against 96% of all Shopify sites. Sites with an LCP image over 300 KB hero image size have it least often, at 94%.

SitesGood, needs improvement, poor LCPMedian
All Shopify sites8,06296%1.3s
Under 40 KB hero image 41.7%2,81597%1.3s
100 to 300 KB hero image 14.3%96496%1.3s
40 to 100 KB hero image 40.8%2,77396%1.3s
Over 300 KB hero image 3.2%21794%1.5s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Shopify: 8,246 crawled sites · 8,062 with all devices field data · 6,910 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
2

LCP image byte weight usage

An LCP image under 40 KB is the most used: 41.7% of Shopify sites.

Under 40 KB hero image 41.7% 40 to 100 KB hero image 40.8% 100 to 300 KB hero image 14.3%
Under 40 KB hero image 41.7% 40 to 100 KB hero image 40.8% 100 to 300 KB hero image 14.3% Over 300 KB hero image 3.2%
The State of Web Vitals · October 2026 · Shopify: 8,246 crawled sites · 8,062 with all devices field data · 6,910 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
3

The four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between an LCP image under 40 KB and an LCP image over 300 KB sits in element render delay: 266 ms median for an LCP image under 40 KB against 367 ms for an LCP image over 300 KB. Overall median field LCP is 1.3s for an LCP image under 40 KB (TTFB 390 ms, load delay 570 ms, load duration 208 ms, render delay 266 ms) versus 1.5s for an LCP image over 300 KB.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Shopify sites with LCP image byte weight 5,995387 ms590 ms211 ms290 ms590 mslab 590 ms1.3s
Under 40 KB hero image 2,475390 ms570 ms208 ms266 ms570 mslab 570 ms1.3s
40 to 100 KB hero image 2,472389 ms598 ms209 ms294 ms598 mslab 598 ms1.3s
100 to 300 KB hero image 862379 ms605 ms219 ms331 ms605 mslab 605 ms1.3s
Over 300 KB hero image 186377 ms660 ms242 ms367 ms660 mslab 660 ms1.5s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Shopify: 8,246 crawled sites · 8,062 with all devices field data · 6,910 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
4

LCP image byte weight per framework

On jQuery, 40% of sites use an LCP image between 40 and 100 KB LCP image byte weight, and 94% of jQuery sites have a good LCP, against 96% of all sites. On Vue, 43% of sites use an LCP image between 40 and 100 KB, and 95% of Vue sites have a good LCP.

FrameworkLCP image byte weight on its sitesGood LCP
Shopify sites with LCP image byte weight 6,910 sitesUnder 40 KB hero image 42%40 to 100 KB hero image 41%100 to 300 KB hero image 14%96%
Vue 784 sites40 to 100 KB hero image 43%Under 40 KB hero image 38%100 to 300 KB hero image 14%95%
jQuery 2,651 sites40 to 100 KB hero image 40%Under 40 KB hero image 40%100 to 300 KB hero image 16%94%
Under 40 KB hero image 40 to 100 KB hero image 100 to 300 KB hero image Over 300 KB hero image
The State of Web Vitals · October 2026 · Shopify: 8,246 crawled sites · 8,062 with all devices field data · 6,910 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
5

LCP image byte weight or the framework

Does the framework explain the LCP image byte weight difference?

On jQuery, 95% of sites with an LCP image under 40 KB LCP image byte weight have a good LCP, against 94% of jQuery sites with an LCP image between 40 and 100 KB. Within jQuery, sites with an LCP image under 40 KB and an LCP image between 40 and 100 KB have a good LCP about equally often. On Vue, 96% of sites with an LCP image under 40 KB LCP image byte weight have a good LCP, against 95% of Vue sites with an LCP image between 40 and 100 KB. Within Vue, sites with an LCP image under 40 KB and an LCP image between 40 and 100 KB have a good LCP about equally often.

How intrinsic versus rendered megapixels waste hero bandwidth

The median LCP image is 0.23 intrinsic megapixels rendered into a 0.12 megapixel slot. Serving unresized desktop banners to mobile viewports inflates hero transfer bytes and extends LCP load duration. Across 2,882 sites (41.7%) with a hero image under 40 KB, 97% pass field LCP (1.3s median), dropping to 94% (1.5s median) on the 3.2% (223) exceeding 300 KB.

The State of Web Vitals · October 2026 · Shopify: 8,246 crawled sites · 8,062 with all devices field data · 6,910 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding LCP image byte weight

Compress hero images below 100 KB using AVIF or WebP and serve responsive srcset widths matched to the rendered viewport slot. Across all audited sites, 41.7% keep the hero image under 40 KB (97% good LCP, 1.3s median) versus 3.2% above 300 KB (94% good LCP, 1.5s median).

The State of Web Vitals · October 2026 · Shopify: 8,246 crawled sites · 8,062 with all devices field data · 6,910 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals LCP loading attribute → LCP element type → LCP responsive markup → LCP discovery → By Arjen Karel · 8,246 crawled Shopify sites (8,062 with all devices Chrome field data, 6,910 sites with LCP image byte weight, October 2026) · How we measured