Iframe Checker
List every embedded frame with its title, loading behaviour, sandboxing and permissions.
About this tool
Lists every `iframe` on a page and reports the four things about each one that actually matter.
An iframe is a whole second page — its own document, scripts and network requests, loaded eagerly unless told otherwise. One YouTube embed fetches most of a megabyte before the visitor has decided to press play, which makes it among the most expensive elements on a typical page.
**`title`** is what a screen reader announces. Without one it says "frame", and a page with three untitled frames offers three identical entries.
**`loading="lazy"`** stops a frame below the fold downloading at all until it is scrolled to. On an embed this is the single largest performance win available.
**`sandbox`** limits what the embedded page may do. Without it a third-party frame can run scripts, submit forms and navigate the page that contains it.
**`allow`** grants access to the camera, microphone, geolocation and payment APIs. A frame with a broad `allow` is worth reading carefully.
Common questions
Does content in an iframe count for SEO?
It is attributed to the page it came from, not to the page embedding it. Anything you want indexed as yours belongs in the page itself; iframes are for other people's content.
How much does a video embed cost?
A standard YouTube iframe pulls roughly 500KB to 1MB of scripts and images before anything is played. A click-to-load placeholder — a thumbnail that swaps in the iframe when clicked — removes nearly all of it.
What should sandbox allow?
Start with sandbox="" and add back only what breaks. allow-scripts and allow-same-origin together defeat the point, because the frame can then remove its own sandbox attribute.
Do all iframes need a title?
Every one a user can reach. A hidden tracking frame is exempt, and should also carry aria-hidden. For anything visible the title is what a screen reader user gets instead of "frame".