The State of Web Vitals

LCP image byte weight on Wix sites

60.9% of audited sites (2,411) keep their LCP hero image under 40 KB and pass LCP at 94% (1.2s median), whereas the 0.5% shipping hero images over 300 KB drop to 89% (1.2s median).

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

32.3% of Wix sites use an LCP image between 40 and 100 KB LCP image byte weight, and 96% 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 · 3,077 with phone field data · 3,960 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with an LCP image between 40 and 100 KB LCP image byte weight have a good LCP most often: 96%, against 94% of all Wix sites. Sites with an LCP image between 100 and 300 KB hero image size have it least often, at 92%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites3,07794%1.1s
40 to 100 KB hero image 32.3%70396%1.1s
Under 40 KB hero image 60.9%1,34894%1.2s
100 to 300 KB hero image 6.4%13492%1.1s
Over 300 KB hero image 0.5%989%1.2s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,960 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: 60.9% of Wix sites. An LCP image between 40 and 100 KB is 32.3% of Wix sites.

Under 40 KB hero image 60.9% 40 to 100 KB hero image 32.3%
Under 40 KB hero image 60.9% 40 to 100 KB hero image 32.3% 100 to 300 KB hero image 6.4% Over 300 KB hero image 0.5%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,960 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 between 40 and 100 KB and an LCP image between 100 and 300 KB sits in resource load delay: 461 ms median for an LCP image between 40 and 100 KB against 443 ms for an LCP image between 100 and 300 KB. Overall median field LCP is 1.2s for an LCP image between 40 and 100 KB (TTFB 396 ms, load delay 461 ms, load duration 123 ms, render delay 153 ms) versus 1.1s for an LCP image between 100 and 300 KB.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Wix sites with LCP image byte weight 1,719406 ms448 ms152 ms448 mslab 457 ms1.1s
100 to 300 KB hero image 115389 ms443 ms128 ms157 ms443 mslab 455 ms1.1s
Under 40 KB hero image 1,047415 ms445 ms150 ms445 mslab 452 ms1.1s
40 to 100 KB hero image 549396 ms461 ms153 ms461 mslab 462 ms1.2s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,960 sites with LCP image byte weightBy Arjen Karel · corewebvitals.io/state-of-cwv
4

LCP image byte weight per framework

On React, 61% of sites use an LCP image under 40 KB LCP image byte weight, and 94% of React sites have a good LCP, against 94% of all sites.

FrameworkLCP image byte weight on its sitesGood LCP
Wix sites with LCP image byte weight 3,960 sitesUnder 40 KB hero image 61%40 to 100 KB hero image 32%94%
React 3,959 sitesUnder 40 KB hero image 61%40 to 100 KB hero image 32%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 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,960 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 React, 96% of sites with an LCP image between 40 and 100 KB LCP image byte weight have a good LCP, against 94% of React sites with an LCP image under 40 KB. Within React, sites with an LCP image between 40 and 100 KB and an LCP image under 40 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,411 sites (60.9%) with a hero image under 40 KB, 94% pass field LCP (1.2s median), dropping to 89% (1.2s median) on the 0.5% (18) exceeding 300 KB.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,960 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, 60.9% keep the hero image under 40 KB (94% good LCP, 1.2s median) versus 0.5% above 300 KB (89% good LCP, 1.2s median).

Go fix it Optimize the LCP image → LCP: resource load duration → Optimize images for Core Web Vitals →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field data · 3,960 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 · 5,621 crawled Wix sites (3,077 with phone Chrome field data, 3,960 sites with LCP image byte weight, October 2026) · How we measured