Image loading strategies on React sites
Eager above-the-fold (96.6%), eager below-the-fold (81.8%), CSS backgrounds (82.3%), lazy below-the-fold (56.7%), and lazy above-the-fold (32.6%): how page-wide image loading affects Largest Contentful Paint.
32.6% of React sites use lazy above-the-fold image loading strategies, and 87% of those sites have a good LCP, against 85% of all React sites.
LCP pass rate
Sites with lazy above-the-fold image loading strategies have a good LCP most often: 87%, against 85% of all React sites. Sites with eager below-the-fold image loading have it least often, at 83%.
Image loading strategies usage
Eager above-the-fold is the most used: 96.6% of React sites. Lazy above-the-fold is 32.6% of React sites.
How page-wide image loading shifts the four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between lazy above-the-fold and eager below-the-fold sits in time to first byte (TTFB): 499 ms median for lazy above-the-fold against 556 ms for eager below-the-fold. Overall median field LCP is 1.3s for lazy above-the-fold (TTFB 499 ms, load delay 456 ms, load duration 140 ms, render delay 173 ms) versus 1.5s for eager below-the-fold.
Image loading strategies per platform
On Wix, 99% of sites use eager above-the-fold image loading strategies, and 94% of Wix sites have a good LCP, against 85% of all sites. On WordPress, 96% of sites use eager below-the-fold, and 61% of WordPress sites have a good LCP.
Image loading strategies or the platform
Does the platform explain the image loading strategies difference?
On Wix, 94% of sites with lazy above-the-fold image loading strategies have a good LCP, against 94% of Wix sites with eager above-the-fold. Within Wix, sites with lazy above-the-fold and eager above-the-fold have a good LCP about equally often. On WordPress, 56% of sites with lazy above-the-fold image loading strategies have a good LCP, against 60% of WordPress sites with eager above-the-fold. Within WordPress, sites with lazy above-the-fold and eager above-the-fold have a good LCP about equally often.
How browser viewport intersection gates lazy image fetches
Standard <img> elements without loading="lazy" are queued by the HTML preload scanner before layout runs (439 ms median LCP load delay on sites with eager above-the-fold images). When loading="lazy" is present on an image inside the initial viewport (32.6% of sites), Chromium withholds the network request until style and layout confirm viewport intersection, pushing median LCP resource load delay to 456 ms.
Understanding image loading strategies
Keep above-the-fold hero and banner images eager while adding loading="lazy" to below-the-fold content and product grids. Across the web, 96.6% of sites ship eager above-the-fold images (85% good LCP, 439 ms load delay), 81.8% still leave below-the-fold images eager (83% good LCP), and 32.6% accidentally lazy-load an image inside the initial viewport (456 ms median load delay).
By Arjen Karel · 9,570 crawled React sites (9,110 with all devices Chrome field data, 9,561 sites with image loading strategies, October 2026). How we measured.