Beyond Bandwidth: Why Latency, Bufferbloat, and Jitter Define Your Internet Experience

When a video call freezes or a game stutters, the instinct is to blame the connection speed. It is usually the wrong suspect. Three other properties decide how a connection feels, and none of them appears on the tariff.

Capacity is not speed

A useful way to hold the distinction: bandwidth is how many lanes the road has, not how fast anything travels along it. Adding lanes lets more traffic move at once. It does not shorten anyone's journey.

This is why upgrading a connection so often changes nothing. If the problem was never a shortage of lanes, more of them will not help, and the money buys a larger number on a bill rather than a better experience.

Latency: how long the round trip takes

Latency is the delay between doing something and seeing the result. Click in a game, and latency is what stands between the click and the effect. On a call it is what makes two people start talking at the same time.

It comes mostly from three things. Distance, because signals take time to cross physical space and no technology avoids that. Congestion, because a busy path adds queueing at each step. And routing, because traffic frequently does not travel the direct way, and a connection to a server in the next city may be routed through another country entirely.

Bufferbloat: the one nobody looks for

If everything slows down whenever someone in the house uploads something, that is almost certainly bufferbloat rather than a shortage of capacity.

Network devices hold packets in queues when they arrive faster than they can be sent. Within reason that is useful. Where the queue is far larger than it needs to be, packets sit in it instead of being dropped, and the delay grows to hundreds of milliseconds while the link still reports its full rate.

The queue analogy is exact: joining a checkout behind someone with a very full trolley does not get you served faster because the shop has other tills open. What is in front of you is what determines your wait.

Active queue management is the answer, keeping queues deliberately short so that a bulk transfer does not push a call to the back of a long line.

Jitter: the timing problem

Jitter is variation in when packets arrive. Media expects a steady stream, and when the spacing becomes uneven, audio turns robotic and video stalls and jumps.

It is more disruptive than either low bandwidth or moderate latency, because consistent delay can be compensated for and inconsistent delay cannot. A receiver can buffer to smooth it out, but only by adding delay of its own, which is a trade rather than a fix.

Wired connections help, because Wi-Fi introduces timing variability that Ethernet does not. So does keeping queues under control, since a queue that fills and empties unpredictably is itself a source of jitter.

What to do

Test latency while the connection is busy rather than idle, since almost everything looks fine when nothing else is running. If the figure climbs sharply under load, the problem is queueing rather than capacity.

Use a wire where it is practical, particularly for calls and gaming. Check whether the router supports modern queue management, because older equipment frequently does not and is the most common cause of the whole pattern.

And before upgrading a plan, establish which of the four properties is actually short. If the answer is latency, jitter or bufferbloat, a larger plan will change the bill and nothing else.

The operator's side of this is covered in optimising network performance, which looks at the same three properties from the network rather than the household.