A connection sold as fast can still stumble through a video call, freeze mid-sentence and drop words, while a much slower one handles the same call cleanly. Download speed, the number providers advertise, explains almost none of this. Three quieter measurements do: ping, jitter and packet loss. They describe not how much data your line can move, but how promptly and reliably each small piece arrives. Learn to read them and most lag complaints stop being mysterious, because you can see which of the three is failing and, often, why it is happening at all.
Ping, the round trip
Ping times how long a tiny probe needs to reach a distant server and come back, written in milliseconds. It is a delay, not a quantity. A line can carry huge amounts of data per second yet still answer slowly, in the same way a wide motorway does not make any single car arrive sooner. Distance sets a floor, since signals cannot outrun physics, and every router the packet passes through adds a little more.
Typical wired ping to a nearby server sits around 5 to 20 milliseconds. Cross a continent and 80 to 150 is normal; reach a satellite and it climbs past 500. Because ping counts the whole journey out and back, anything that adds queuing on the way, a congested link or an overloaded router, raises it. Newer wireless equipment trims part of this by handling many devices more efficiently, the progress the overview of the way wifi generations compare traces.
Jitter, the wobble
Jitter is not a separate delay but the variation in ping from one packet to the next. If ten packets leave evenly spaced and arrive evenly spaced, jitter is near zero. If they arrive bunched, then late, then bunched again, jitter is high even when the average ping looks fine. Real-time software cares deeply about this, because it must play sound at a steady rate and cannot wait for a straggler.
To cope, apps hold incoming audio in a small buffer and release it smoothly, trading a little delay for stability. When jitter exceeds what the buffer can absorb, you hear the result as robotic voices or clipped syllables. Wireless links are a common source, since a microwave, a neighbour’s network or a cluster of 2.4 GHz gadgets can interrupt the timing, the crowding the guide on how Bluetooth range and pairing work touches on.
Packet loss, the gaps
Packet loss counts the fraction of packets that leave but never reach the far end, shown as a percentage. Some loss is normal, and well below one percent usually goes unnoticed. Above a few percent, real-time media starts to break up. The causes fall into a few groups: congestion, where a link is full and a router discards what it cannot queue; a weak or noisy wireless signal; and faults in cabling or hardware that corrupt packets in transit.
What happens next depends on the traffic. File transfers use a protocol that notices the gap and asks for the missing piece again, so the data survives but the transfer slows. Live calls cannot wait for a resend, so a lost packet is simply gone, heard as a dropout. On wifi, weak coverage is a frequent culprit, which comes down partly to aerials, the ground the guide on what a router’s antenna count means covers.
A quick reference
The four figures below are easy to confuse, so it helps to see what each one actually reports and what tends to spoil it.
| Measure | What it reports | Usual unit | What worsens it |
|---|---|---|---|
| Ping | Round-trip delay | Milliseconds | Distance, extra hops, queuing |
| Jitter | Variation in ping | Milliseconds | Interference, congestion |
| Packet loss | Packets that never arrive | Percent | Full links, weak signal, faults |
| Bandwidth | Data moved per second | Megabits | Shared use, plan limits |
Why a call breaks before a download does
Downloads are elastic. The software behind them expects delay and loss, recovers quietly, and only cares that the file eventually completes. A one-second stall means the download finishes one second later, and nobody notices. Bandwidth is what limits it, so a fast line genuinely helps here.
A voice or video call is the opposite. It produces a steady stream that must arrive on time and in order to be useful, and it cannot rewind. High ping adds an awkward pause before each reply; jitter scrambles the timing; loss punches holes in the audio. None of these depends on how many megabits the line can carry, which is why a connection with plenty of headroom can still deliver a poor call while a modest one sounds fine.
Measuring the three yourself
The built-in ping command is the quickest start. Running it against a well-known server shows the round-trip time for each packet, an average, and the percentage lost. Let it run for a minute rather than a few packets, and watch how much the times vary; that spread is your jitter in practice. Online speed tests report all three alongside bandwidth, and many routers and calling apps show live figures during a session.
Test methodically. Compare a wired connection against wifi to see how much the wireless leg adds, and repeat the check while the problem is happening rather than afterwards. If the numbers only fall apart on wifi, the fix lives near the radio, not the line. Moving a struggling device onto a wired or wired-style path often steadies all three, one reason the comparison of powerline, MoCA and mesh links is worth reading.
Reading the three together
No single number tells the whole story. A low ping with high jitter still ruins calls; light packet loss on top of a long round trip pushes a marginal connection over the edge. The habit worth building is to glance at all three at once and ask which is out of line, because the offender points to the cause. High loss on wifi suggests coverage or interference; high ping everywhere suggests distance or a congested route.
Bandwidth still matters for large transfers and many simultaneous streams, so it has not stopped being relevant. It is simply the wrong tool for diagnosing lag. Once ping, jitter and loss are part of how you look at a connection, upgrades and fixes get easier to choose, because you are treating the fault you measured rather than the one the advertising implied you had.
Frequently asked questions
What is a good ping?
For a nearby server over a wired link, anything under about 20 milliseconds feels immediate and suits gaming and calls. Up to 50 is comfortable for most uses, and 50 to 100 is workable but noticeable in fast games. Beyond 150 the delay becomes obvious in conversation. Distance sets a hard floor, so a ping to another continent will always be higher than one across your own city.
What is jitter?
Jitter is how much the ping varies between consecutive packets rather than its average value. Steady arrivals mean low jitter; times that jump around mean high jitter. It matters for anything live, because voice and video need packets spaced evenly to reassemble into smooth sound and picture. A good connection keeps jitter in the low single-digit milliseconds; figures above about 30 usually start to make calls sound broken.
Why do my calls drop on fast internet?
Because call quality depends on timing and reliability, not raw speed. A line with high download figures can still carry jitter and packet loss, often on the wifi leg, and those directly damage live audio while leaving downloads untouched. Interference, weak coverage or a congested router are common causes. Test ping, jitter and loss during a bad call, and compare wired against wireless to find where the timing falls apart.
