Website Speed Tester
Time how quickly a page responds from your own connection, with time to first byte, download time and HTML size across several runs.
What this tester measures
It requests the page you enter several times, one after another, and times each response from your browser. For sites that allow it, you get the time until the first byte arrived, the time to download the HTML, and the size of the HTML. For sites that do not, you still get the time until the server answered. It then reports the fastest, median and slowest run, so one unlucky request does not mislead you.
What it does not measure
A real page load also fetches images, scripts and stylesheets, runs JavaScript and draws the page. A browser page cannot see any of that for another site, so this tool times the first document request only. It is a good check of server and network responsiveness: how quickly a host answers, whether it is slower than it was yesterday, or whether a change to caching or hosting helped. For a full audit with Core Web Vitals, use a lab tool such as PageSpeed Insights or the Lighthouse panel in Chrome DevTools.
How to read the numbers
Time to first byte | How long the server and network took before any data came back. Under about 200 ms is good, over 600 ms is slow. |
Download time | The time to receive the HTML after the first byte. Large pages and slow connections raise it. |
Size | The HTML as received. Compressed size is shown when the server reports it. |
Response time | Used when the site hides details from the browser: the time until the server answered. |
The first run often includes DNS, connection and security setup, so it can be slower than the rest. Results also depend on where you are, since you are testing the distance between your device and the server. To look at how the domain resolves, use the DNS Lookup Tool, and to confirm what status the page returns, use the HTTP Status Checker.
Frequently asked
Is this the same as a Google PageSpeed test?
No. PageSpeed Insights loads the whole page in a lab browser and scores rendering, scripts and images. This tool times only the first request from your own device, so it shows how fast the server responds, not how fast the page appears.
Why can it only show some details for certain sites?
Browsers hide the details of a response from another site unless that site sends CORS headers. If it does not, this tool can still time how long the server took to answer, but it cannot read the size or split the time into stages.
Why is the first run slower than the others?
The first request has to look up the domain, open a connection and negotiate encryption. Later runs can reuse that work, so they are usually faster. The median helps smooth this out.
What is a good time to first byte?
As a rough guide, under 200 ms is good, up to about 600 ms is acceptable, and more than that suggests slow hosting, no caching, or a heavy server-side process. Distance from the server affects it too.
Is the URL sent to Curious Assistant?
No. The requests go from your browser directly to the site you enter. Curious Assistant does not see the URL or the results.