What is a good ping? Latency explained in plain English

Ping measures how long a small packet takes to travel to a machine and come back. Nothing else. It does not measure how much data your connection can carry, how fast a web page renders, or how good your Wi-Fi is. It is the round-trip time of the network path, and it is set mostly by distance and routing.

The numbers, and what they feel like

• Under 20 ms — same city or same country over a well-peered network. Everything feels instant.
• 20–50 ms — regional. Perfect for competitive gaming and video calls.
• 50–100 ms — continental or transatlantic. Fine for calls; noticeable in twitch shooters.
• 100–200 ms — intercontinental, or a mobile network. Video calls develop that half-second of talking over each other.
• Over 200 ms — satellite, congestion or badly routed traffic. Interactive use is uncomfortable.

Why bandwidth does not fix latency

This is the part that surprises people who have just paid for faster broadband. Bandwidth is the width of the pipe; latency is the length of it. Upgrading from 100 Mbps to 1 Gbps makes large downloads finish sooner and does almost nothing to your ping, because the packet still has to travel the same distance through the same routers. A video call needs about 2 Mbps and a low, stable latency — which is why calls stutter on a fast connection with a congested uplink.

Jitter is the number nobody quotes

Jitter is the variation between consecutive round trips. A connection with a steady 90 ms ping delivers better calls than one that swings between 20 ms and 200 ms, because every real-time protocol buffers against the worst case it has recently seen. If your ping results show a large gap between minimum and maximum, you have congestion or a struggling Wi-Fi link — not a distance problem, and not one that a faster plan will fix.

Packet loss: the real culprit

Loss above 1–2% is worse than high latency. TCP responds to loss by retransmitting and backing off, so a lossy line feels sluggish for everything, and voice and video develop dropouts. If you see sustained loss on a wired connection, suspect the cable, the router, or the line itself — in that order, because that is the order of how cheap they are to test.

Why some hosts never answer a ping

If a ping test returns nothing at all, the host is very often fine. ICMP is routinely blocked or rate-limited: most Cloudflare-fronted sites, many cloud load balancers and plenty of corporate firewalls simply drop it. That is why a sensible availability check does not rely on ping alone. If ping fails but the HTTP check succeeds, the site is up and ignoring pings on purpose.

How to actually improve your ping

1. Use a cable. Wi-Fi adds a few milliseconds at best and tens of milliseconds of jitter under contention. This is the single biggest win for most homes.
2. Pick a closer server. For gaming, region selection matters more than any hardware you can buy.
3. Turn off the VPN for latency-sensitive traffic. Every VPN adds a detour, sometimes across a continent.
4. Check what else is on the line. A cloud backup or a game update saturating the uplink wrecks latency for everything else; most routers can prioritise traffic to fix this.
5. Do not buy "gaming" hardware for latency. Nothing in your house changes the speed of light or the route your ISP takes.

Ping is not page speed

A site can have a 5 ms ping and take four seconds to load, because everything that matters happens after the network round trip: the server building the page, the database, the JavaScript. If you are diagnosing a slow website rather than a slow connection, the response time breakdown is the tool you want — it separates network time from server time so you know which one to blame.