Why video calls freeze while your speed test looks fine
Your download number looks fine but the call still stutters. Latency, jitter and upload speed decide call quality, and here is how to check each one.
A speed test shows 300 Mbps. Then the 8pm call freezes anyway, faces turn to blocks and everyone says "you're breaking up" while your internet is supposedly fine. Both readings are true, because they measure different things.
A speed test answers "how wide is the pipe". A video call asks a different question: does a small packet leave my laptop, cross the network and arrive in the next 100 milliseconds, in both directions, every time, for the next 40 minutes. Wide pipe, late packets — the call still stutters.
What a call actually needs
| Requirement | What it does to the call | Where it usually breaks |
|---|---|---|
| Download | Receives other people's video | Rarely the problem on fibre |
| Upload | Sends your camera feed | Often much smaller than download |
| Latency (ping) | Delay before anyone hears you | Congestion, bufferbloat, long routing |
| Jitter | How much that delay swings | Busy WiFi, busy line |
| Packet loss | Missing pieces of the picture | Weak WiFi signal, saturated link |
A call survives a modest download speed far better than it survives 3% packet loss. That is the single most useful thing to know here: calls are hurt by timing, not by bandwidth.
Step 1: measure latency and jitter, not just speed
Run the speed test on this site over WiFi from the room where the call fails, and look at the ping and jitter figures as closely as the download number.
Read them like this:
- Ping under 50 ms, jitter under 15 ms — the network is not your problem. Look at the laptop, the app or the far end of the call.
- Ping fine when idle, but 300 ms during the call — this is bufferbloat. Classic, and fixable.
- Ping 20 ms, then 400 ms, then 30 ms — jitter. Usually WiFi airtime or a neighbour hammering the line.
- Upload far below what your plan promises — the camera feed is being squeezed, and the app turns the video to mush to compensate.
Run it twice: once with everything idle, once while the call is actually happening in another room. The second run is the one that matters.
Cause 1: bufferbloat in your own router
When the line is busy, packets queue. If the queue is deep and dumb, it fills up and everything waits behind it — the classic symptom is a call that is fine for two minutes, then dead for five seconds, then fine again.
The tell: your ping is normal when nothing is downloading, and explodes to hundreds of milliseconds the moment someone starts a backup, a game update or a big upload.
What helps, cheapest first:
- Turn on SQM or Smart Queue if your router has it. On many routers it is buried under QoS settings.
- Cap the router's WAN download and upload to about 90% of your plan speed. Counter-intuitive, but a queue that never fully fills cannot add seconds of delay.
- Move big downloads and cloud backups to after 11pm, or schedule them.
Cause 2: upload is the quiet bottleneck
Home plans are lopsided: the download number on the advert is many times the upload number. A single 1080p call on a good codec needs roughly 3–4 Mbps up. Add a second person on a call, a phone syncing photos, and a cloud drive uploading a file, and the upload is fully booked. Everything still "works" — just badly.
Check it: run the speed test while both calls are live and watch the upload figure. If it is pinned at your ceiling, that is your answer.
What helps: stop cloud backups during call hours, turn off camera when you are not speaking (it cuts upload hard), and if calls are a daily part of your household, treat upload speed as the number you care about when choosing a plan — not the download headline.
Cause 3: WiFi airtime, not signal bars
Four bars is not the same as a clear channel. One device at the far end of the house with a weak signal retransmits every packet several times, and each retransmission takes a turn on the channel that every other device is waiting for. Your laptop can sit next to the router with full bars and still stutter because a phone in the back room is monopolising the air.
Signs: calls are fine when the house is empty, bad when everyone is home. Or the problem follows you around the house instead of staying in one room.
What helps: use 5 GHz or 6 GHz for the device you call on, keep the router out of cabinets, and if the weak-signal device is permanent, fix its coverage rather than buying more speed. Where to put your router covers the placement rules that cost nothing.
Cause 4: the far end of the call
Worth checking before you buy anything. If the same call fails with the same person at the same time of day, and a different call works fine, the problem is at their end or on the route between you. Ask them to test on mobile data for one call. If their side is bad, nothing in your house will fix it.
The order to do this in
- Run the speed test during a bad call, and write down ping, jitter and upload.
- If ping is fine idle and terrible under load, enable SQM or cap the line at ~90%.
- If upload is pinned at the ceiling, cut the competing uploads before touching hardware.
- If it only fails far from the router, fix coverage — do not buy a faster plan.
- If all three are clean, test the same call on mobile data to isolate the far end.
A call does not care how much data your line can carry. It cares whether the next packet arrives on time — and that is a queue problem, not a speed problem.