Reachability and response time, measured from your network

Enter the address of a website and your browser measures whether it can reach the site from your network and how quickly it gets an answer. The measurement starts from your computer, not from our server.

What does this tool measure?

Reachability
Whether the website answers your browser over HTTPS: that is, whether it can be reached from your internet connection.
Response time
The time between a request and its answer, over several measurements: the fastest, the typical and the slowest value.
First connection
How long a new visitor waits while the name is looked up, the connection is opened and encryption is negotiated.
Reference
The same measurement against our own site, to tell a slow website from a slow connection of your own.

Frequently asked questions

Is this the same as the ping command?

No. Ping sends ICMP packets, which a web page cannot do. This tool sends HTTPS requests and measures how long the answers take. The figure therefore includes the server's processing time on top of the network delay, and is usually a little higher than what ping reports.

Why does it measure from my computer and not from your server?

Because the question is usually whether you can reach the site. A measurement from a server would show whether the site is reachable from there, which says nothing when the fault is on your network or at your provider.

The site does not answer. What could be the reason?

For security reasons the browser does not say. The domain may not resolve, the server may be down or not accept HTTPS, the certificate may have expired, or an ad blocker or firewall may be blocking the request. Our DNS and SSL checks show from our side which of these applies.

Can it measure a route (traceroute) too?

No, that is not possible from a browser. Measure a route on your own computer with the tracert (Windows) or traceroute (macOS, Linux) command.

Have a question about the results, or need help fixing something? Contact our support