Iframe Usage
Checks iframe count and usage — too many hurts performance.
What this check measures
We count `<iframe>` elements per page and warn if more than 2-3. Iframes each carry their own overhead (separate document, own JS context, own network budget).
Why it matters
Every iframe is a mini-browser tab inside your page. 5+ iframes on a page noticeably slow down mobile. Common culprits: ads, embedded videos, chat widgets, analytics.
How our audit detects it
Count <iframe> elements per page. Flag if over 3.
Typical findings
- error_outlineBlog post with 3 video embeds + Twitter embed + chat widget = 5 iframes.
- error_outlineAnalytics using iframe-based tracking.
How to fix
Lazy-load iframes with `loading="lazy"`. Replace video iframes with lite-youtube-embed for instant-load. Consolidate chat/analytics.
Frequently asked questions
Is one iframe bad?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.