"My ping is 90 and my friend on the same server gets 30." "My ping is 20 and twice a minute the game freezes and snaps me back three steps." Those two sentences arrive with the same word attached and have almost nothing in common — and sorting out which one you have is most of the work, because the fixes do not overlap.
Three symptoms, three different causes
- A high baseline. Every match, every server, the same figure. Mostly distance and routing, and the one you have least control over.
- Spikes. The average is good and the number jumps periodically. Something on the path — often something you own — is queueing your packets for a moment.
- Rubber-banding with a healthy average. Positions correct backwards, shots do not register. That is jitter and packet loss, and neither shows up in an average.
What ping is actually made of
Four things:
- The distance to the server and the route taken to it. Signal in fibre is not instant, and the route is rarely a straight line. Nothing on your PC changes it.
- Queueing. Every device between you and the server holds packets when more arrives than it can send. Your own router usually has the deepest buffer, and it is the one you can do something about.
- The last metre, where a wireless link is a shared, interference-prone medium and a cable is not.
- The server itself, and the state of the match on it.
That first item is why the floor matters: the lowest of several probes is close to real distance, and everything above it is queueing. That split is the whole diagnosis, and it is why a single ping figure tells you so little.
Measure before you change anything
w0a's Game Server Ping page measures a reference endpoint in each region rather than the match server, because the platform assigns a server per match and does not publish its address — so what is measured is the city, the distance and the route. Three numbers per region: the lowest of several probes, the jitter (the average difference between consecutive samples), and the percentage of probes that went unanswered.
The Latency Test page is not this. It measures your mouse, your drivers and your display — the delay between your hand and the screen. It has nothing to say about the network, and confusing the two sends you after the wrong problem. Reading the latency test covers what it does measure.
Spikes at a steady interval, only on Wi-Fi
This one has a known mechanism. To find networks, a Wi-Fi adapter scans the other channels, and Microsoft's documentation spells out the cost: "it becomes more difficult for a wireless interface to send and receive data packets while a scan is occurring", so a scan "may increase latency until the network scan is complete". By default, the same page says, Windows asks the adapter for a scan only every 60 seconds, and sometimes not at all while you are connected; other programs can ask for scans too (Microsoft Learn). The result can be a spike that comes back at a steady interval and never happens on a cable.
w0a's Process Manager page covers it: Wi-Fi quiet is one of the parts of the single Game Mode switch. While a game runs, w0a asks Windows to switch off background scanning on each wireless adapter, and the request ends when the game does, or sooner if w0a closes. Like every engine here, Game Mode is off on a new installation and stays off until you turn it on. If your adapter's driver accepts the request and keeps scanning anyway, the page says so rather than claiming a fix.
The ping is fine until someone downloads
Then it is not the internet, it is a queue filling up: when a device is handed more than the line carries, packets wait in a buffer, and a buffer that is too deep turns a full line into a tenth of a second of added delay.
Measuring it is simple — round trips on a quiet line, then again while the connection is saturated in each direction. What you find is not fixable from a PC, because the buffer is inside your modem or router. What empties it is SQM (fq_codel or cake) turned on there, or a shaped rate set on that device slightly below your line speed. No Windows setting reaches that device.
The other half is your own machine: Windows Update, the Store and app updaters download through a background transfer service, competing with your match for the same line and the same disk. The Process Manager page can pause them for the duration of a game, with security updates never paused.
Three things about the path worth knowing once
Three questions about the path only need answering once per connection, and they deserve separate answers because the evidence behind them is not equally strong:
- Address translation. Look at the WAN (internet) address on your router's status page. If it is a private address (10.x.x.x, 172.16–31.x.x, 192.168.x.x), something in front of your router is translating as well — usually the provider's modem-router, and then the fix is on your side: bridge mode on the modem, or access-point mode on your own router. If it falls in 100.64–127.x.x, the range reserved for carrier-grade NAT (CGNAT), your provider is doing the translating: a port you open on your router, by hand or through UPnP, stays closed there, and asking them for a public IP address is the usual way out.
- Hop distribution. The part of the path before your traffic reaches globally routed space can only account for a bounded share of your delay — a ceiling, not a measurement.
- Path MTU. A path that silently drops large packets produces connections that open and then stall, which people report as lag.
When the "lag" is not the network
Frame-time stutter feels exactly like a network hitch: the world stops for a moment and then catches up. The difference is decidable — capture frame times and look. If frames were arriving late, the network was innocent and why games stutter on Windows 11 is the list to work through.
One cause sits in both worlds: a network driver that holds a processor core inside an interrupt stops the machine drawing and reading input, and that has nothing to do with ping. DPC latency covers how to see it.
What does not lower your ping
- TCP tuning. Competitive shooters send their match traffic over UDP, which none of the TCP settings touch. Network tweaks goes box by box and says the same thing in its first sentence.
- Traffic marking. w0a no longer writes a QoS policy for a game: providers mostly ignore the mark, and some treat marked traffic as something to police. If an older version wrote one, the network settings card removes it.
- DNS. A faster resolver changes how quickly a name is looked up, not your in-match ping. Internet connection and DNS is the card for a resolver left in a bad state, and legacy TCP settings removes what an old "optimizer" script left behind — both repairs, neither a gain.
What is actually worth doing
A cable instead of Wi-Fi. SQM on the router if anyone else uses the line while you play. A less crowded channel and a shorter path to the access point if a cable is impossible. Then measure once more and stop — the remaining number is distance, and distance is not a setting.
Related
- Network tweaks
- DPC latency
- Why games stutter on Windows 11
- How to reduce input lag: what software can and cannot shorten
What a game booster or optimizer can change in Windows, what it cannot, and how to check one before you trust it: Do game boosters and optimizers actually work?
Did this page help?
What was missing, or what did not work? We read every one of these.
If this page did not solve it, write to us — say which article you read, and we will fix the article.