Wi-Fi vs Ethernet for Gaming: The Latency Numbers
Wi-Fi adds latency, jitter, and packet loss that show up as rubber-banding and peek disadvantage. Here is the actual difference in milliseconds, why jitter hurts more than average ping, and what a $10 cable and powerline adapters can and cannot fix.
"Is ethernet really worth it for gaming?" The question gets answered with vibes on both sides. The honest answer needs numbers: how many milliseconds Wi-Fi actually adds, what jitter does to your effective latency, and when wireless is genuinely good enough. This article walks through the measured differences, explains why average ping alone hides the real problem, and lists the fixes in order of cost.
Latency: the average difference is smaller than you think
In a clean setup — good router in the same room, minimal interference — modern Wi-Fi 5 and Wi-Fi 6 connections often average within 1–5 ms of a wired connection to the same server. Ping a nearby server from both connections on a quiet network and you may see 12 ms wired versus 15 ms wireless. On those averages alone, nobody would notice.
So if averages were the whole story, Wi-Fi would be fine. They are not the whole story, because averages hide the two things that actually cost you games: jitter and packet loss.
Jitter: the number that decides games
Jitter is the variation in ping between packets. A wired connection typically shows jitter of ±1 ms or less. Wi-Fi routinely fluctuates by ±5–30 ms, and much more when the airwaves get busy. Here is why that matters more than the average:
- In a shooter, you act in bursts: you swing a corner, you take a fight, all within a few hundred milliseconds. Your effective latency is your ping during that burst, not your daily average.
- A Wi-Fi connection averaging 15 ms with spikes to 45 ms means that some of your fights happen at 45 ms — three times worse than the number you see on screen.
- Games interpolate to smooth this over, which is why Wi-Fi symptoms feel like rubber-banding, hit-marker failures, and "I shot first" moments rather than constant sluggishness.
Packet loss is the nastier sibling: a lost packet must be retransmitted, adding one full round trip or more. Wi-Fi retries happen silently and frequently under interference — a microwave oven running on the 2.4 GHz band can destroy throughput for the seconds it runs.
The physics of why Wi-Fi fluctuates
- Shared spectrum. Every Wi-Fi device in range — neighbors included — shares channels. Your router pauses whenever someone else transmits.
- Interference. Microwaves, baby monitors, Bluetooth, and USB 3.0 ports radiate in or near the 2.4 GHz band.
- Walls and distance. Each wall costs signal; the client lowers its modulation rate as signal drops, and lower rates mean longer airtime per packet.
- Power saving. Laptop and phone Wi-Fi chips sleep briefly between transmissions; on a desktop NIC this is usually disabled, but it is worth checking the adapter's power management settings.
Wired ethernet has none of these failure modes. A cable is a dedicated, shielded path with constant timing.
What the fix costs
| Option | Typical cost | Expected improvement |
|---|---|---|
| Ethernet cable, same room | $10–$15 | Jitter near zero, no loss |
| Ethernet through walls (flat cable / drilled run) | $20–$50 | Same as above |
| Powerline adapter pair | $50–$90 | Better than bad Wi-Fi, worse than cable; quality varies by wiring |
| Mesh node with wired backhaul | $120+ | Very good wireless, best if node is ethernet-connected |
| Wi-Fi 6/6E upgrade alone | $70–$200 | Helps congestion, jitter remains possible |
The first row is the punchline: for most desktop gamers whose router is one or two rooms away, a long flat ethernet cable run along the wall is the cheapest possible fix and completely solves the problem. Save the money on networking upgrades until the cable is genuinely impossible.
When Wi-Fi is actually fine
- Turn-based and slow-paced games — card games, strategy, most MMOs outside raids. A 20 ms spike changes nothing.
- A strong 5 GHz or 6 GHz signal in the same room as the router, with no more than a couple of other active devices. Casual play on well-behaved Wi-Fi is genuinely indistinguishable for many people.
- Consoles in the living room where a cable run is impractical — though even a single mesh node near the console helps.
If you must stay on Wi-Fi: the checklist
- Move to 5 GHz (or 6 GHz) and away from 2.4 GHz if your devices support it. Same room, no walls between.
- Pick a clean channel. In the router admin page (usually
192.168.1.1or192.168.0.1— check the label on the router), scan for the least congested channel; 2.4 GHz non-overlapping choices are 1, 6, and 11. - Disable the NIC's power saving. Device Manager > Network adapters > your Wi-Fi adapter > Properties > Power Management > uncheck "Allow the computer to turn off this device." Menu names may vary slightly by driver version.
- Keep the router high and central, away from microwaves, aquariums, and thick exterior walls.
- Test during your real play hours. Run a ping test to your game's server region at 8 PM, not 10 AM. Continuous ping (
ping -t <server>on Windows) for ten minutes shows the spikes a single test hides.
Measuring your own numbers
Before and after any change, gather three numbers: average ping, jitter (the spread in a continuous ping), and packet loss. Windows' pathping or a free tool like PingPlotter shows all three over time. For the deeper diagnosis of online lag symptoms, our guide to fixing lag and packet loss covers server-side issues, and reducing input lag covers the parts of delay that never touch the network at all. If your stutter turns out to be frames rather than packets, start with fixing stuttering on Windows 11. More networking and performance guides are on the blog index.
Menu paths reflect Windows 11 and common router firmware as of 2026 and may vary by version and manufacturer.
