Iframe dimensions set
Whether iframes declare dimensions - unsized iframes shift layout.
At a glance the headline numbers for Iframe dimensions set
Whether iframes declare dimensions - unsized iframes shift layout.
68.4% of iframes declare no dimensions.
The iframe dimensions set mix who uses what, and how fast each group loads
Iframe dimensions set. On the fleet: 68.4% has none, 31.6% has dimensions. 35.4% of sites use at least one has_none.
Lowest-share bucket: LCP 1.3s. Highest-share bucket: LCP 1.5s. r = +0.23.
Passing LCP per bucket every category and count level at once - color is the pass rate
Each row is a category, each column its own count bucket (few on the left, many on the right); the cell is the share of those sites passing LCP.
Has dimensions swings the hardest: 87% of sites pass LCP with few, 81% with many. computed
Few vs many - does quantity cost LCP? the pass rate with few vs many of each category
Per category: the pass rate among pages with FEW of it (hollow ring) against pages with MANY (solid dot), worst trend first. Thin buckets are excluded from the endpoints.
More Has dimensions costs the most: the LCP pass rate falls from 87% with few to 81% with many. computed
Why this matters for the Core Web Vitals, and where to start fixing it
An iframe without dimensions is a box of unknown size. The browser guesses, the embed loads, the box resizes, and everything below it jumps. That is the CLS pattern for embeds: maps, videos, forms, ads.
Reserve the slot. Width and height (or aspect-ratio on the container) make the size known before the content arrives, and the late embed lands without moving anything.
How does this affect the Core Web Vitals?
Passing CLS barely moves across the range: 80% at one end, 76% at the other. This signal does not separate passing sites from failing ones.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.