The State of Web Vitals

LCP priority hints on Wix sites

The strongest priority signal on the LCP element: preload, fetchpriority, preconnect, or none.

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

Half of Wix sites, 49.4%, have no LCP priority hints. Of the 50.6% that do, 100% use fetchpriority="high", and 93% of those sites have a good LCP, against 92% of all Wix sites.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,589 sites with LCP priority hintsBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with fetchpriority="high" LCP priority hints have a good LCP most often: 93%, against 92% of all Wix sites.

SitesGood, needs improvement, poor LCPMedian
All Wix sites72892%1.2s
fetchpriority="high" 50.6%34893%1.2s
No priority hint 49.4%37392%1.2s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,589 sites with LCP priority hintsBy Arjen Karel · corewebvitals.io/state-of-cwv
2

LCP priority hints usage

Half of Wix sites use LCP priority hints, and 100% of those use fetchpriority="high".

Wix sites with LCP priority hints 5,589 sites
No priority hint 49.4% LCP priority hints 50.6%
Sites with LCP priority hints 2,829 sites
fetchpriority="high" 100.0%
fetchpriority="high" 100.0%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,589 sites with LCP priority hintsBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Where priority hints save time: the four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between fetchpriority="high" and no sits in time to first byte (TTFB): 321 ms median for fetchpriority="high" against 353 ms for no. Overall median field LCP is 1.2s for fetchpriority="high" (TTFB 321 ms, load delay 481 ms, load duration 256 ms, render delay 135 ms) versus 1.3s for no.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Wix sites with LCP priority hints 371349 ms480 ms259 ms137 ms480 mslab 469 ms1.2s
No priority hint 189353 ms478 ms261 ms139 ms478 mslab 462 ms1.3s
fetchpriority="high" 182321 ms481 ms256 ms481 mslab 471 ms1.2s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,589 sites with LCP priority hintsBy Arjen Karel · corewebvitals.io/state-of-cwv
4

LCP priority hints combined with the loading attribute

Combining no with Lazy reaches 93% good LCP across 100 sites (447 ms median load delay). At the other end, fetchpriority="high" paired with Auto sits at 93% across 321 sites (478 ms median load delay).

Priority hint No loading attribute (auto) loading="lazy" loading="eager"
No priority hint
100% 453 ms delay 33 sites
93% 447 ms delay 789 sites
87% 509 ms delay 285 sites
fetchpriority="high"
93% 478 ms delay 2,745 sites
93% 505 ms delay 84 sites
few sites
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,589 sites with LCP priority hintsBy Arjen Karel · corewebvitals.io/state-of-cwv
5

LCP priority hints per framework

React sets the LCP priority hints to fetchpriority="high" on 51% of its sites, and 92% of React sites have a good LCP, against 92% of all sites.

FrameworkLCP priority hints on its sitesGood LCP
Wix sites with LCP priority hints 5,589 sitesfetchpriority="high" 51%No priority hint 49%92%
React 5,588 sitesfetchpriority="high" 51%No priority hint 49%92%
fetchpriority="high" No priority hint
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,589 sites with LCP priority hintsBy Arjen Karel · corewebvitals.io/state-of-cwv
6

LCP priority hints or the framework

Does the framework explain the LCP priority hints difference?

On React, 93% of sites with fetchpriority="high" LCP priority hints have a good LCP, against 92% of React sites without LCP priority hints. Within React, sites with and without LCP priority hints have a good LCP about equally often.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,589 sites with LCP priority hintsBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals LCP image size → LCP origin → LCP image format → LCP element type → By Arjen Karel · 5,621 crawled Wix sites (728 with desktop Chrome field data, 5,589 sites with LCP priority hints, October 2026) · How we measured