How to actually lower your ping: Ethernet cable, SG TCP Optimizer, and a nearby server cover 80% of the fix. No gaming VPNs, no paid tricks.
Ping isn't everything, but it's the most visible metric. If you've spent weeks noticing your shots not registering the way they should, the server reading you late in close fights, or your scoreboard flickering green and red nonstop — there are seven or eight things worth checking before you switch ISPs or drop money on a new router.
Here's what I run in my own setup (Ethernet always, ~500 Mb connection), the real levers that actually move the needle, and the commercial shortcuts (gaming VPNs, "ping boosters") that just drain your wallet.
Three numbers, not one: ping, jitter, and packet loss
Before you touch anything, understand what you're measuring:
Ping (or RTT) is the round-trip time of a packet between your PC and the game server. Good ping for competitive shooters is under 40 ms; above 80 ms you start feeling the lag.
Jitter is the variation in your ping. An average ping of 30 ms with 1 ms jitter is perfectly playable; a ping of 25 ms with 40 ms jitter is a nightmare — it means some packets arrive fast and others late, so the game stutters even though the average looks fine.
Packet loss is the percentage of packets that never arrive. Above 1% sustained, you'll feel shots not registering, animations snapping back, rubber-banding. It's the most insidious problem because it doesn't show up as "lag" — it shows up as "the game hates me."
A good gaming connection keeps all three low: ping < 40 ms, jitter < 5 ms, packet loss < 1%. If any one of those is off, you'll feel it in-game.
Rule #1: Ethernet always. Full stop.
A personal example that illustrates this perfectly: when I went from playing on a laptop over WiFi to a desktop on Ethernet, the difference showed up even in something as basic as Steam downloads — from 30–40 MB/s with fluctuations to a locked 60 MB/s on cable. And ping did what it always does: 50–90 ms variable over WiFi → 25 ms stable on cable. Another similar case: playing on a
(yes, a console plugged into a 500 Mb fiber line can only use 100 — hardware limitation of the console). That kind of bottleneck is invisible until you switch and go "oh, so that was it."
I'll say it plainly because it saves arguments: if you can run an Ethernet cable from your router to your PC, do it. There is no reasonable excuse for playing competitive on WiFi in 2026.
I've played on WiFi (when cabling wasn't an option) and the ping is much higher, not marginally. The difference between 25 ms stable on cable and 50–90 ms variable over WiFi is noticeable game after game. And it's not just average ping: jitter goes up, micro-drops increase, and in high-tickrate games (Valorant, CS2) you feel it on every peek.
If your PC and your router are in different rooms, there are two honest options:
Ethernet cable routed along the baseboard or ceiling. A 30 m flat cable doesn't cost much and is the definitive solution.
PLC (powerline): plug one adapter into the router, another into the PC, and it runs over your home's electrical wiring. Not as good as a direct cable but far better than WiFi for gaming, and that's the end of the debate. Make sure it's AV2 or better (1000–1200 Mbps nominal) or it's not worth it.
Forget WiFi extenders, repeaters, and "gaming mesh" systems. Fine for video streaming; not for competitive multiplayer.
Contracted speed: how much do I actually need?
People obsess over this and it's not the main issue. For gaming, 100 Mb is plenty. Games use very little bandwidth — the problem is never the amount, it's the quality (latency + stability).
I'm on ~500 Mb and it covers everything comfortably: streaming, large game downloads without noticing, and clean gameplay. 500 Mb is the sweet spot if you share the connection, download big games regularly, or upload content. Below 100 Mb a concurrent download can mess you up; above 500 Mb the cost/benefit doesn't make sense for almost anyone.
ISP: whichever one you have. Most fiber ISPs in Spain are decent enough. Switching providers rarely lowers your ping if your connection is stable — what actually matters is whether your local node is saturated during peak hours. You find that out by measuring (see below).
Rule #2: Tune TCP and configure your Windows adapter
The two levers that actually move the needle on the Windows side:
SG TCP Optimizer. It's a free tool from Speed Guide that tunes Windows TCP parameters (RWIN, congestion control, etc.) for your connection speed. I use it, competitive players have used it for decades, and it works. Download it, select your connection speed, choose the "Optimal" profile (not "Default"), and apply. Reboot. Done.
It's not magic. What it does is adjust values Windows leaves conservative by default so your connection doesn't get throttled on small transfers — which is exactly the pattern of an online game (small, rapid, constant packets).
Network adapter settings in Windows: go to Device Manager → Network Adapters → your adapter → Properties → Advanced. What matters:
Speed & Duplex: set it to your card's maximum (1.0 Gbps Full Duplex on a standard gigabit NIC). Leaving it on "Auto" sometimes negotiates down to 100 Mbps silently. Forcing it to max avoids that silent failure.
Receive Side Scaling: enabled.
Jumbo Frames / Jumbo Packet: only if your router/switch supports it (9014 bytes). Otherwise leave it alone.
Energy Efficient Ethernet / Green Ethernet: disabled. It puts the NIC to sleep during idle and introduces micro-stutters on wake.
These two changes (TCP Optimizer + adapter at max) are what you'll actually notice. Everything else in this guide is fine-tuning.
Rule #3: The closest server, always
Every game handles matchmaking differently, but the logic is the same: ping drops with distance. If you play from Spain, you'll get better ping on Madrid or Frankfurt servers than on London or Stockholm.
In most games you can:
Force your region in settings (CS2: `mm_dedicated_search_maxping`, Valorant: server filter, Apex: data center selector with F10 in the lobby...).
Check the ping to each server before queuing.
The other half of the rule: load matters. If your closest server is packed during peak hours and you fall over to the next one, you'll sometimes get worse average ping than on a less-saturated server even if it's farther away. Counterintuitive, and you only find out by testing.
What you should NEVER pay for: gaming VPNs, ping boosters, "accelerators"
This is unambiguous: do not install any VPN or paid service that promises "faster connection speeds" or "lower ping" for gaming. They don't work. Period.
ExitLag, WTFast, NoPing, Mudfish, Battleping... the pitch is always the same: "we route you through our optimized network and your ping drops." Physically, this cannot happen in most cases: adding an extra hop (your PC → their VPN → game server) can only maintain or increase your ping, never lower it. The rare exception is when your ISP has terrible peering with the game server and the VPN finds a better route — and that is the exception, not the rule.
And the VPN "to protect yourself while gaming": it doesn't protect you from anything meaningful. Targeted DDoS attacks against players exist but are rare (they need your IP, which isn't trivial to get). All a VPN gives you is an extra latency hop and a recurring monthly cost.
The same applies to:
"Network optimizers" like Auslogics, Net Optimizer, Game Booster: best case they replicate what TCP Optimizer does for free, worst case they leave you with unstable settings.
"Gaming" routers priced at 300–500 €: you're paying for marketing. A decent 80 € router does the same job if your connection is stable.
"Gaming" Cat 8 Ethernet cables for a 500 Mb connection: Cat 5e or Cat 6 is more than enough. Cat 8 only adds value if your internal network is running 10 Gbps, which it isn't.
If you're going to spend money on gaming, there are 20 things with better return than a VPN service or a gold-plated cable.
How to actually measure your connection
Speedtest apps measure bandwidth, but bandwidth barely matters for gaming. What matters is stability under light sustained load — which is exactly what a game produces.
What I use to diagnose:
`ping -t` from CMD to a stable server (e.g. `ping -t 8.8.8.8` or your game's server if you know the IP). Let it run for 2–3 minutes while you play and watch the variation, packet loss, and average ping.
`pathping` or `tracert`: if your ping is acting up, these tell you which hop is breaking down. Sometimes the problem isn't your home — it's your ISP's peering at hop 5.
In-game stats: `net_graph` in CS2, ping display in Valorant, server info in Apex. This is the most honest measurement because it measures your actual path to the actual game server.
Measure BEFORE you touch anything. Apply one change. Measure AFTER. If the difference is 1–2 ms, that's noise. If it's 10+ ms sustained or jitter collapses, that change stays.
Next step: Windows matters too
If you've cabled up, run TCP Optimizer, set your adapter settings, and something still feels off — the next bottleneck is usually the OS. Recommendations in Windows 11 for gaming: Ultimate Performance power plan, Xbox Game Bar off, and XMP enabled in the BIOS. Network and system are tied together: if one drags, the other feels it.
Quick summary
Ethernet always. PLC AV2+ if you can't cable. Forget WiFi for competitive.
500 Mb connection is the sweet spot. 100 Mb is fine if you live alone and don't download much.
SG TCP Optimizer + adapter settings maxed out = 70% of the Windows benefit.
Closest server, and try the next one when the closest is saturated.
Measure with `ping -t` and `pathping` before and after every change.
If you only take away three things: cable, TCP Optimizer, closest server. That covers 80% of ping problems.
Frequently asked questions
What ping is good for online gaming?
Good ping for competitive shooters is under 40 ms; above 80 ms you start feeling the lag. But ping alone isn't everything: you also need jitter below 5 ms and packet loss under 1%. If any one of those three is off, you'll feel it in-game.
Is Ethernet or WiFi better for gaming?
Ethernet always — there's no reasonable excuse for playing competitive on WiFi in 2026. The difference between 25 ms stable on cable and 50–90 ms variable over WiFi is noticeable game after game: jitter goes up, micro-drops increase, and in high-tickrate games like Valorant or CS2 you feel it on every peek. If you can't cable directly, a PLC AV2 or better is far superior to any WiFi extender.
Do gaming VPNs like ExitLag or WTFast actually lower ping?
They don't work. Adding an extra hop (your PC → their VPN → game server) can only maintain or increase your ping, never lower it. The rare exception is when your ISP has terrible peering with the game server and the VPN finds a better route — but that's the exception, not the rule. All you get is a recurring monthly cost and extra latency.
What is jitter and why does it matter more than ping?
Jitter is the variation in your ping. An average ping of 30 ms with 1 ms jitter is perfectly playable; a ping of 25 ms with 40 ms jitter is a nightmare, because some packets arrive fast and others late, so the game stutters even though the average looks fine. It's one of the three numbers you need to measure before touching anything, alongside ping and packet loss.
