Guide
Internet Speed for Gaming
Why gaming depends on latency, jitter, and loaded latency more than raw bandwidth — and how to test for a smoother, more consistent connection.
Gaming is different from streaming
Most guides talk about internet quality purely in terms of speed, but gaming is the activity where that framing breaks down the most. A live multiplayer session typically needs only a few Mbps of bandwidth — far less than a single HD video stream. What actually determines whether a game feels smooth is responsiveness: how quickly your input reaches the game server and a result comes back, how consistent that timing is, and whether it holds up while the rest of your connection is busy. Those three properties — latency, jitter, and loaded latency under load — matter far more to a gamer than a bigger download number. See our ping, jitter & loaded latency guide for a full breakdown of each.
Gameplay bandwidth vs. game downloads and updates
It helps to separate two very different kinds of traffic that both happen on a "gaming" connection. Live gameplay traffic — the constant stream of small packets telling the server where you are, what you're doing, and what just happened — is small and continuous, usually only a few Mbps even in competitive titles. Downloading or patching a game is the opposite: a large, one-time (or occasional) transfer that benefits directly from raw download bandwidth, where a faster connection genuinely means a shorter wait. If your evening is going badly because a 60 GB update is still installing, that's a bandwidth problem and a faster plan or a wired connection will help. If your evening is going badly because you're getting outplayed by half a second of lag despite a fast connection, bandwidth isn't the issue at all.
Latency: the round trip that decides how "instant" the game feels
Latency (often shown as "ping") is the round-trip time between your device and a game server — how long it takes for your action to arrive and a response to come back. Lower is better, and the effect is most noticeable in fast-paced or competitive genres, where the gap between "shot registered" and "shot missed" can come down to a few tens of milliseconds. Slower-paced, turn-based, or single-player-with- occasional-sync games are far more forgiving. Rather than repeat exact thresholds here, see our methodology page for the specific latency ranges we use to rate a connection as excellent, good, acceptable, or poor for real-time use.
Jitter: why "average" latency can be misleading
Jitter measures how much your latency varies from one moment to the next, rather than what it averages out to. A connection that alternates between 15 ms and 90 ms can report a perfectly reasonable average latency while feeling terrible to actually play on, because the game server has to guess at your true position and periodically correct it — the rubber-banding, stutter, or "warping" that players often blame on the game itself is frequently a jitter problem instead. Low, stable latency is worth more than a lower average latency that swings wildly.
Loaded latency: the bufferbloat problem
Loaded latency is what happens to your latency while the connection is also busy doing something else — and it's often the single biggest culprit behind "my internet is fast but gaming still lags." A household member starting a large download, a cloud backup kicking off, or someone else beginning a 4K stream or a video call can flood a shared connection's upload or download queue, a phenomenon known as bufferbloat. Even though your plan's advertised bandwidth is technically "available," those queued packets can delay your gameplay traffic by hundreds of milliseconds. This is why testing loaded latency specifically — not just idle ping — matters for gamers: it's the number that tells you what actually happens under real household conditions, not ideal ones. If loaded latency spikes on your connection, enabling Quality of Service (QoS) or Smart Queue Management (SQM) on your router, if it supports one, is one of the most effective fixes, since it prioritizes latency-sensitive traffic like gaming ahead of large downloads and uploads sharing the same line.
Packet loss: a concept worth understanding, even though we don't measure it yet
Packet loss happens when some of the small data packets sent between your device and the game server never arrive, forcing a retransmission or a gap the game has to guess around. In gaming, this typically shows up as sudden hitching, brief freezes, or actions that seem to register late or not at all — distinct from the smoother slowdown caused by high latency or jitter alone. It's a real and relevant concept for diagnosing a rough gaming session. That said, this test does not currently measure packet loss: reliable packet-loss measurement needs a WebRTC TURN relay with securely issued, per-session credentials, and the public TURN configuration that would make this possible is deprecated — see our methodology page for the full explanation. We don't report a packet-loss number, and you should treat any claim of measured packet loss on this site with suspicion until we explicitly say otherwise.
Wi-Fi vs. Ethernet for gaming
Wi-Fi adds variability — interference, distance from the router, and contention with other devices — that shows up primarily as extra latency and jitter rather than lower bandwidth. For competitive or latency-sensitive gaming, a wired Ethernet connection to your console or PC removes that variability almost entirely. See our full Wi-Fi vs. Ethernet comparison for what changes and when it's worth running a cable.
Check what your connection is actually doing
A download number alone won't tell you whether your connection is ready for gaming. Run a speed test to see your idle latency, jitter, and loaded latency together, and check them again while someone else in the household is streaming or downloading to see how much your connection moves under real conditions.