Is Your Network Good Enough for Gaming?
Gamers obsess over FPS and GPU benchmarks, but your network matters just as much. Here's what metrics to look for and what numbers you actually need.
You upgraded your GPU, cranked the settings to ultra, and you're still getting destroyed in competitive matches. Before you blame your reflexes, check your network — it might be the real bottleneck.
What Gamers Actually Need
Here's the uncomfortable truth: bandwidth barely matters for gaming. A typical online game uses surprisingly little data:
| Game | Data per hour | Notes |
|---|---|---|
| League of Legends | 45–100 MB/hr | Riot's Learn with League |
| Fortnite | ~100 MB/hr | Epic recommends min 3 Mbps connection |
| Valorant | 200–290 MB/hr | Higher due to 128-tick servers |
| CS2 | ~450 MB/hr | ~3x more than CS:GO due to 128-tick |
Even CS2 — the most bandwidth-hungry game on this list — uses less than 1 Mbps of sustained throughput. Your 500 Mbps connection is wildly overkill for the game itself.
What actually matters is latency, jitter, and packet loss:
| Metric | Excellent | Acceptable | Problematic |
|---|---|---|---|
| Latency (ping) | < 30ms | 30–50ms | > 100ms |
| Jitter | < 5ms | 5–15ms | > 15ms |
| Packet loss | 0% | < 1% | > 1% |
These thresholds are industry conventions rather than official standards from any single publisher, but they're consistent across networking and gaming engineering literature.
Latency: The Input Delay You Can Feel
Latency is the round-trip time between your machine and the game server. Every millisecond of latency is a millisecond of delay between your click and the server registering it.
Riot Games has published some of the most specific latency targets in the industry. For Valorant, which runs on 128-tick servers with a network interpolation delay of 7.8ms, their engineering target is under 17.5ms latency for 70% of the player population.
At 20ms, you won't notice. At 80ms, you'll start losing gunfights you should have won. At 150ms, the game feels sluggish and unresponsive.
One thing to keep in mind: your latency to a speed test server is not necessarily your latency to the game server. Game servers are often in specific regions, and routing can vary. For a realistic number, test against a server close to where your game's servers are located.
Jitter: The Silent Killer
Jitter is the variation in your latency over time. Consistent 50ms latency is playable — your brain adapts. But latency that jumps between 20ms and 150ms every few seconds? That's rubber-banding, teleporting enemies, and shots that don't register.
Most gamers focus on average ping and ignore jitter entirely. This is a mistake. A connection with 30ms average and 5ms jitter will feel dramatically better than one with 25ms average and 40ms jitter.
Packet Loss: Where Hits Disappear
When packets are lost, game data never reaches the server (or never comes back to you). Most competitive games use UDP for game state updates, which doesn't retransmit — lost packets are just gone. The result: your perfectly aimed shot vanishes into the void.
How bad is even a little packet loss? According to ThousandEyes, 1% packet loss can reduce TCP throughput by up to 75% due to retransmission overhead. For UDP game traffic, there's no retransmission — those packets are simply lost. Even Riot's engineering guidance states that high-quality connections "should have near-zero packet loss at all times."
WiFi vs Ethernet: It's Not Close
If you're gaming on WiFi, that's likely your biggest problem. Independent benchmarks from HowToGeek measured:
- Wired Ethernet: average 16ms ping, 7ms jitter
- WiFi 6 (same network): average 60ms ping, 20ms jitter
That's nearly 4x the latency and 3x the jitter. And these are under good conditions. Under interference — neighbor's WiFi, 2.4 GHz congestion, someone streaming 4K on the same network — WiFi jitter can spike far worse. Real-world tests on SNBForums showed WiFi 5 adding occasional spikes from 50ms to 68–70ms, perfectly illustrating how average latency hides the real problem.
Riot Games explicitly recommends wired connections in their troubleshooting documentation: "Wireless connections tend to be difficult to troubleshoot due to potential interference from the environment and other radio signals. This often causes lag spikes and/or packet loss in the game."
If you can't run a cable, WiFi 6E on a clear 6 GHz channel is the next best option — less congestion means less jitter.
How to Test Your Gaming Network
- Run a quality test at netprofile.net/speedtest — focus on the latency, jitter, and packet loss results rather than raw download speed
- Test during peak hours — your network might be fine at 2 AM but congested at 8 PM when everyone's streaming
- Test on the same connection you game on — if you game on WiFi, test on WiFi
If your packet loss is above 1% or jitter is above 15ms, switching to Ethernet or addressing your network configuration will likely make a bigger difference than any hardware upgrade.