Speed Test Says Fine, But You Still Lag in Games? Here’s Why

Your speed test shows 300 Mbps and a 20 ms ping, yet you still rubber-band, miss shots that were on target, and freeze at the worst possible moment. Both things can be true at the same time — because a speed test and an online game measure completely different things.

What a speed test actually measures

A typical speed test answers one question: how much data can this connection move per second? It opens several TCP connections to a nearby, carefully chosen server, transfers as much as it can for a few seconds, and reports the peak or average throughput. The “ping” it shows is usually a handful of samples to that same optimized server, averaged together.

That is a useful number for streaming and downloads. But it tells you almost nothing about the consistency of your connection — and consistency is the only thing a game cares about.

What an online game actually needs

A competitive game sends tiny messages called UDP packets to the server 20 to 60 times per second — your position, your inputs, your shots. UDP just means “fire and forget”: the packet is thrown at the server with no delivery receipt and no resend if it goes missing. Fast, but unforgiving. Each one of those packets needs to arrive quickly and at a steady interval. The total bandwidth involved is trivially small; even a slow DSL line has enough. What breaks games is not a lack of speed, it is moments where the connection stumbles:

• Lagspikes — latency suddenly jumps from 25 ms to 300–800 ms for a second or two. That is the freeze you feel when you peek a corner and die before the screen updates.
• Jitter — your ping going on a rollercoaster: 25 ms, then 90, then 15, then 60. A steady 40 ms plays far better than that ride, because the game cannot smooth out arrival times it can’t predict.
• Packet loss — bullets that never arrived. Some packets simply never reach the server: shots don’t register, movement snaps back, voice chat turns robotic.
• Bufferbloat — your router making your game packets stand in line behind someone’s Netflix stream or a Windows update. Nothing gets lost; everything just shows up late. Fine in the speed test, miserable the moment anyone in the house starts a download. We have a whole guide on it.

Why averages hide all of this

Do the math on a typical speed test ping. Suppose your line is probed 60 times over ten seconds: 59 probes come back at a healthy 25 ms, and one — the one that made you die in-game — takes 800 ms. The reported average is about 38 ms. “Looks fine.” The single worst moment, the only one that mattered, is diluted to nothing.

Bandwidth averages work the same way. A line that delivers 500 Mbps for 9 seconds and drops to zero for 1 second still reports roughly 450 Mbps — a great score for a connection that just disconnected you from the match.

TCP hides packet loss — games don’t use TCP

There is a second, subtler problem: speed tests run over TCP, and TCP silently retransmits lost packets. From the test’s point of view nothing was lost; the transfer just took slightly longer, invisible inside an average. Games overwhelmingly use UDP, which never retransmits — a lost packet is simply gone. That is why a TCP-based test can show a clean bill of health on a line where a game sees 3% packet loss.

To measure what a game actually experiences you have to send traffic that behaves like game traffic: small UDP packets, at game-like rates, with no retransmission. That is exactly what LagScope’s GAME TRAFFIC mode does — it opens a WebRTC DataChannel in unreliable/unordered mode and exchanges 128-byte UDP packets at 30 Hz, so the packet loss and jitter it reports are the ones your game feels.

How to see what’s really happening

1. Run a continuous monitor, not a one-shot test. Spikes that happen every few minutes will never show up in a 10-second speed test.
2. Watch jitter and worst-case latency, not the average. A 0–100 Gaming Readiness score that weighs spikes and loss tells you more than any Mbps number.
3. Measure with UDP game traffic, not just TCP, so retransmissions don’t launder your packet loss into looking like nothing.
4. Let it run while you play. When you feel the lag, look at the graph — the spike will be sitting there with an exact timestamp.
5. Test under load too. If you only lag while someone is streaming, that’s bufferbloat, and it has a specific fix.

Frequently asked questions

Is 300 Mbps enough for gaming?

Easily — games use only a few megabits. A 25 Mbps line with stable latency beats a gigabit line with jitter and packet loss every single time. Buy stability, not speed.

What ping is good for gaming?

Under 20 ms to the server is excellent, 20–50 ms is fine for almost everyone, and beyond 80 ms starts to hurt in fast shooters. But a steady 50 ms beats a spiky 25 ms — jitter matters as much as the number.

My ping is low but games still stutter — why?

Almost always jitter or packet loss. A low average ping with high variance means packets arrive early, then late, then not at all. The game client can’t interpolate smoothly, so players teleport and shots desync.