LCP priority hints on Wix sites
The strongest priority signal on the LCP element: preload, fetchpriority, preconnect, or none.
Half of Wix sites, 49.4%, have no LCP priority hints. Of the 50.6% that do, 100% use fetchpriority="high", and 94% of those sites have a good LCP, against 94% of all Wix sites.
LCP pass rate
Sites with fetchpriority="high" LCP priority hints have a good LCP most often: 94%, against 94% of all Wix sites.
LCP priority hints usage
Half of Wix sites use LCP priority hints, and 100% of those use fetchpriority="high".
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 resource load delay: 452 ms median for fetchpriority="high" against 439 ms for no. Overall median field LCP is 1.1s for fetchpriority="high" (TTFB 405 ms, load delay 452 ms, load duration 113 ms, render delay 151 ms) versus 1.1s for no.
LCP priority hints combined with the loading attribute
Combining no with Lazy reaches 94% good LCP across 434 sites (433 ms median load delay). At the other end, no paired with Eager sits at 91% across 158 sites (451 ms median load delay).
| Priority hint | No loading attribute (auto) | loading="lazy" | loading="eager" |
|---|---|---|---|
| No priority hint | 100% 33 sites | 94% 789 sites | 91% 285 sites |
| fetchpriority="high" | 94% 2,745 sites | 95% 84 sites | few sites |
LCP priority hints per framework
React sets the LCP priority hints to fetchpriority="high" on 51% of its sites, and 94% of React sites have a good LCP, against 94% of all sites.
LCP priority hints or the framework
Does the framework explain the LCP priority hints difference?
On React, 94% of sites with fetchpriority="high" LCP priority hints have a good LCP, against 94% of React sites without LCP priority hints. Within React, sites with and without LCP priority hints have a good LCP about equally often.
By Arjen Karel · 5,621 crawled Wix sites (3,077 with phone Chrome field data, 5,589 sites with LCP priority hints, October 2026). How we measured.