Website speed test
We open your page in a real browser on a phone and a desktop, and measure what your visitors wait for: the first paint, the main content, the jumps, every heavy file.
What it checks
- Server response timeNothing can render until the first byte arrives. A slow server makes every other optimisation irrelevant.
- HTTP/2 or HTTP/3Loads many files at once over one connection. HTTP/1.1 queues them six at a time.
- Text compressionHTML, CSS and JS shrink by 70–80% with gzip or Brotli. Without it every visitor downloads the difference.
- HTML sizeA huge document is slow to download and slow to parse, before a single image has loaded.
- Redirect chainEach hop is a full round trip before the page even starts loading.
- Number of requestsEvery script, style and image is a request; past a few dozen the queue itself is the delay.
- Render-blocking scriptsA script in <head> without defer or async stops the page from painting until it has downloaded and run.
- Lazy-loaded imagesImages below the fold need not load before the page is usable.
- Browser cachingA returning visitor downloads every script and style again unless the server said to keep them.
- Minified CSS and JavaScriptWhitespace and comments are bytes the visitor downloads and the browser throws away.
- Image optimisationImages are most of a page's weight. Oversized files, old formats and missing dimensions each cost visible seconds.
- Largest Contentful PaintThe moment the main content — the hero image or the headline — is on screen. The number Google ranks page experience by, and the one visitors feel.
- First Contentful PaintWhen anything at all appears. Until then the visitor stares at a blank screen and wonders whether the link worked.
- Cumulative Layout ShiftHow much the page jumps while it loads. A jump under a finger is a tap on the wrong thing.
- Total Blocking TimeHow long scripts keep the page from answering a tap or a scroll — the lab measure of how responsive it feels.
- Total page weightEverything a visit downloads on a phone: every image, script, font and style. On mobile data it is time and money.
- Third-party loadEvery outside server — analytics, ads, chat, fonts — is a connection, a delay and someone else's outage you inherit.
Questions
Why is my score different from Google PageSpeed?
PageSpeed simulates a slow phone on a throttled network; we measure a real Chromium from our server. Both are lab numbers — use either to compare before and after a change, not against each other.
What is a good load time?
Google calls the main content appearing within 2.5 seconds good, and the page moving less than 0.1 of its size stable. The report shows each on that scale.
What speeds a site up most?
Usually three things: a faster server response, smaller images in modern formats, and fewer scripts running before the page shows. The report names which one is yours.
We only read what a public visitor could. Nothing is submitted to your site and no vulnerability is exploited — findings are what your site shows, not what we tried.