Measures page weight, request count & load time by fetching the page and its resources
Checks up to 20 images/scripts/stylesheets referenced by the page. Not a full browser render (no JS execution timing, no Core Web Vitals) — this measures raw network weight and request count.
A page speed analyzer fetches a page and its resources to measure how heavy and how fast-loading it is — total size, number of requests, and a handful of common speed-related issues.
Enter a URL.
Press "Analyze."
Review the score, weight breakdown, and heaviest resources.
Yes — there's no paywall, no watermark, and no sign-up required.
No. Google's tool runs a real browser and reports Core Web Vitals — LCP, CLS, INP — based on actual rendering and interaction timing. This tool fetches the raw HTML and its resources directly over HTTP and measures network weight, request count, and a few static-HTML heuristics. No browser, no rendering, no JavaScript execution happens here.
Seven checks, each weighted by how much it typically affects speed. A pass earns its full weight, a warning earns half, and a fail earns none — the score is the total earned as a percentage of what was possible.
"Weight by type" groups everything fetched into HTML, image, script, and stylesheet totals. "Heaviest resources" lists the five single biggest files — usually the fastest place to look for an easy win.
Only the first 20 images, scripts, and stylesheets found in the page are fetched and measured, to keep each analysis fast. If a page references more than that, its true total weight and request count can be higher than what's reported here.
Yes — the page is fetched and analyzed for that one request and isn't saved anywhere. No account or sign-up is required to use it.
A quick way to spot obvious weight problems without a full performance-monitoring subscription.
Find the images actually dragging a page's weight down.
Check for render-blocking scripts sitting in the head.
Compare total weight before and after a theme or template change.
Yes — there's no paywall, no watermark, and no sign-up required.
No. Google's tool runs a real browser and reports Core Web Vitals like LCP, CLS, and INP. This tool fetches the raw HTML and its resources directly and measures network weight, request count, and a few static-HTML heuristics — no real rendering happens.
HTML load time, total page weight across all resources, number of requests, render-blocking scripts in <head>, whether HTML is compressed, oversized images, and images missing explicit width/height.
It's a cap to keep each analysis fast. If a page has more than 20 images, scripts, and stylesheets, only the first 20 discovered are measured, so a very resource-heavy page's true weight can be higher than what's reported.
Different tools measure different things, so scores between tools won't match. This one measures raw network weight and static markup — treat it as one signal, not a final verdict.
No. The page is fetched and analyzed for that one request and isn't saved anywhere.