Image fetchpriority hints on React sites
Default auto priority (96.5%), fetchpriority="high" (79.8%), and fetchpriority="low" (1.3%): how image priority hints are deployed across the web and how they move Largest Contentful Paint.
79.8% of React sites use fetchpriority="high" image fetchpriority hints, and 87% of those sites have a good LCP, against 84% of all React sites.
LCP pass rate
Sites with fetchpriority="high" image fetchpriority hints have a good LCP most often: 87%, against 84% of all React sites. Sites with default auto priority fetchpriority hints have it least often, at 84%.
Image fetchpriority hints usage
Default auto priority is the most used: 96.5% of React sites. Fetchpriority="high" is 79.8% of React sites.
How image fetchpriority hints affect the four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between fetchpriority="high" and default auto priority sits in time to first byte (TTFB): 466 ms median for fetchpriority="high" against 510 ms for default auto priority. Overall median field LCP is 1.3s for fetchpriority="high" (TTFB 466 ms, load delay 435 ms, load duration 123 ms, render delay 169 ms) versus 1.4s for default auto priority.
Image fetchpriority hints per platform
Wix sets the image fetchpriority hints to fetchpriority="high" on 99% of its sites, and 94% of Wix sites have a good LCP, against 84% of all sites. WordPress sets the image fetchpriority hints to default auto priority on 99% of its sites, and 63% of WordPress sites have a good LCP.
Wix 5,802 sitesfetchpriority="high" 99%Default priority (auto / unset) 95%94%
WordPress 2,334 sitesDefault priority (auto / unset) 99%fetchpriority="high" 71%63%Image fetchpriority hints or the platform
Does the platform explain the image fetchpriority hints difference?
On Wix, 94% of sites with fetchpriority="high" image fetchpriority hints have a good LCP, against 94% of Wix sites with default auto priority. Within Wix, sites with fetchpriority="high" and default auto priority have a good LCP about equally often. On WordPress, 62% of sites with fetchpriority="high" image fetchpriority hints have a good LCP, against 63% of WordPress sites with default auto priority. Within WordPress, sites with fetchpriority="high" and default auto priority have a good LCP about equally often.
How fetchpriority="high" and fetchpriority="low" reorder image fetches
In Chromium, <img> requests start at Low priority until layout determines which images sit inside the viewport. Setting fetchpriority="high" (79.8% of sites) elevates the request to High priority during HTML parsing, while setting fetchpriority="low" (1.3% of sites, 75% good LCP) keeps offscreen carousel or thumbnail images from competing with critical resources.
Understanding image fetchpriority hints
Apply fetchpriority="high" only to the single above-the-fold LCP image, and use fetchpriority="low" on secondary carousel slides or product thumbnails that are fetched early. Across the web, 96.5% of sites have default-priority images (84% good LCP), 79.8% ship at least one fetchpriority="high" image (87% good LCP, heavily concentrated on WordPress), and 1.3% use fetchpriority="low" (75% good LCP).
By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, 9,502 sites with image fetchpriority hints, October 2026). How we measured.