See a real, full browser-rendered load — not just server response time.
This loads the real page in a hidden frame and times how long the browser takes to fully finish loading it, including images, styles and scripts — unlike our Website Speed Test, which only measures server response time for the base HTML.
Page Load Time Analyzer measures how long a browser genuinely takes to finish loading an entire page — HTML, CSS, JavaScript, images and all — rather than just the time to receive the first response byte. This is a meaningfully different measurement from our Website Speed Test tool, which deliberately measures only server response time for the base document; this tool measures the complete, real, rendered load experience a visitor actually has.
The tool loads your target URL inside a hidden, sandboxed iframe and starts a high-resolution timer the instant the request begins. The browser's native onload event for that frame fires only once every sub-resource referenced by the page — every image, stylesheet, script and font — has finished loading, exactly matching what a real visitor's browser experiences. The elapsed time between those two points is your full page load time.
Many websites deliberately send an X-Frame-Options or Content-Security-Policy: frame-ancestors header specifically to prevent being loaded inside another page's frame — this is a legitimate, common security measure against clickjacking attacks, and it's completely outside this tool's control. When that happens, the frame simply never fires its load event, and after a short wait the tool tells you plainly rather than reporting a fake number, and suggests the response-time-only Speed Test as a fallback for that URL.
A full load under roughly 2 seconds is generally considered good for typical content pages; times over 4 seconds are worth investigating, usually starting with unoptimized images, render-blocking third-party scripts (analytics, chat widgets, ad tags), or an uncompressed asset pipeline. Since this measurement reflects your own current network and location, running it a few times — and comparing against results from a different network — gives a more complete picture than any single run.
Speed Test measures only the time to receive the base HTML response; this tool measures the complete load including every image, script and stylesheet the page references — a fuller, usually larger, number.
That site is very likely sending a frame-blocking security header, which is standard practice for a large share of the web and has nothing to do with the site being broken.
No — it measures total load completion time only. For detailed Core Web Vitals scoring, a dedicated lab tool that has deeper access to the page's rendering internals is needed.
Not exactly — caching (both browser and CDN), current server load, and your own network conditions all cause natural variation between runs; treat the result as a representative sample, not a fixed constant.
Yes — the frame is sandboxed with restricted permissions, and it performs the same kind of read-only page load your browser does for any normal visit.
Idiot Website Tools