Bufferbloat: why your fast connection feels slow
Your line tests at hundreds of megabits, yet video calls stutter whenever someone starts a download. The usual culprit is bufferbloat, and the fix is cheap.
A few months ago a friend asked me to look at his home connection. The plan was a respectable 300 Mbit/s, the speed tests agreed, and yet every evening his video calls turned into a slideshow. Nothing was "slow" in the traditional sense. The problem was that the connection became sluggish the moment anything else used it.
That symptom has a name: bufferbloat. It is one of the most common problems on home networks and one of the least understood, mostly because the standard speed test doesn't measure it.
What is actually happening
Every device that forwards packets — your router, the modem, the equipment at your provider — keeps a queue. When packets arrive faster than they can leave, they wait in that queue. A small queue absorbs short bursts and is a good thing. A huge queue is not: once it fills up, every packet has to wait behind hundreds of others.
Imagine a supermarket with one cashier and a very long line. Throughput (people served per minute) is exactly the same whether the line is five people or fifty. But if you just want to buy a bottle of water, the length of the line is all that matters to you. Video calls, games and even ordinary web browsing are "bottle of water" traffic: small, frequent and sensitive to waiting.
How to see it
Measure latency twice: once on an idle connection, and once while the link is saturated by a large download. On a healthy connection the second number is only a few milliseconds higher. On a bloated one I regularly see it jump from 15 ms to 300 ms or more.
The speed test on this site reports latency during the download phase for exactly this reason. Run it while nothing else is using the network, and pay attention to the "loaded latency" figure rather than the headline speed.
Fixing it
- Enable smart queue management on the router if it has it. It may be labelled SQM, fq_codel, CAKE or "adaptive QoS". These algorithms keep queues short and share them fairly between flows.
- Set the shaper slightly below your real speed, around 85–95% of what you measure. The goal is to make your router the bottleneck, so that the queue forms where a smart algorithm controls it instead of inside the ISP's modem.
- Re-test under load. If loaded latency drops to within 5–20 ms of idle, you're done. You give up a sliver of peak throughput and gain a connection that feels dramatically faster.
My friend's router supported CAKE. Five minutes of configuration took his loaded latency from about 250 ms down to 22 ms. The speed test number dropped by roughly 8%. He hasn't complained about a call since.