You pay for 500 Mbps, the speed test confirms it, and yet your video call freezes, your game lags and pages take a while to start loading. That's because Mbps measures only one thing: how much fits through the pipe. Whether the internet feels fast also depends on how long each packet takes, whether that time is stable, and whether any packets get lost along the way. This guide explains those three measurements and how to test them.
Speed is not the same as quality
Think of your connection as a highway. The speed you pay for (bandwidth) is the number of lanes. Ping is the travel time. Jitter is how much that time varies from one car to the next. Packet loss is cars that never arrive. A ten-lane highway full of potholes is still bad if you need to get there fast and on time.
Downloading a large file depends almost entirely on bandwidth. Online games, video calls, internet voice calls and remote access, on the other hand, send small packets all the time and depend much more on ping, jitter and loss.
The three measurements that matter
Ping (latency)
It's the time, in milliseconds (ms), that a packet takes to reach a server and come back. Lower is better. Physical distance matters a lot: a server on the other side of the continent will always have higher ping than one in your city, no matter how good your connection is.
Jitter (variation)
It's the difference between one ping and the next. If replies come back at 20, 21 and 19 ms, jitter is low. If they come back at 20, 90 and 35 ms, it's high. Voice and video suffer a lot from jitter: audio sounds robotic or choppy, even when the average ping looks fine.
Packet loss
It's the percentage of packets that were sent and never got a reply. On a healthy connection, 0% is normal. Small but constant losses already cause stutters in games, dropped calls and slow websites, because the data has to be resent.
What values are good
There's no official number, but these ranges are a useful reference for home use:
- Ping: up to 50 ms is great for almost everything; 50 to 100 ms works well for most uses; above 150 ms, competitive games and calls start to suffer.
- Jitter: below 10 ms is excellent; up to 30 ms is still acceptable for voice and video; above that, dropouts appear.
- Loss: 0% is what you should expect; up to 1% may go unnoticed; above 1 to 2%, the problem shows up in everyday use.
Always compare against the same destination. High ping to a server in another country may simply be distance, not a fault.
How to measure
In the browser
The ping test sends several packets to the address you choose and shows the minimum, average and maximum latency, plus packet loss. The gap between minimum and maximum already gives a good idea of jitter. One important detail: the test runs from our server, which is in Miami (USA), so it measures the path between there and the destination. To measure your own connection, also use your computer's terminal.
In the terminal
On Windows, open Command Prompt and run a long ping:
ping -n 50 8.8.8.8
On Linux or macOS:
ping -c 50 8.8.8.8
At the end you'll see a summary with lost packets and the minimum, average and maximum times. Run the test at different times of day, including the evening, when your ISP's network is usually busiest.
Finding where the problem is
If ping is bad, the next step is to find out which segment is to blame. Ping your router (usually 192.168.0.1 or 192.168.1.1). If it already shows variation or loss, the problem is inside your home: Wi-Fi, cabling or the router itself. If the router responds well but the external destination doesn't, the problem is from your ISP outward. A traceroute shows hop by hop where latency rises; the guide how to read a traceroute helps you interpret the result without falling into the common traps.
What to do when the numbers are bad
- Test with a cable: Wi-Fi is the most common cause of jitter and loss. If everything improves on a cable, tune your Wi-Fi: move the device closer, prefer the 5 GHz network and avoid thick walls.
- Check who's using the network: downloads, cloud backups and high-resolution video on other devices fill the router's queue and raise everyone's ping.
- Restart the router: it fixes temporary glitches, but if the problem keeps coming back, look for the cause.
- Turn on QoS, if your router has it: it prioritizes games and calls over downloads.
- Keep records and contact your ISP: save ping results from different times of day, taken on a cable and with the router responding well. That shows the problem is on their network.
For a step-by-step focused on latency, see the guide high ping: causes and how to lower it.
Summary
Mbps tells you how much fits; ping, jitter and loss tell you how the data arrives. A truly good connection has low ping to nearby destinations, small jitter and zero loss. Measure on a cable, at different times, separate your home network from your ISP's network, and only then draw conclusions.