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 86% of those sites have a good LCP, against 85% of all React sites.
LCP pass rate
Sites with fetchpriority="high" image fetchpriority hints have a good LCP most often: 86%, against 85% of all React sites. Sites with fetchpriority="low" fetchpriority hints have it least often, at 74%.
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 fetchpriority="low" sits in time to first byte (TTFB): 490 ms median for fetchpriority="high" against 793 ms for fetchpriority="low". Overall median field LCP is 1.3s for fetchpriority="high" (TTFB 490 ms, load delay 445 ms, load duration 143 ms, render delay 169 ms) versus 1.7s for fetchpriority="low".
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 85% of all sites. WordPress sets the image fetchpriority hints to default auto priority on 99% of its sites, and 61% 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%61%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, 60% of sites with fetchpriority="high" image fetchpriority hints have a good LCP, against 61% 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, 74% 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 (86% good LCP, heavily concentrated on WordPress), and 1.3% use fetchpriority="low" (74% good LCP).
By Arjen Karel · 9,570 crawled React sites (9,110 with all devices Chrome field data, 9,502 sites with image fetchpriority hints, October 2026). How we measured.