A video call stutters the instant someone in the house starts a large upload, even though a speed test insists the connection is quick. That gap between a good headline number and a bad real feel has a name, bufferbloat, and it comes from network equipment holding onto data too eagerly. This guide follows a concrete example of a line that tests fast yet lags under load, shows why ordinary speed tests miss the problem, and walks through the queue-management setting that fixes it without paying for faster service.
How buffers turn into delay
Buffers are small holding areas that let equipment absorb bursts of traffic instead of dropping it. In moderation they are useful. The trouble is that many modems and routers ship with buffers far larger than they need, and a large buffer that fills up becomes a long queue. When you saturate your upload or download, packets pile into that queue and wait their turn, and the wait is added latency. A packet that would normally cross your link in fifteen milliseconds can sit in an overgrown buffer for hundreds of milliseconds before it even leaves the house.
The damage is worst on the direction that fills first, usually the slower upload. A single file sync, photo backup, or game update can swamp the queue, and because the buffer does not tell the sender to ease off until it is completely full, delay climbs and stays high for as long as the transfer runs.
Why speed tests look fine
A standard speed test measures two things, how many megabits per second flow down and up, and often a single ping taken while the line is otherwise idle. Bufferbloat does not show up in any of those. Throughput can be exactly as advertised, and the idle ping can be low, because the queue only grows long while the link is fully loaded. The test finishes before the damage is visible, then reports a reassuring set of numbers.
This also explains why upgrading to a quicker plan or a newer wireless standard does not help. The queue is a delay problem, not a throughput one, so the generational speed gains the comparison of competing Wi-Fi standards describes leave bufferbloat completely untouched. People insist their connection is fast while genuinely suffering lag, and both statements are true; they simply describe different moments.
What it does to calls and games
Real-time applications care far more about consistent low latency than about raw speed. A voice or video call needs each packet to arrive on a tight schedule, and a few hundred milliseconds of queuing delay turns a smooth conversation into two people talking over each other. Online games feel it as rubber-banding and late hit registration, where your inputs and the server’s view drift apart. None of this is a bandwidth shortage; the pipe is wide, but everything is stuck in line.
Reading latency under load
The quickest way to grasp the effect is to compare idle delay with delay under a saturated link, and note how that maps to experience. The added figure is the one that matters, and it travels with two companions, jitter and packet loss, all three defined in the guide on what ping, jitter, and loss really mean.
| Latency added under load | Typical grade | How it feels |
|---|---|---|
| Under 30ms | A | Calls and games stay smooth |
| 30 to 100ms | B to C | Occasional stutter is noticeable |
| 100 to 250ms | D | Calls break up, games rubber-band |
| Over 250ms | F | Real-time use becomes frustrating |
The setting that fixes it
The cure is a feature called smart queue management, sometimes labelled SQM, adaptive queue management, or by the names of its algorithms such as fq_codel and CAKE. Rather than let a giant buffer hoard packets, it keeps the queue short and shares the link fairly between connections, signalling senders to slow before delay builds. For this to work, your router has to be the point that controls the queue, not the modem, a division of labour the guide on how the two boxes split the job makes clear. In practice that means shaping traffic just below your line’s real speed, so the backlog forms where the algorithm can manage it.
Here is the setting on a real connection. Suppose a line rated 100Mbps down and 20Mbps up shows an idle ping of 18ms, but a bufferbloat test during a full upload pushes latency to 340ms, a clear F.
- Enable smart queue management on the router and choose the CAKE algorithm.
- Set the upload shaping rate to about 18Mbps, roughly 90 percent of the measured 20, and the download to about 90Mbps.
- Rerun the same test while saturating the upload.
- Latency under load now settles near 25ms, an A, while throughput slips only slightly to the shaped rates.
The trade is small and deliberate: you give up a sliver of peak speed, about ten percent, and in return the connection stops falling apart whenever it is busy. For most households that is an easy exchange, since the lost megabits are rarely missed while the steadier latency is felt constantly.
Testing your own line
Finding out where you stand takes a couple of minutes. Use a test built to measure latency while the link is loaded, rather than a plain speed test, letting it run a download and an upload while it samples ping. The result is usually shown as a letter grade alongside the idle and loaded figures. Wired results are cleaner than wireless ones, because Wi-Fi adds its own variable delay that can muddy the picture, so run the check over a cable of a decent grade, the sort the guide on choosing an Ethernet cable category helps you pick.
What this means in practice
Bufferbloat is one of the few network problems where the fix is free, precise, and felt immediately. It is not about paying for more speed, replacing cables, or moving the router; it is about stopping a buffer from hoarding packets and letting a smart queue keep the line responsive under load. Because the symptom looks like slowness, people chase bandwidth they already have, when the real shortfall is discipline in the queue.
If calls degrade the moment a download starts, or games spike whenever someone streams, run a proper loaded-latency test first. A poor grade points straight at bufferbloat, and enabling smart queue management on a capable router usually turns that F into an A within an evening. The connection you already pay for often holds more real-world quality than any speed test would suggest.
Frequently asked questions
Why does my internet lag when downloading?
Because a large transfer fills an oversized buffer in your modem or router, and every other packet has to wait behind that queue. The added delay, often hundreds of milliseconds, is bufferbloat. Your download speed can be perfectly normal while this happens, since the problem is queuing latency rather than a lack of bandwidth. Smart queue management removes it by keeping the queue short and disciplined.
What is bufferbloat?
Bufferbloat is excess latency caused by network buffers that are too large. When a link is saturated, these buffers fill with packets that sit waiting, adding delay that can reach hundreds of milliseconds. It hurts real-time uses like calls and games while leaving raw speed measurements looking fine, which is why it often goes unnoticed and gets misdiagnosed as a general slowdown of the connection.
How do I fix lag under load?
Enable smart queue management, sometimes called SQM, on a router that supports it, using an algorithm such as fq_codel or CAKE. Set the shaping rate slightly below your measured line speed, around ninety percent, so the queue forms inside the router where the algorithm can control it. Retest with a loaded-latency tool, and the added delay should fall from hundreds of milliseconds to a few dozen.
