What Is Latency? Latency vs Ping vs Bandwidth Explained
Quick answer
Latency is the delay between asking for data and it starting to arrive, measured in milliseconds. It decides how responsive the internet feels — games, calls, page loads — while bandwidth decides how much data can flow at once. Ping is the measurement you use to put a number on latency.
Latency in one sentence
Latency is waiting: the time between "give me that" and the first of it arriving. Picture a water pipe — bandwidth is how much flows per second once the tap is open; latency is how long the first drop takes to reach you after you turn it. A wide pipe (fast plan) with a long wait (high latency) still feels sluggish every time something new is requested, and almost everything you do online — every click, every tap — starts something new.
Latency vs ping vs bandwidth
The three words get used interchangeably, but they answer three different questions:
| Latency | Ping | Bandwidth | |
|---|---|---|---|
| What it is | The delay itself | The measurement of that delay (round trip, ms) | The capacity of the link (Mbps) |
| Question it answers | How long before data starts arriving? | What number did we measure? | How much can arrive per second? |
| It decides | Responsiveness | — (it's the reading, not the thing) | Streaming quality, download times |
| Feels bad as | Delay, lag, talking over each other | — | Buffering, long downloads |
So "ping" and "latency" are two views of the same thing: latency is the delay, ping is the tool and the number that measures it. People say "high ping" to mean "high latency". For what counts as a good number — and the full guide — see what is ping.
Where latency comes from
Delay isn't one thing; it's accumulated along the whole path between you and a server:
- Distance. Signals travel fast but not instantly; every kilometre to the server adds waiting you cannot remove. This is why the server's location shows up in your results.
- Hops. Each router your data passes through looks at it and forwards it — a small delay each time, multiplied by every hop.
- The last metre. Wi-Fi adds a few milliseconds and some waiting for airtime; a cable doesn't. See Wi-Fi vs Ethernet.
- Queues. When the connection is busy, new packets wait behind bulk traffic. This is the biggest hidden source of latency in homes — bufferbloat — and the one you can fix yourself.
- The connection type. Satellite adds the round trip to orbit; older DSL interleaves data for stability at the cost of delay. Fibre and cable are usually the lowest.
Why latency matters more than you'd think
Loading a page is dozens of small requests; each one pays the latency cost before any bandwidth helps. On a high-latency connection, pages start late no matter how many megabits you have. The places it bites hardest: online games, where you see opponents where they were; video calls, where people talk over each other because pauses arrive late; remote desktops and cloud gaming, where every keystroke waits for a round trip.
Downloads and streams barely care — they ask once and then flow. That's the shape of a common mismatch: "my speed test says 300 Mbps but everything feels slow" usually means latency, jitter (latency that moves around — what is jitter), or loss (how to fix packet loss), not bandwidth.
Does a faster plan lower latency?
Usually not. Distance, hops and queues don't shrink because the pipe got wider — upgrading 100 Mbps to 1 Gbps rarely changes your ping to the same server. The exception is a connection so full that queues never drain: there, extra capacity shortens the waits. In general, if you want lower latency, the fixes are a cable, SQM/QoS on the router to stop bufferbloat, and nearer servers: how to lower ping in games.
Measure your latency
The ping test pings a nearby server four times a second for 30 seconds and shows median, minimum, maximum and jitter on a live chart. Run it while the house is quiet, then again during a big download — the difference is bufferbloat, and the bufferbloat test grades exactly that from A to F.