LCP priority hints on React sites
fetchpriority="high", <link rel="preload">, <link rel="preconnect">, or no hint at all: how priority hints cut LCP resource load delay (239 ms with preload vs 421 ms with no hint) and move Largest Contentful Paint.
Three in five React sites, 60.5%, have no LCP priority hints. Of the 39.5% that do, 90% use fetchpriority="high", and 88% of those sites have a good LCP, against 79% of all React sites.
LCP pass rate
Sites with fetchpriority="high" LCP priority hints have a good LCP most often: 88%, against 79% of all React sites.
LCP priority hints usage
Two in five React sites uses LCP priority hints, and nine in ten 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 time to first byte (TTFB): 461 ms median for fetchpriority="high" against 773 ms for no. Overall median field LCP is 1.3s for fetchpriority="high" (TTFB 461 ms, load delay 446 ms, load duration 201 ms, render delay 161 ms) versus 1.7s for no.
LCP priority hints combined with the loading attribute
Combining fetchpriority="high" with Auto reaches 88% good LCP across 449 sites (442 ms median load delay). At the other end, no paired with Auto sits at 74% across 251 sites (327 ms median load delay).
| Priority hint | No loading attribute (auto) | loading="lazy" | loading="eager" |
|---|---|---|---|
| No priority hint | 74% 779 sites | 87% 990 sites | 85% 325 sites |
| fetchpriority="high" | 88% 3,194 sites | 89% 90 sites | 79% 71 sites |
| <link rel="preload"> | few sites | few sites | few sites |
| <link rel="preconnect"> | 77% 199 sites | few sites | few sites |
LCP priority hints per platform
Wix sets the LCP priority hints to fetchpriority="high" on 52% of its sites, and 92% of Wix sites have a good LCP, against 79% of all sites.
Wix 5,791 sitesfetchpriority="high" 52%No priority hint 48%92%
WordPress 2,219 sitesNo priority hint 81%fetchpriority="high" 13%66%LCP priority hints or the platform
Does the platform explain the LCP priority hints difference?
On Wix, 93% of sites with fetchpriority="high" LCP priority hints have a good LCP, against 92% of Wix sites without LCP priority hints. Within Wix, sites with and without LCP priority hints have a good LCP about equally often.
How fetchpriority and preload change Chrome's network queue
Chromium starts <img> requests at Low network priority while stylesheets and head scripts download at Highest or High priority, only promoting visible viewport images to High after layout completes. Adding fetchpriority="high" to the hero <img> sets its initial network priority to High during the preload scan, while <link rel="preload" as="image"> starts the download from the document <head> and cuts median resource load delay from 421 ms to 239 ms.
Understanding LCP priority hints
Add fetchpriority="high" directly to your hero <img> element, and use <link rel="preload" as="image" fetchpriority="high"> if the image is discovered late. Across all audited sites, 60.5% of LCP elements carry no priority hint at all (76% good LCP, 421 ms median resource load delay). Sites using fetchpriority="high" reach 88% good LCP (446 ms load delay), and sites using <link rel="preload"> cut median resource load delay to 239 ms. Apply priority hints strictly to the single LCP resource so other images do not compete for the same bandwidth.
By Arjen Karel · 9,570 crawled React sites (1,979 with desktop Chrome field data, 9,390 sites with LCP priority hints, October 2026). How we measured.