Page Speed Test
Test how fast a live URL loads — TTFB, DOMContentLoaded and full load time, Core Web Vitals (LCP, CLS), and a resource-weight breakdown by request count and transferred bytes. Runs through a real headless browser, server-side.
Input
Loaded and measured server-side through a real headless browser — takes a few seconds longer than a plain fetch.
Result
Load timing, Core Web Vitals and a resource breakdown will appear here.
Also available with
Guides
What Page Speed Test does
Enter a live URL and this tool loads it in a real headless Chromium browser, server-side, and reports how fast it actually loaded: Time to First Byte, DOMContentLoaded, and full page load time, plus Core Web Vitals — Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS) — read straight from the browser's own performance APIs. A resource breakdown shows how many requests the page made and how many bytes it transferred, grouped by type (script, stylesheet, image, font, and so on).
How to use it
- Enter the full URL of the page you want to test.
- Click Test page speed. The page is loaded and measured on our server, which takes a few seconds longer than a plain fetch.
- Read the timing metrics first — a high TTFB points at a slow server or origin, while a high load time relative to TTFB points at heavy client-side work (large scripts, unoptimized images, render-blocking resources). Check the resource table for the biggest contributors to that weight.
Reading Core Web Vitals
LCP (Largest Contentful Paint) is how long the page's biggest above-the-fold element — usually a hero image or heading — took to render; Google's own thresholds treat anything under 2.5s as good. CLS (Cumulative Layout Shift) scores how much visible content jumped around as the page loaded (images without reserved dimensions, late-injected banners); under 0.1 is good. Both are measured live during this one page load, not averaged across real visitors the way Google's own field data (CrUX) is — a single lab measurement can vary run to run with network conditions and third-party ad/analytics timing.
Scope
This is a single server-side load from one location, not a multi-region or repeated-run average, and it doesn't simulate a throttled mobile connection the way Lighthouse's mobile preset does — treat a single result as a snapshot, and re-run a borderline page a few times if the numbers matter for a decision. Bot-blocking or JS-challenge pages (Cloudflare, etc.) may report artificially fast or broken metrics, since the tool measures whatever the page actually serves it.
Privacy
The URL is fetched and rendered by our server only to produce this report, and isn't stored beyond the job's lifetime. Requests to private or local network addresses are blocked.