1
At a glance the headline numbers for Iframes per page
How many iframes the page embeds.
0
on the typical site
half of sites sit at or below
2
1 in 4 sites exceed this
the top quarter
8
the heaviest 1%
the long tail
180,899
sites measured
phone field data
The typical page embeds 0 iframes.
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
2
Distribution & median LCP site count and median LCP at each level of iframes per page
0ms 750ms 1500ms 2250ms 3000ms
2.5s
0 51319 102637
0–0 1–1 2–2 3+
Good (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
3
Passing LCP by iframes per page which level passes the LCP most often
Iframes per pageSitesPassing LCPLCP
0–0 102,637 1.5s
1–1 31,433 1.6s
2–2 21,235 1.7s
3+ 25,594 1.7s
Good Needs Improvement Poor Faded rows: under 100 sites
Iframes per page 0. p75 2. p99 8. At the low end (0–0): LCP 1.5s. At the high end (3+): LCP 1.7s. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
4
Why this matters for the Core Web Vitals, and where to start fixing it
Each iframe is a separate document with its own resources, scripts and lifecycle, and its work still competes for the same device. The count is a decent proxy for embed weight: chat widgets, videos, ad slots, forms.
Every embed should justify itself. The heavy default (always-on iframe) has a light replacement for almost every case: a facade for video and chat, a static image for maps, a reserved slot for ads.
Related signals Responsive image markup → Image fetchpriority → Script coverage (used vs unused) → Bytes by resource type → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.