A live server-response test
The server requests the public URL, records network timing from this hosting location, follows a limited number of safe public redirects and reports response headers and transfer size. No Google API key is required.
This website speed test measures how quickly a public page responds on the server side, without needing a Google API key. It suits site owners checking a page after a redesign or a hosting move, and WordPress users trying to find out whether a slow page is a server problem, a page problem or both.
How to test a page
- Enter the address of a public page into the Website URL field.
- Press Run check and wait while the server requests the page.
- Read the timings first: DNS, connection, TLS, time to first byte and total response time.
- Then check the supporting detail — redirects, transfer size, compression and cache headers — for the cause behind a slow result.
Why test the server response first?
Most slow pages have a cause that shows up in the server timings before anything else. This check helps you separate the usual suspects:
- A slow time to first byte points at the server or hosting — the page is taking too long to even start responding.
- A large transfer size points at uncompressed images, scripts or stylesheets being sent in full.
- Missing compression or cache headers are quick wins — the same content sent smaller, or reused instead of re-downloaded.
- Redirect chains add round trips — each hop costs time before the real page even starts loading.
What this test does not measure
Be clear about the limit: this is a server-response test, not a browser test. It does not render the page the way Chrome does, so it cannot measure Core Web Vitals such as LCP, INP or CLS — those describe how a page feels in a real browser, and need a lab or field test such as PageSpeed Insights. Timings also depend on where the test runs from, how the page's CDN routes the request and how busy the server is at that moment, so run the same page more than once before drawing conclusions. Use this page to find server-side problems, then use PageSpeed Insights or Search Console for the full browser-side picture.
Frequently asked questions
What does this website speed test measure?
It records server-side timings for a public page — DNS lookup, connection, TLS handshake, time to first byte and total response time — plus redirects, transfer size, compression and cache headers.
Is this the same as PageSpeed Insights?
No. PageSpeed Insights renders the page in Chrome and reports Core Web Vitals such as LCP, INP and CLS. This test measures the server response only, which is the part of speed your hosting controls most directly.
Why do my results change between runs?
Server load, CDN routing and caching all change from minute to minute. A page served from cache can be much faster than the same page built fresh, so test more than once and look at the pattern, not a single run.
What is TTFB and why does it matter?
Time to first byte is how long the server takes to start responding after the request arrives. A slow TTFB usually points at the server, the hosting plan or a heavy page build, rather than at images or scripts.
Can it test pages that need a login?
No. Only public pages can be tested. Private networks, localhost addresses and pages behind a login are blocked.