Website Speed Checker
Measure how quickly a site's server responds and delivers its HTML, broken down step by step, with practical suggestions where something is slow.
- Encrypted connection
- No sign-up
- Free to use
Timing breakdown (median of 3 runs)
Response
Recommendations
How to use Website Speed Checker
- Enter the address of the page to test.
- Select Test speed. The page is requested three times and the median is reported.
- Look at the timing breakdown to see whether DNS, connection, TLS or the server itself is the slow part.
- Review the page weight, compression and resource counts, then act on the recommendations.
Website Speed Checker features
Step-by-step timing
DNS lookup, TCP connection, TLS handshake, time to first byte and download, shown as a waterfall.
Median of three runs
Reduces the effect of a single slow request.
Overall grade
A simple rating based on time to first byte and total load time of the HTML.
Page weight and compression
HTML size, whether gzip or Brotli is used and the HTTP version.
Resource count
Number of scripts, stylesheets and images the page references.
Actionable suggestions
Specific notes when a measurement is outside a healthy range.
When to use Website Speed Checker
- Checking whether a slow site is caused by the server or by the page itself.
- Comparing hosting providers or a site before and after enabling caching.
- Verifying that compression and HTTP/2 are enabled after a server change.
- Monitoring response time during a launch or traffic spike.
Website Speed Checker FAQ
What is time to first byte (TTFB)?
The time from sending the request until the first byte of the response arrives. It covers network latency plus the time the server spends generating the page. Under 200 ms is excellent, under 800 ms is acceptable, and anything above 1.8 seconds needs attention.
Does this measure Core Web Vitals?
No. Metrics such as Largest Contentful Paint require loading the page in a real browser with all its images and scripts. This tool measures the server and network part, which is the foundation those metrics build on. Use your browser's Lighthouse panel or PageSpeed Insights for in-browser metrics.
Where is the test run from?
From our server, so results reflect the distance between it and the site. Visitors far from the site's server will see longer connection times; a CDN reduces that.
Why does the first run sometimes look slower?
Caches warm up and connections are established on the first request. That is why the median of three runs is reported.
How can I reduce TTFB?
Cache rendered pages, optimise slow database queries, use a faster host or more resources, and serve visitors from a CDN close to them.
Where loading time goes
Before a browser can show anything, several steps happen in sequence. The domain name is resolved to an address, a connection is opened, a secure TLS session is negotiated, the request is sent and the server builds a response. Only then does the HTML start to arrive. Each step adds latency, and the waterfall view shows which one dominates.
A slow DNS or connection time points at the network or hosting location. A slow TLS handshake can mean an outdated server configuration. A long wait for the first byte almost always means the server is doing too much work per request, which caching usually fixes. A long download time for the HTML suggests the document itself is too large or not compressed.