Skip to content
Independent, hands-on tech troubleshooting guides.
Advertisement
Wi-Fi & Networking

Wi-Fi Fast on Speed Tests but Slow in Real Use? Latency Is the Missing Number

Wi-Fi Fast on Speed Tests but Slow in Real Use? Latency Is the Missing Number

We may earn a commission when you buy through links on this page, at no extra cost to you.

What's in this guide
  1. The numbers that actually matter
  2. Bufferbloat, explained simply
  3. What to do
  4. Frequently asked questions

The short answer

Speed tests measure how much data you can move, not how quickly it starts moving. If pages are slow to begin loading and video calls stutter while your speed test looks excellent, the problem is latency, jitter or packet loss — and often bufferbloat, which a standard test hides completely.

Bandwidth is the width of the pipe; latency is how long it takes for anything to come out. Most everyday frustration — pages that hang before loading, calls that break up, games that feel laggy — is latency, and a 500 Mbps result tells you nothing about it.

The numbers that actually matter

  • Ping or latency — round trip time. Under 30 ms is good, over 100 ms is noticeable in calls and games.
  • Jitter — how much the latency varies. High jitter breaks up voice and video even when average latency looks fine.
  • Packet loss — anything above about 1 percent causes visible problems. This is the single most damaging and least reported figure.
  • Latency under load — what happens to ping while the connection is busy. This is bufferbloat, and it is the usual culprit.

Bufferbloat, explained simply

When a device saturates the connection — a big upload, a cloud backup, a game update — routers queue the excess traffic in large buffers rather than dropping it. Those queues add delay to everything else. Your ping can jump from 20 ms to several hundred while a single upload runs, which is why one person’s backup makes everyone else’s video call unusable.

Test for it using a bufferbloat-aware speed test, which measures ping both idle and under load. A large gap between the two is the diagnosis.

What to do

  1. Run a proper test

    Use a test that reports latency under load as well as raw speed, and run it wired if you can, to separate the connection from your Wi-Fi.

  2. Test wired versus wireless

    If a wired connection is fine and Wi-Fi is not, the problem is your Wi-Fi — congestion, distance or an old adapter — rather than your internet connection.

  3. Turn on Smart Queue Management or QoS

    Many routers have SQM, Adaptive QoS or a bufferbloat setting. Enabling it and setting your actual connection speed lets the router manage queues properly instead of letting them grow. This is the single most effective fix and costs nothing.

  4. Find what is saturating the connection

    Cloud backups, game updates, security camera uploads and someone else’s video call all count. Upload capacity is usually far smaller than download, so uploads cause the most damage.

  5. Check for packet loss

    Run a long ping to your router, then to a public address such as 1.1.1.1. Loss to your router means a local problem, usually Wi-Fi. Loss beyond it points at your line and is evidence to give your provider.

  6. Prioritise the traffic that matters

    If your router supports device or application prioritisation, put video calling and gaming above backups and downloads.

Why paying for more speed rarely helps

Upgrading from 200 to 500 Mbps does nothing for latency, and bufferbloat can actually get slightly worse on a faster connection with the same router. If your complaint is responsiveness rather than download times, spend the money on a router with proper queue management instead.

Frequently asked questions


Why does my internet feel slow when speed tests are fast?

Because speed tests measure throughput, not responsiveness. Latency, jitter and packet loss determine how the connection feels, and none of them appear in the headline number.


What causes high ping on Wi-Fi but not Ethernet?

Channel congestion, distance or an older wireless adapter. Wi-Fi adds variable delay that a cable does not, which is why fixed devices benefit so much from being wired.


Is packet loss my provider's fault?

It depends where it occurs. Loss between your device and your router is a local Wi-Fi problem. Loss beyond the router is upstream, and a ping log is the evidence that gets a provider to act.


Does QoS slow down my connection?

It caps throughput very slightly to keep queues short, and the trade is almost always worth it — a few percent of bandwidth for a large improvement in responsiveness under load.


Measure latency under load, not just speed. That one number explains most connections that test well and feel poor.

Share

Did this fix work for you?

Tell us what worked, what did not, and which device you have — it helps the next reader. Your email is never published.