The State of Web Vitals

Wix LCP resource discovery and the Core Web Vitals

HTML markup, CSS background-image, <link rel="preload">, JavaScript, or HTTP Link header: how the browser finds the LCP element and how much load delay each path adds.

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

On 98.8% of Wix sites, the browser finds the LCP element straight in the HTML. 1.1% hide it in a CSS stylesheet, and 0.1% inject it with JavaScript. Sites with the LCP element in HTML have a good LCP on 94% of sites (1.2s median), against 93% for CSS discovery (1.2s) and 100% for JavaScript discovery (1.6s).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,589 sites with LCP resource discoveryBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with HTML discovery have a good LCP on 94% of Wix sites, CSS discovery at 93%, and JavaScript discovery at 100%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites5,33394%1.2s
JavaScript injection 0.1%7100%1.6s
HTML document 98.8%5,24194%1.2s
CSS background-image 1.1%5593%1.2s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,589 sites with LCP resource discoveryBy Arjen Karel · corewebvitals.io/state-of-cwv
2

LCP resource discovery usage

On Wix, 98.8% of sites put their LCP element in the initial HTML markup. 1.1% (59 sites) put the LCP image inside a CSS background-image rule.

HTML document 98.8%
HTML document 98.8% CSS background-image 1.1% JavaScript injection 0.1%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,589 sites with LCP resource discoveryBy Arjen Karel · corewebvitals.io/state-of-cwv
3

LCP phase breakdown by discovery path

How the browser discovers the LCP asset directly sets its resource load delay: HTML discovery after 456 ms, CSS discovery after 418 ms, JavaScript discovery after 716 ms.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Wix sites with LCP resource discovery 3,917419 ms456 ms456 mslab 456 ms1.2s
CSS background-image 41425 ms418 ms418 mslab 418 ms1.3s
HTML document 3,870418 ms456 ms456 mslab 456 ms1.2s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,589 sites with LCP resource discoveryBy Arjen Karel · corewebvitals.io/state-of-cwv
4

LCP discovery path by element type

Discovery path <img> element CSS background-image Text block <video> element
HTML document
94% 460 ms delay 3,930 sites
few sites
95% 446 ms delay 1,493 sites
93% 498 ms delay 100 sites
CSS background-image few sites
93% 418 ms delay 59 sites
few sites few sites
JavaScript injection few sites few sites few sites few sites
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,589 sites with LCP resource discoveryBy Arjen Karel · corewebvitals.io/state-of-cwv
5

LCP resource discovery per framework

React discovers the LCP element in HTML on 99% of its sites and in CSS on 1%, and 94% of React sites have a good LCP.

FrameworkLCP resource discovery on its sitesGood LCP
Wix sites with LCP resource discovery 5,589 sitesHTML document 99%94%
React 5,588 sitesHTML document 99%94%
HTML document CSS background-image JavaScript injection
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,589 sites with LCP resource discoveryBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding LCP resource discovery

Put the LCP image in the initial HTML as an <img> (or <picture>) element with fetchpriority="high". Do not hide hero images in CSS background-image rules or render them from client-side JavaScript. Across this dataset, 1.1% of sites put their LCP image in CSS, which adds 38 ms of resource load delay and drops good LCP from 94% to 93%. If a theme or page builder locks the hero into a CSS background-image, add <link rel="preload" as="image" fetchpriority="high"> in the <head> or send a Link: rel=preload HTTP header. The browser can then start downloading the image before the stylesheet arrives.

Go fix it LCP: resource load delay → Preload the LCP image → Background images are evil → How I lowered the LCP by 70 percent →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field data · 5,589 sites with LCP resource discoveryBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals LCP image size → LCP element type → LCP origin → LCP image format → By Arjen Karel · 5,621 crawled Wix sites (5,333 with all devices Chrome field data, 5,589 sites with LCP resource discovery, October 2026) · How we measured