Your download speed looks great but calls glitch and games lag? Jitter and packet loss, not bandwidth, are usually why. Here is what causes them.
A 500 Mbps connection can still deliver robotic audio on a call, stuttering video, and rubber-banding in a game — because bandwidth measures how much data your line can move, not whether each piece of it arrives on time and intact. The two culprits behind a fast line that feels slow are jitter (inconsistent delay) and packet loss (data that never arrives at all). Neither shows up in the headline download number, and both matter more than bandwidth for anything happening in real time.
Key Takeaways
- Jitter is variation in latency, not raw speed — a connection can have low average ping and still feel bad if that ping swings wildly between packets.
- Packet loss means data never arrives and has to be retransmitted or dropped outright, which is worse for real-time apps than merely slow delivery.
- Both are usually caused by congestion, Wi-Fi interference, or an overloaded router — the same everyday culprits, not necessarily your ISP.
- VoIP, video calls, and gaming are the most sensitive use cases, because they can't buffer around bad timing the way streaming video can.
- A speed test surfaces both numbers alongside bandwidth, which is why the download figure alone is an incomplete picture of quality.
Jitter: latency variation, not raw speed
Latency (ping) is how long one packet takes to make a round trip. Jitter is how much that travel time varies from one packet to the next. RFC 3550, the standard behind real-time audio and video delivery over IP, defines jitter as the statistical variance in packet interarrival time — in plain terms, how unevenly spaced your packets are when they show up.
A connection with a steady 25 ms ping is easy to work with, even if 25 ms isn't especially fast: everything downstream can predict when the next packet lands. A connection that swings between 10 ms and 90 ms is harder to work with even though its average might look identical, because nothing arrives when expected. That unpredictability is what produces choppy audio, frozen video frames, and characters that teleport in a game rather than moving smoothly.
Jitter is easy to miss because most consumer speed tests either bury it in an "advanced" tab or skip it entirely — the headline numbers are download and upload, which say nothing about timing consistency.
What causes packet loss
Packet loss is a separate problem: a piece of data leaves your device (or the server) and simply never arrives. The network doesn't slow it down — it drops it, usually because something in the path is overwhelmed. Common causes:
- Network congestion — a router or link along the path is handling more traffic than it can queue, and it starts discarding packets rather than delaying them indefinitely.
- Wi-Fi interference — walls, distance from the router, and competing 2.4 GHz devices (microwaves, other networks) corrupt wireless packets, which get discarded rather than repaired.
- Faulty or aging hardware — a failing cable, a worn connector, or an overheating router can drop packets even on an otherwise idle network.
- Route instability — if traffic between you and a server bounces across a congested or misconfigured hop, packets can be lost mid-route, outside your home network entirely.
- Overloaded ISP infrastructure — during peak hours, a shared local segment can hit capacity and start shedding packets for everyone on it.
For protocols like TCP (most web traffic), lost packets get retransmitted automatically, which you experience as things taking longer than they should. For real-time protocols like VoIP, there usually isn't time to retransmit — a lost packet just means a small gap or glitch in the audio or video, because waiting for a resend would make the delay worse than the loss.
Impact on VoIP, gaming, and video calls
Bulk transfers like downloads and video streaming tolerate jitter and modest packet loss well, because they buffer ahead of what you're watching — a few milliseconds of unevenness gets smoothed out before you ever notice. Real-time interaction doesn't have that luxury:
| Use case | What jitter does | What packet loss does |
|---|---|---|
| VoIP / voice calls | Choppy, robotic, or delayed audio | Dropped syllables, silent gaps |
| Video calls | Frozen frames, audio/video drift out of sync | Blocky video, frozen picture |
| Online gaming | Rubber-banding, inconsistent hit registration | Teleporting characters, rejected inputs |
| Streaming video | Rarely noticeable — buffered ahead | Occasional pixelation if severe |
The pattern is consistent: the more a use case depends on this instant rather than a buffered-ahead instant, the more jitter and packet loss dominate the experience — often even when the connection's bandwidth is generous and the average ping looks fine.
How a speed test surfaces both
A good speed test doesn't stop at download and upload — it measures latency, jitter, and often packet loss in the same run, because that's the combination that predicts how a connection actually feels for calls and games, not just how fast a file transfers. Run BrowserInsight's network speed test and check all four figures together rather than only the download number:
- Bandwidth tells you capacity — how much data can move per second.
- Latency tells you delay — how long one round trip takes.
- Jitter tells you consistency — whether that delay stays steady or swings around.
- Packet loss tells you reliability — whether data arrives at all.
If calls or games glitch despite a fast download number, jitter or packet loss — not bandwidth — is almost always the reason. See bandwidth vs latency vs jitter explained for what counts as a good value on each, and why speed test results keep changing for why a single reading can miss an intermittent problem entirely.
Frequently Asked Questions
What's a good jitter value?
Under 30 ms is generally fine for browsing and streaming, under 15 ms is good for video calls, and under 5 ms is ideal for competitive gaming. Above 30 ms, real-time apps typically show noticeable stutter or audio dropouts even when bandwidth is high.
How much packet loss is acceptable?
Under 1% packet loss is usually unnoticeable for most use cases. Between 1–2.5% starts to degrade voice and video calls; above 2.5%, calls and games become difficult to use reliably. Any sustained packet loss on a wired connection with no other traffic is worth investigating.
Can a fast connection still have high jitter or packet loss?
Yes. Bandwidth and timing consistency are largely independent — a high-bandwidth connection routed through a congested or unstable path can still deliver uneven, lossy packet delivery. This is why gaming and VoIP performance doesn't scale simply with a bigger plan.
Does Wi-Fi cause more jitter and packet loss than a wired connection?
Generally yes. Wi-Fi is subject to interference, distance-based signal loss, and contention with other wireless devices, all of which introduce timing variation and dropped packets that a wired Ethernet connection avoids. If calls or games are glitchy over Wi-Fi, testing the same connection over Ethernet isolates whether Wi-Fi is the cause.
Conclusion
Bandwidth answers "how much," but jitter and packet loss answer "how reliably and how consistently" — and for calls, games, and anything else happening in real time, that second question matters more. A fast line with unstable timing or dropped packets will still feel slow, glitchy, or unreliable. Run a full speed test that reports all four numbers together, and if the experience doesn't match the download figure, look at jitter and packet loss first.
Recommended Reading:
