Iframe loading attributes on React sites
Default eager iframes (97.2%) versus loading="lazy" iframes (5.8%): how third-party embed scheduling affects Largest Contentful Paint across the 5,283 sites that use iframes.
97.2% of React sites use default eager iframe loading, and 84% of those sites have a good LCP, against 85% of all React sites.
5.8% of React sites use loading="lazy" iframe loading, and 95% of those sites have a good INP, against 95% of all React sites.
Core Web Vitals pass rate
Sites with default eager iframe loading have a good LCP most often: 84%, against 85% of all React sites. Sites with loading="lazy" iframe loading have it least often, at 68%.
Sites with loading="lazy" iframe loading have a good INP most often: 95%, against 95% of all React sites. Sites with default eager iframe loading have it least often, at 95%.
Iframe loading usage
Default eager is the most used: 97.2% of React sites.
How iframe loading affects the four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between default eager and loading="lazy" sits in time to first byte (TTFB): 510 ms median for default eager against 1118 ms for loading="lazy". Overall median field LCP is 1.4s for default eager (TTFB 510 ms, load delay 453 ms, load duration 144 ms, render delay 174 ms) versus 2.0s for loading="lazy".
Across the four LCP sub-parts in Chrome's field data, the largest gap between default eager and loading="lazy" sits in time to first byte (TTFB): 510 ms median for default eager against 1118 ms for loading="lazy". Overall median field LCP is 1.4s for default eager (TTFB 510 ms, load delay 453 ms, load duration 144 ms, render delay 174 ms) versus 2.0s for loading="lazy".
Iframe loading per platform
Wix sets the iframe loading to default eager on 100% of its sites, and 94% of Wix sites have a good LCP, against 85% of all sites.
Wix sets the iframe loading to default eager on 100% of its sites, and 97% of Wix sites have a good INP, against 95% of all sites.
Iframe loading or the platform
Does the platform explain the iframe loading difference?
On WordPress, 56% of sites with default eager iframe loading have a good LCP, against 61% of WordPress sites with loading="lazy". Within WordPress, sites with default eager and loading="lazy" have a good LCP about equally often.
On WordPress, 96% of sites with loading="lazy" iframe loading have a good INP, against 98% of WordPress sites with default eager. Within WordPress, sites with loading="lazy" and default eager have a good INP about equally often.
How embedded iframes compete for network and main-thread budget
Every eager iframe initializes a nested browsing context that fetches its own HTML, stylesheets, and scripts during page startup. Among iframe-using sites, 97.2% include default eager iframes (84% good LCP, 1.4s median LCP) - often lightweight analytics or payment sandboxes - while 5.8% use loading="lazy" (68% good LCP, 2.0s median LCP), predominantly on article pages embedding heavy video players or maps.
Understanding iframe loading
Add loading="lazy" to all visible below-the-fold video, map, and social iframes, or replace them with a click-to-load poster facade. Among sites with iframes, 97.2% ship default eager iframes (84% good LCP) and 5.8% ship loading="lazy" iframes (68% good LCP). Avoid putting loading="lazy" on hidden zero-pixel auth or analytics sandboxes, and never leave visible third-party media embeds eager during initial page load.
By Arjen Karel · 9,570 crawled React sites (9,110 with all devices Chrome field data, 5,283 sites with iframe loading, October 2026). How we measured.