Domain & Website SEO Tools
Website Speed Test
Detailed timing breakdown: DNS, connect, time-to-first-byte and total load time.
- Free to use
- No sign-up
Working on it…
Running the tool — your results will appear here in a moment.
No results yet
Enter the details above and run the tool to see your results here.
About this tool
Measure how long a server takes to answer, step by step. The test breaks the request into DNS lookup, connection, time to first byte (TTFB) and total load time, so you can see exactly where the delay is.
How to use it
- Enter the URL to test.
- Run the test.
- Read the timing for each stage.
The stages explained
- DNS – finding the server's IP. Slow here? Consider a faster DNS provider.
- Connect – opening the connection, including the secure HTTPS handshake.
- TTFB – how long the server takes to start replying. High values usually point to slow hosting, heavy database queries or missing caching.
- Total – the complete download of the HTML document.
What is a good result?
As a rough guide, a TTFB under about 200 ms feels fast, 200–600 ms is acceptable, and anything above a second is worth investigating.
How it differs from Page Speed Checker
This test focuses on the server's response for the main document. Our Page Speed Checker runs a full browser test that also includes images, scripts and styles.
Limitations
Results are measured from our server's location, so visitors elsewhere may see different timings. Caches, CDNs and temporary load can change results between runs — test a few times.
A worked example
An online magazine sees a TTFB of 1.8 seconds while DNS and connection times are tiny. The delay is on the server: every page is built from scratch on each visit. Enabling full-page caching reduces TTFB to around 150 ms without changing hosts.
Where delays usually come from
- Slow DNS – a budget DNS provider or a long chain of CNAME aliases.
- Slow connect – a server far from visitors, or an outdated TLS configuration.
- High TTFB – no caching, slow database queries, heavy plugins or an overloaded shared server.
- Long total time – a very large HTML document or a slow network path.
Quick fixes
- Enable page caching in your CMS or server.
- Use a CDN to serve visitors from nearby locations.
- Upgrade PHP or your runtime to a current version.
- Move to better hosting if the server is consistently slow.
Related tools
- Page Speed Checker – a full browser performance test
- Server Status Checker – confirm the site is reachable
- Page Size Checker – check document weight
Step by step: measuring an improvement
- Run the test three times and note the average TTFB.
- Make one change, such as enabling page caching.
- Run three more tests and compare averages.
- Keep the change if it helps, and move on to the next idea.
Changing one thing at a time makes it clear what actually improved performance.