Download latency is your ping measured while a download is running. It's also called loaded latency or latency under load. It's almost always higher than your idle ping. A rise of a few tens of milliseconds is normal. A jump of 100 ms or more usually means your router or modem is holding traffic in an oversized queue, a problem known as bufferbloat.
Plain "ping" on most results means idle ping: measured when your connection is quiet. Download latency answers a more practical question: what happens to responsiveness when someone in the house is actually using the connection?
Where you'll see "download latency"
Different speed tests label it differently, but they mean the same thing:
- Speedtest by Ookla measures ping at three stages: idle, during the download test, and during the upload test.
- Cloudflare defines download latency as the round-trip time measured during an active download, and upload latency the same way for uploads. Its "unloaded latency" is the idle figure.
- FAST.com shows "unloaded" and "loaded" latency, and notes that the difference between them is also called bufferbloat.
So if your result shows idle ping of 15 ms and download latency of 180 ms, the line itself is quick. It just gets slow to respond when it's busy.
Why it's higher than idle ping
When you download a big file, data arrives at your provider's equipment faster than your line can carry it. The extra waits in a queue, or buffer. Your ping test has to wait in that same queue, behind the download.
A small queue is healthy. It smooths out bursts and keeps the line full. An oversized queue lets hundreds of milliseconds of data pile up, and every game packet, call packet and web request waits behind it. That's why a call can break up the moment someone starts a large download, even though your download speed looks great.
The bufferbloat guide goes deeper into how these queues build up.
What download latency is normal?
No standards body publishes a "normal" figure, so these are rules of thumb. Judge the gap between idle and loaded latency more than either number alone:
| Increase over idle ping | What it means |
|---|---|
| Under 30 ms | Good. Calls and games survive a busy line. |
| 30–100 ms | Noticeable. Fast games feel it, calls usually cope. |
| Over 100 ms | Bufferbloat. Expect lag and choppy calls whenever the line is busy. |
Then compare the loaded figure with what each activity tolerates. What counts as a good ping lists the ranges for streaming, calls and games. If your loaded latency stays inside them, you don't have a practical problem, whatever the idle figure says.
Upload latency is usually the worse one
Most cable, DSL, 5G and satellite plans give you far less upload than download. A single phone backing up videos can fill the upload, and the queue in the upstream direction grows quickly. So upload latency is often much higher than download latency on the same line.
That's why video calls, which send and receive at the same time, are usually the first thing to break. The guide to a good upload speed shows how quickly cameras and backups use up a typical upload.
What SpeedMetric shows
The SpeedMetric speed test reports download speed, upload speed, idle ping and jitter. It measures ping before the download starts, so it doesn't show download or upload latency. A low ping on SpeedMetric tells you the connection is responsive when it's quiet. It doesn't rule out bufferbloat.
To see loaded latency, use a test that reports it, such as the three above. You can also check it yourself on a computer:
- Open a terminal and run a continuous ping to a well-known server, for example
ping 1.1.1.1. - Note the typical time while nothing else is running.
- Start a large download or upload on the same network and watch the ping times.
If they climb by 100 ms or more and fall back when the transfer ends, you've measured download (or upload) latency, and it's high.
How to bring download latency down
Most of the fix is controlling the queue, not buying more speed.
- Turn on smart queue management if your router has it. It may be labeled SQM, Smart Queue, fq_codel, CAKE or "adaptive QoS." These keep queues short. A common rule of thumb is to set the limit a little below your measured speed, around 90–95%, so the queue stays in your router where it can be managed.
- Pause big transfers during calls and games: cloud backups, game updates, large uploads.
- Use Ethernet for the device that matters. Wi-Fi adds its own delay and variation on top of the line's.
- Check the router and modem. Ookla's own advice is that if download or upload ping is high, contact your router maker or provider. An older modem or router is a common cause.
- Then consider the plan. A bigger upload helps if you're constantly filling it, but without queue management a faster line can still bloat.
Once you've made a change, re-run the test and compare the idle and loaded numbers. The gap is the number to watch. For how download, upload, ping and jitter fit together on a result, see download, upload and ping explained, and for related symptoms see the guide to packet loss and lag.
Common questions
Is download latency the same as download speed?
No. Download speed is how much data arrives per second, in Mbps. Download latency is how long a small round trip takes while that download is running, in milliseconds.
Why is my upload latency worse than my download latency?
Most home plans have much less upload than download, so a single upload fills the line sooner and the queue in your router or modem grows faster.