Skip to main content
RankBrain

Website Ping Test

Times five requests to a site and breaks each one into DNS, connection, TLS and first byte.

We fetch the page for you. Our server fetches the public address you enter and reads the response. Nothing you enter is stored. Free, no account.

How it works

Your site feels slow and you cannot tell where the time goes: the network, the secure handshake or the server's own work. This tool sends requests to the address you enter and times each stage on its own: DNS, connection, TLS and first byte. You see the minimum, average and maximum for each stage, and which one takes longest.

  1. 1

    We send between three and ten requests to the address and time each stage separately.

  2. 2

    You get the minimum, average and maximum for each stage, and how many requests were answered.

  3. 3

    The stage that takes longest tells you where the delay is: the network path, the secure handshake or the server's own work.

What it does not do

  • This times HTTP requests, not ICMP ping packets. Browser JavaScript has no native ICMP API; this server tool uses HTTP. For a website, the HTTP time is the one visitors feel.

  • Times are from our server to the site and include the distance between them.

When a source is busy or a site does not answer, this tool says so. It never fills the gap with a guess.

Questions

Why are the times different from my own machine?

Times come from our server, so they include the distance between our network and the site. A visitor closer to the site sees different numbers. Use the per-stage breakdown to find where time goes, not to predict exactly what one visitor in one city will feel.

Why not use a normal ping?

This sends HTTP requests, not ICMP ping packets. Browser JavaScript has no native ICMP API. Servers may support ICMP, but this tool uses HTTP to test a website's response. HTTP time is what a visitor waits for: the request goes out, the server answers, the page starts to arrive.

Which stage should I look at first?

Look at the stage with the highest minimum. If DNS or connection dominates, the delay sits on the network path between our server and yours. If TLS dominates, the secure handshake costs the most time. If first byte dominates, the server itself took long to start answering.

Tools that answer the next question

All 74 free tools