Website Speed Test
Measure your site’s server response time, HTML size, compression, HTTP version and the page structure that affects speed.
This tool runs through our server; what you enter is not stored. Only public websites are inspected.
In short
A speed test measures how fast a page arrives from the server and how heavy it is. Time to first byte should stay under about 600 ms; large HTML, uncompressed responses and many files slow a page down.
What does the speed test measure?
The tool opens the address once from our server and measures the server response time (time to first byte), total time, HTML size, compression (gzip / Brotli), HTTP version and redirects. It counts render-blocking scripts, images without dimensions and images that are not lazy-loaded, and gives a weighted score.
The measurement is taken from our server’s location and does not download every image and script. For real-user metrics (LCP, INP, CLS) open the Google PageSpeed Insights report from the link in the result; when the site owner has configured an API key, LCP, INP and CLS are shown right in the result.
Who uses it and when?
- Site owners measuring before and after a hosting change
- Developers checking the effect of caching
- SEO specialists reporting slow pages
Frequently asked questions
Why does the result change slightly each time?
Server load, the network path and the cache state change with every request. Test a few times a few minutes apart for a stable picture.
What is a good server response time?
As a rule of thumb, under 600 ms is good and over 1.5 s is slow; page caching and good hosting lower it noticeably.