For online games, video calls and cloud gaming, ping matters more than download speed once you have enough Mbps for the activity. For downloads, streaming and backups, download (or upload) speed matters more and ping barely registers. Neither number wins everywhere. The useful question is which one your activity is waiting on.
What each number actually measures
Download speed, in Mbps, is how much data the connection can move each second. Ping, in milliseconds, is how long one small message takes to reach a server and come back. Jitter is how much that ping varies from one message to the next. The download, upload and ping guide covers each metric in more depth.
A highway is a decent picture. Mbps is the number of lanes. Ping is how far away the destination is. More lanes let more cars through per minute, but they don't make any single trip shorter. A moving truck (a 50 GB game) cares about lanes. A courier with one envelope (a game's position update) cares about distance.
When ping matters more
Anything that sends small pieces of data back and forth and waits for a reply is limited by ping:
- Online games. The game sends short, frequent updates about where you are and what you did. The size is small. What you feel is the delay before the server reacts. Our ping guide for gaming has the target ranges.
- Video and voice calls. Each call needs only a few megabits. Zoom, for example, recommends 3.8 Mbps up and 3.0 Mbps down for 1080p. Delay and jitter are what cause talking over each other, robotic audio and frozen faces.
- Remote desktop and remote work tools. Every click waits for a round trip.
- Web browsing, partly. A page is dozens of small requests, and each one needs at least one round trip before data flows. On a fast line, a high ping is often why pages feel slow to start.
Cloud gaming needs both. NVIDIA's GeForce NOW asks for 25 Mbps for 1080p at 60 fps and also requires less than 80 ms of latency to its data center. Meet one requirement but not the other and the stream suffers.
When download speed matters more
Anything that moves a lot of data and doesn't need instant replies is limited by Mbps:
- Streaming video. The player buffers ahead, so a 60 ms ping is invisible. What matters is sustaining the bitrate: Netflix recommends 15 Mbps per 4K stream.
- Game, app and system downloads. A 50 GB game takes about 67 minutes at 100 Mbps and about 13 minutes at 500 Mbps (50 × 8,000 megabits ÷ Mbps, best case). Ping changes almost nothing here.
- Several people at once. Four streams and a download share one pipe. Running out of Mbps is what makes everything slow down together.
- Uploading. Cloud backups, video uploads and live streaming depend on upload Mbps, which is often far lower than download.
Why a faster plan rarely lowers ping
Much of ping is distance. Light in optical fiber covers roughly 200,000 km per second, so a server 1,000 km away costs at least 10 ms for the round trip (2,000 km ÷ 200,000 km/s = 0.01 s) before any router adds its own delay. Upgrading from 100 Mbps to 1 Gbps doesn't move the server closer.
The exception is a full connection. When something saturates your upload or download, the router or modem queues packets, and ping can jump from 20 ms to several hundred. That is bufferbloat. Here more Mbps can help, because the line fills less often. A router with good queue management can help more. Wi-Fi also adds delay and jitter of its own, which is one reason Wi-Fi tests slower than Ethernet.
Which one fits your situation
| What you're doing | Usually limited by | What to check first |
|---|---|---|
| Competitive online games | Ping and jitter | Ping to the game's region, Wi-Fi vs cable |
| Video calls | Upload, jitter, delay under load | Upload Mbps and what else is uploading |
| Cloud gaming | Both | Mbps for the resolution and ping to the data center |
| 4K streaming on several TVs | Download Mbps | Total Mbps across all screens |
| Game and app downloads | Download Mbps | Mbps on a wired device |
| Backups and video uploads | Upload Mbps | Upload result |
How to tell which one is limiting you
- Run a speed test on a quiet connection. SpeedMetric's speed test measures download, upload, idle ping and jitter in your browser. Test on Ethernet if you can, so Wi-Fi doesn't muddy the result.
- Compare Mbps with what the activity needs. If your download is well above the service's published figure and the problem is lag, more Mbps won't fix it. Look at ping and jitter instead.
- Check whether it only happens when the line is busy. If calls and games are fine until someone starts a big upload or download, the problem is latency under load. SpeedMetric shows idle ping only. It doesn't measure latency under load, so check it yourself: run a continuous
pingto any well-known host in a terminal, start a large upload, and watch whether the numbers climb. - Consider packet loss. SpeedMetric doesn't measure packet loss either. If ping looks fine but the game still teleports you, check the game's own network stats and read packet loss, jitter and lag.
As a rule of thumb, once a connection has enough Mbps for what everyone in the home is doing at the same moment, extra Mbps stops improving games and calls. From there, lower and steadier ping is what you'll feel.
Common questions
Is 20 ms ping on 50 Mbps better than 80 ms ping on 500 Mbps?
For playing online games and taking calls, yes: the 20 ms line will feel more responsive. For downloading the game or streaming on several TVs at once, the 500 Mbps line wins.
Is jitter more important than ping?
For calls and games, steady delay matters as much as low delay. A line that sits at 40 ms with little jitter often feels better than one that swings between 15 ms and 120 ms.