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.

Field data PhoneDesktopAll Scope All sites October 2026 edition · Phone field outcomes · React sites only
React Scoped to 9,570 sites out of 210,902 analyzed (frameworks) Compare with all sites →

97.2% of React sites use default eager iframe loading, and 83% of those sites have a good LCP, against 84% of all React sites.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field data · 5,283 sites with iframe loadingBy Arjen Karel · corewebvitals.io/state-of-cwv
1

Core Web Vitals pass rate

Sites with default eager iframe loading have a good LCP most often: 83%, against 84% of all React sites. Sites with loading="lazy" iframe loading have it least often, at 72%.

SitesGood, needs improvement, poor LCPMedian
All React sites5,48884%1.4s
Default eager iframe (no loading="lazy") 97.2%2,98283%1.4s
Lazy-loaded iframe (loading="lazy") 5.8%16972%1.9s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field data · 5,283 sites with iframe loadingBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Iframe loading usage

Default eager is the most used: 97.2% of React sites.

Sites using each option (sites can use more than one) 5,283 sites
Default eager iframe (no loading="lazy") 97.2%
Default eager iframe (no loading="lazy") 97.2% Lazy-loaded iframe (loading="lazy") 5.8%
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field data · 5,283 sites with iframe loadingBy Arjen Karel · corewebvitals.io/state-of-cwv
3

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): 502 ms median for default eager against 835 ms for loading="lazy". Overall median field LCP is 1.4s for default eager (TTFB 502 ms, load delay 449 ms, load duration 130 ms, render delay 180 ms) versus 1.9s for loading="lazy".

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
React sites with iframe loading 2,357509 ms450 ms450 mslab 452 ms1.4s
Lazy-loaded iframe (loading="lazy") 127835 ms434 ms245 ms434 mslab 435 ms1.9s
Default eager iframe (no loading="lazy") 2,292502 ms449 ms449 mslab 452 ms1.4s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field data · 5,283 sites with iframe loadingBy Arjen Karel · corewebvitals.io/state-of-cwv
4

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 84% of all sites.

PlatformIframe loading on its sitesGood LCP
React sites with iframe loading 5,283 sitesDefault eager iframe (no loading="lazy") 97%84%
Wix 3,352 sitesDefault eager iframe (no loading="lazy") 100%94%
WordPress 1,198 sitesDefault eager iframe (no loading="lazy") 91%Lazy-loaded iframe (loading="lazy") 18%63%
Default eager iframe (no loading="lazy") Lazy-loaded iframe (loading="lazy")
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field data · 5,283 sites with iframe loadingBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Iframe loading or the platform

Does the platform explain the iframe loading difference?

On WordPress, 58% of sites with default eager iframe loading have a good LCP, against 65% of WordPress sites with loading="lazy". Within WordPress, sites with default eager and loading="lazy" have a good LCP 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 (83% good LCP, 1.4s median LCP) - often lightweight analytics or payment sandboxes - while 5.8% use loading="lazy" (72% good LCP, 1.9s median LCP), predominantly on article pages embedding heavy video players or maps.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field data · 5,283 sites with iframe loadingBy Arjen Karel · corewebvitals.io/state-of-cwv
6

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 (83% good LCP) and 5.8% ship loading="lazy" iframes (72% 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.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field data · 5,283 sites with iframe loadingBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Image format mix → Fonts per page → Font source → Script loading mix → By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, 5,283 sites with iframe loading, October 2026) · How we measured