Bufferbloat is the extra delay that builds up when your internet connection is busy. Your connection might show a perfect 15 ms ping when idle. Then someone starts a large download, your video call starts to stutter, and a game becomes unplayable. That jump in delay under load is bufferbloat.

Why it happens

Routers and modems contain buffers: small waiting rooms for packets that arrive faster than they can be sent on. Buffers are useful because they absorb short bursts of traffic.

The problem comes when a buffer is too large and kept full. A big download sends data as fast as it can, and the buffer at the slowest point of your connection fills up. Every other packet, including your game’s or call’s tiny time-sensitive packets, now has to wait behind hundreds of milliseconds of queued download data.

The upload direction is often worse, because upload speeds are lower, so the same buffer takes longer to empty.

How to test for bufferbloat

Measure latency twice: once while the connection is idle, and once while it is fully loaded. That is exactly what SpeedCheckWeb does:

  1. Idle latency: 20 samples before any heavy traffic starts.
  2. Latency during download: samples taken while the download test fills the line.
  3. Latency during upload: samples taken while the upload test fills the line.

The difference between idle and loaded latency is your bufferbloat. Our ping and bufferbloat test puts these numbers front and centre and grades them as follows:

Extra delay under load SpeedCheckWeb grade What it means
Under 30 ms Low Calls and games stay responsive during downloads.
30–100 ms Moderate Fast games and calls may suffer while the line is busy.
100–300 ms High Expect clear lag whenever someone downloads or uploads.
Over 300 ms Severe The connection is close to unusable for real-time apps under load.

These grades are SpeedCheckWeb’s own guidance; they are not an industry standard.

How to fix bufferbloat

The proper fix is smarter queue management, which keeps queues short even when the line is full.

  1. Turn on Smart Queue Management (SQM). Many modern routers have a setting called SQM, “Smart Queue”, “Adaptive QoS” or similar, often using algorithms such as FQ-CoDel or CAKE. FQ-CoDel is standardised in RFC 8290. Set the bandwidth limits slightly below your measured speeds, often about 90–95%, so that queuing happens in your router, where it can be managed well.
  2. Update your router’s firmware. Newer firmware sometimes adds or improves queue management.
  3. Consider a router that supports SQM if yours does not. Some open-source router firmware supports it as well.
  4. Limit heavy transfers. Many apps and consoles let you cap download or upload speed. Capping a big background upload often removes the lag immediately.
  5. Ask your provider. Some providers have improved queue management in their own equipment. Your test results are useful evidence.

Simply buying a faster plan can help, because the buffer empties sooner, but it often does not fix the problem completely. Queue management does.

Bufferbloat and “fast” connections

A gigabit plan does not guarantee low latency under load. A modest connection with good queue management can feel more responsive during busy periods than a much faster one without it. That is why SpeedCheckWeb treats latency under load as a headline result, not a footnote.

In short: bufferbloat is the lag that appears when your connection is busy, caused by oversized queues. Test for it by comparing idle and loaded latency, and fix it with Smart Queue Management.

Sources

  1. Bufferbloat.net – project overview and fixes
  2. RFC 8290 – The Flow Queue CoDel Packet Scheduler and Active Queue Management Algorithm
  3. RFC 8289 – Controlled Delay Active Queue Management (CoDel)

Figures from third parties can change; we review guides regularly. See our editorial policy.

Run a speed test