Wi-Fi Ping Test
Measure your latency over the wireless link, then work out how much of it the Wi-Fi itself is responsible for. Wireless rarely makes a connection slow — it makes it inconsistent, and inconsistency is what ruins games and calls.
Measures round-trip time to 14 cloud regions
Run this once on Wi-Fi and once with an Ethernet cable, then compare the closest region on both. The difference is what your wireless link is costing you. Pay particular attention to the jitter column — that is where Wi-Fi problems show up first.
The one test that settles it: ping your own router
Before blaming your provider, measure the part of the journey that never leaves your house. Your router's address is almost always 192.168.1.1, 192.168.0.1 or 10.0.0.1 — you can confirm it with ipconfig on Windows or ip route on Linux.
Then run ping -c 20 192.168.1.1 (or ping -n 20 192.168.1.1 on Windows) while connected wirelessly. That round trip is your wireless link and nothing else.
Under 5 ms with a standard deviation of a millisecond or two: your Wi-Fi is healthy and any lag you feel is coming from beyond your front door. Between 5 and 20 ms: acceptable for most things, marginal for competitive play. Above 20 ms, or a minimum of 2 ms with a maximum of 200 ms: the wireless link is your problem, and everything else you might change upstream is a distraction.
Why wireless adds delay at all
Ethernet gives every device its own dedicated path. Wi-Fi does not: every device on the channel — including your neighbours' devices on their own networks — takes turns using the same slice of radio spectrum. Before your packet can be sent, the adapter has to listen, wait for a quiet moment, and sometimes back off and retry. That waiting is where the milliseconds come from, and it is why your latency depends on what other people in the building are doing.
On top of that, a weak or noisy signal causes frames to be lost and retransmitted. Retransmission is invisible to the application but very visible in the latency graph, because a single retry can add tens of milliseconds. This is why signal strength affects ping even when your speed test still reports a high number: bandwidth degrades gracefully, latency does not.
| Band | Typical added latency | Trade-off |
|---|---|---|
| 2.4 GHz | 5-40 ms | Only three non-overlapping channels, shared with microwaves, Bluetooth and every neighbour. Best range, worst consistency. |
| 5 GHz | 1-5 ms | Many more channels and wider ones. Weakens through walls, so range is the limiting factor rather than congestion. |
| 6 GHz (Wi-Fi 6E / 7) | 1-3 ms | Currently almost empty spectrum, so contention is minimal. Short range and needs both router and device to support it. |
| Ethernet | Under 1 ms | No contention, no retransmission, no jitter. Still the correct answer for a competitive setup. |
Fixes that actually move the number
Move to 5 or 6 GHz. Many routers publish both bands under one name and let the device choose, often badly. Splitting them into separate network names and connecting deliberately to the faster band is the single highest-impact change for most households.
Change channel. A Wi-Fi analyser app will show which channels your neighbours occupy. On 2.4 GHz only 1, 6 and 11 do not overlap, so anything else is actively harmful. On 5 GHz pick a channel nobody nearby is using and, if your router supports it, avoid the DFS range where radar detection can force a sudden channel change.
Turn off adapter power saving. On Windows this hides in Device Manager under your wireless adapter's Power Management tab, and on laptops it is usually enabled by default. It saves a trivial amount of battery and costs a very untrivial amount of consistency.
Reduce distance and obstacles. Signal strength affects latency more than most people expect, because a weak link means retransmissions. One wall closer often beats any setting change.
Enable Wi-Fi Multimedia or gaming QoS if your router offers it. It prioritises small, latency-sensitive packets over bulk transfers, which is exactly the distinction that matters when someone else in the house is streaming.
When Wi-Fi is not the culprit
If the wired and wireless results are within a few milliseconds of each other, stop optimising your Wi-Fi. The delay is coming from your ISP's network, from the route to the destination, or from sheer distance — and none of those respond to a channel change.
The regional table above is the quickest way to tell the difference. A connection where every region reads high, including the nearest one, has a local or provider problem. A connection where the nearest region is fast and distant ones are slow is simply behaving the way physics requires.
Wi-Fi latency questions
How much latency does Wi-Fi add?
On a clean 5 GHz link, typically 1-3 ms of extra latency and very little jitter. On a congested 2.4 GHz band in an apartment building it can be 15-40 ms with jitter swinging by tens of milliseconds. The average matters less than the variation: Wi-Fi rarely makes your connection slow, but it very often makes it inconsistent.
How do I know if Wi-Fi or my ISP is the problem?
Ping your own router first. On Windows run ping 192.168.1.1 and on macOS or Linux ping -c 20 192.168.1.1. That round trip never leaves your home, so whatever it reports is purely the wireless link. Under 5 ms with low variation means Wi-Fi is fine and the problem is upstream. Above 20 ms, or wildly varying, means the wireless link is your bottleneck.
Is 5 GHz always better than 2.4 GHz for ping?
For latency, almost always yes. 5 GHz has far more non-overlapping channels, so your traffic competes with fewer neighbours, and it supports wider channels that clear the queue faster. The trade-off is range: 5 GHz weakens noticeably through walls. If you are far from the router, a strong 2.4 GHz signal can beat a weak 5 GHz one, because retransmissions caused by a poor signal add more delay than band congestion does.
Why does my ping spike only sometimes on Wi-Fi?
Three common causes. Power saving lets the radio sleep between transmissions and the wake-up costs milliseconds. Background scanning makes the adapter briefly leave your channel to look for other networks. And airtime contention means a neighbour's large download can delay your packets even though you are on separate networks, because you share the same radio spectrum.
Does a mesh system increase ping?
Each wireless hop between nodes adds latency, usually 3-10 ms. If your satellite node talks to the main router over the same band your devices use, that hop also halves the available airtime. A mesh with a dedicated backhaul band, or better still an Ethernet backhaul between nodes, avoids nearly all of it.
Will a Wi-Fi extender fix my ping?
Usually not — a basic repeater receives and rebroadcasts on the same channel, which roughly doubles the airtime your traffic consumes and adds a hop. It improves coverage where there was none, but for latency it is often worse than a weaker direct connection. Powerline adapters or a longer Ethernet run are better answers when the goal is responsiveness.