You pay for 200 Mbps, the speed test confirms it, and your game still lags in the middle of a firefight. Download speed and ping aren’t the same metric. They do different jobs, and fixing one when the other is the problem doesn’t help.
What ping actually is
Ping is the time it takes for a packet to travel from your machine to the game server and back, measured in milliseconds. When you press fire, that click travels to the server, the server processes it, and a confirmation comes back. Ping is how long that round trip takes.
At 20 ms, that round trip happens 50 times per second. At 150 ms, the server is registering your inputs from an eighth of a second ago. In Valorant or CS2, you can cross two strafing positions in that window. That’s why you miss shots that visually connected on your screen.
Low, consistent ping is the single most important network metric for online gaming. You can play a competitive match on 5 Mbps of download speed. You can’t compete meaningfully at 150 ms.
- Under 20 ms: excellent, competition-grade
- 20-50 ms: comfortable for most games
- 50-100 ms: playable but noticeable in fast shooters
- Over 100 ms: impacts hit registration and reaction windows
What download speed actually is
Download speed (Mbps) is your bandwidth. Bandwidth determines how fast a 60 GB game downloads, how quickly patches apply, and whether a 4K stream buffers. During active gameplay, most titles use between 1 and 5 Mbps. Modern multiplayer games send small state updates back and forth, not large transfers.
At 25 Mbps, you have enough room for gaming and a video call running at the same time. At 10 Mbps, patch downloads take longer, but active gameplay is unaffected.
The speed figure on your ISP invoice matters for game installs, update downloads, streaming while queued, and households with multiple people on the connection. It doesn’t decide whether your shots land.
- 10 Mbps: solo gaming, no concurrent streaming
- 25 Mbps: gaming alongside a video call or one streamer
- 100 Mbps+: multiple users, 4K streaming alongside gaming
The metric both miss: loaded latency
There’s a third factor most speed tests don’t show, and it explains why many “fast” connections feel bad in games.
When your connection gets busy, your router queues packets to handle the load. That queue spikes your latency. A line that pings at 10 ms idle can hit 300 ms when someone starts a download. That spike happens mid-game, right when you need the connection most.
It’s called bufferbloat, and it’s why your ping seems fine in the morning but your game falls apart at 8 PM when the household is active. The internet speed test on RigPolice measures it directly: it samples your ping while the download and upload are running, not just while the line is idle. An A+ grade means the connection stays responsive under load. An F means every large transfer tanks your latency.
If your game ping spikes whenever someone else uses the network, bufferbloat is the likely cause. Fixing it usually means a wired connection and a router with smart queue management, not a faster plan.
Upload speed and jitter
Upload matters mainly if you stream. Encoding 1080p60 to Twitch pulls 6-10 Mbps, and that fights your game traffic on the same pipe. For gaming alone, 3-5 Mbps is enough.
Jitter is ping variance. A steady 45 ms beats a line that swings between 15 and 90. High jitter causes rubber-banding even when your average looks fine. The speed test shows jitter alongside idle ping.
What to check first
Run a speed test and read the results in this order:
- Idle ping: under 50 ms is comfortable for most games. Over 100 ms, check your in-game server region and investigate your ISP’s routing to your nearest game server.
- Bufferbloat grade: A or B is fine. C or below means your router’s queue management needs attention. Switching from Wi-Fi to a wired connection often improves this without touching the router.
- Jitter: under 10 ms is stable. Higher values point to congestion or a weak Wi-Fi signal.
- Download and upload: check these last. If the above three are solid and the game still lags, raw speed is unlikely to be the bottleneck.
Most lag complaints trace back to ping, not bandwidth. A 1 Gbps plan doesn’t fix a routing problem.