Free website speed test online
A slow website loses visitors and Google rankings. Check your server response time, page size and compression, and get specific advice on what to fix.
What the speed test measures
The test downloads the page from our server and times every stage of the response: DNS lookup, connection, TLS handshake, the time until the server sends the first byte (TTFB) and the full download. It also reads the size of the HTML, whether the response is compressed with gzip or Brotli, whether caching headers are set and which HTTP version the server agreed to.
It measures the server side of speed, the part that hosting and configuration control. It does not render the page in a browser, so images, scripts and fonts loaded by the page are not timed, and Core Web Vitals such as LCP are not measured. For those, use PageSpeed Insights alongside this test.
How to read the speed result
- Server response (TTFB): under 200 ms is excellent, up to 800 ms is acceptable, above 800 ms we flag it. A high TTFB means the server builds the page slowly: weak hosting, no page cache or heavy code.
- Compression: should show gzip or br. Disabled means text is sent raw and transfers several times slower.
- Cache headers: Cache-Control or Expires let browsers reuse files on repeat visits.
- Protocol: HTTP/2 and HTTP/3 load many files in parallel over one connection; HTTP/1.1 is flagged as outdated.
- Page size: the HTML document alone. More than 2 MB of HTML is unusual and usually means inline data or a bloated page builder.
- You can also test a single file: paste the full URL of a CSS or JS file to see whether it is compressed.
Related errors and guides
- How to enable gzip and Brotli compression
- How to reduce TTFB on shared hosting
- How to enable HTTP/2 on your hosting
- Compression is on but PageSpeed still warns
- What TTFB is
Frequently asked questions
- Why does my result differ from PageSpeed Insights?
- PageSpeed loads the whole page in an emulated phone and scores what the visitor sees. This test looks at the server response only. A site can have a fast server and a heavy page, or the other way round, so the two tools answer different questions.
- Where is the test run from?
- From our server in Europe. Visitors far from your hosting will see longer connection times; a CDN closes that gap.
- Why does TTFB change between runs?
- The first request after a quiet period often hits a cold cache or a sleeping PHP process. Run the test two or three times: if only the first run is slow, set up page caching; if every run is slow, the server itself is the bottleneck.