Insights
How to Lower Ping in Online Games
Lower gaming ping by testing Ethernet, pausing heavy transfers and comparing game regions. Diagnose lag spikes and know when to contact your ISP.

On this page
The fastest way to lower your ping is to pause background downloads and uploads, try Ethernet instead of Wi-Fi, and pick the game region with the lowest measured latencyOpens in a new tab. Check your in-game ping before and after each change so you know what actually helped.
If latency spikes when your connection is busy, look at your router's queue management. If it stays high even on a quiet wired connection, the cause is probably server distance, ISP routing or a game-service issue. And remember that a faster internet plan doesn't guarantee lower pingOpens in a new tab.
In short:
- Quick wins: pause transfers, plug in Ethernet, compare game regions.
- Spikes under load: look at router queue management (SQM or QoS).
- High on a quiet wired line: the fix is likely outside your home.
Start with the quickest fixes
Begin with changes that are easy to undo and that help you tell a local problem from a distant one. Record a baseline and change one thing at a timeOpens in a new tab instead of applying a pile of "gaming tweaks" whose effects you can't tell apart.
- Record your in-game ping. Note the region, whether you're on Wi-Fi or Ethernet, and whether the reading is steady or jumpy. Keep the game's network display on screen while you compare.
- Pause heavy transfers. Stop launcher downloads, cloud uploads and any other big transfers you control. Ask others in the household whether they can pause heavy activity for a few minutes.
- Test Ethernet. Plug straight into your router if you can, and confirm your device is using that connection and not Wi-Fi. Compare the same game region under similar conditions.
- Compare game regions. Start with the nearby ones and check their latency and stability during play. Keep whichever performs best on your connection, not simply the one with the closest-sounding name.
A steadier connection after pausing an upload suggests your transfers were competing for capacity. An improvement on Ethernet points to your wireless link. Keep the changes that help, and move on to the next check when one makes no clear difference.
Repeat a promising result before you make it permanent. Network and game conditions shift, so one good run matters less than a consistent improvement under similar conditions.
Check whether the problem is actually ping
Ping is the round-trip delay between your device and a destination. Jitter is how much that delay varies. Packet loss means some data never arrives. FPS (frames per second) measures rendering performance, not network delay.
| Problem | What you may notice | Next check |
|---|---|---|
| High ping | Actions take a long time to get a server response, even when movement looks smooth | Compare game regions and quiet wired results |
| Jitter | Response timing changes, with occasional delay spikes | Compare Wi-Fi with Ethernet, and idle with busy conditions |
| Packet loss | Missing updates, interrupted movement or sudden position corrections | Check the game's loss display and compare connection types |
| Low FPS | Choppy animation while network readings stay steady | Look at rendering performance, separately from ping |
Use the game's own ping display as your baselineOpens in a new tab. Note the region and compare similar play conditions, including whether others are using the connection. Symptoms overlap, so use the numbers together with what you see on screen instead of guessing the cause from stuttering alone.
A speed test can show a different ping because it usually measures a different server and routeOpens in a new tab. A good speed-test result doesn't cancel out high in-game latency, and a bad one doesn't pinpoint the game's problem on its own.
For example, if the game feels choppy but its ping and loss readings stay stable, look at rendering instead of piling on network changes. Graphics settings can help visual smoothness, but they don't shorten the network round trip.
Test Ethernet, then improve Wi-Fi if needed
In most cases, Ethernet is the best first comparison on your local network. Wi-Fi signal strength and interference can cause latency problems, while Ethernet gives you a direct connection to your routerOpens in a new tab. Testing both shows whether your wireless conditions are part of the problem.
- Keep the game region the same. Don't compare a wireless result in one region with a wired result in another.
- Connect directly to the router. Make sure Ethernet is the active connection. If needed, turn Wi-Fi off briefly for the test, then switch it back on.
- Compare average delay and spikes. A similar average with fewer spikes is still a win. Check packet loss too, if the game shows it.
- Act on the result. If Ethernet fixes the problem, work on Wi-Fi placement and interference. If it doesn't, move on to background traffic and route checks before buying any equipment.
If you can't use Ethernet, move your device closer to the routerOpens in a new tab and repeat the comparison. A better result tells you wireless conditions are worth investigating, though it doesn't isolate Wi-Fi as cleanly as a wired test.
Try the different Wi-Fi bands too, rather than assuming the higher frequency always wins. The 5 GHz band can face less interference than 2.4 GHz, but its shorter range suits devices that are close byOpens in a new tab. Test both from where you actually play and keep the one that's steadier.
Reduce lag spikes when your connection is busy
If latency climbs during downloads or uploads, your traffic is competing for capacity and queuing up under load. Background updates and cloud backups can cause latency spikesOpens in a new tab, even when you didn't start a transfer yourself.
- Compare quiet and busy conditions. Outside a match, watch latency while the connection is quiet, then during an ordinary download or upload. Keep the destination and connection type the same.
- Pause likely culprits. Check cloud backups, launcher downloads and transfers on other devices. Talk to the people you live with instead of cutting off their devices without warning.
- Look for queue-management controls. If busy periods keep causing spikes, check your router's documentation for Smart Queue Management or QoS (Quality of Service).
- Change settings safely. Only adjust a router you're authorized to manage. Save the existing settings, follow the instructions for your router and connection, and revert if latency, stability or throughput gets worse.
- Resume paused transfers. When you're done testing, restart your backups and updates. If pausing them consistently helps, schedule heavy transfers for times when you're not gaming.
Bufferbloat is excessive queuing under load: your game traffic waits behind other traffic instead of moving straight through. Queue management is meant to control that waiting. Marking gaming traffic as "high priority" isn't the same thing as controlling queue buildup, and router controls vary too much for one setting to suit everyone.
The number of connected devices doesn't prove congestion on its own. Several idle devices may matter less than one active upload, so test real traffic instead of unplugging things at random.
More bandwidth can ease competition when capacity is limited, but raw speed doesn't directly set your pingOpens in a new tab. Consider extra capacity only when your everyday traffic regularly overwhelms the connection, not because your ping looks high on a quiet line.
Choose a game region by measured latency
Nearby game regions usually have lower latency, but a slightly farther one can perform better when the nearby server is congestedOpens in a new tab. Geography is a good place to start, but it's no substitute for measuring your own connection.
- Compare nearby regions first. Use the game's region selector or latency display. Note which region it picks automatically.
- Check stability during play. Compare real in-game ping, spikes and loss, not just one matchmaking estimate.
- Confirm your party's region. When you play with distant friends, check which region the party uses. A region that suits them may be farther from you.
- Check service status for isolated problems. If only one game or region performs badly, look at that game's service status before changing your whole network.
For example, a nearby region might work best when it's quiet but become unstable at busy times. If another region consistently does better under similar conditions, let that guide your choice.
Keep the comparison fair by leaving your local connection and background traffic alone. Otherwise a region change and a paused download can look like a single improvement, and you won't know which one mattered.
The in-game display shows your live connection to that specific serverOpens in a new tab, so check it again after you join. A region label alone doesn't tell you how the current match will run.
Test alternate routes without weakening security
An alternate route is an optional experiment to try after the local fixes. It isn't a guaranteed ping cut. A tunnel can improve or worsen latency, because it changes the route and can add extra hopsOpens in a new tab.
- Keep the destination fixed. Compare the same game region with similar background traffic. Changing the route and the region at once makes the result impossible to read.
- Use permitted configurations. If you already use a privacy tunnel, compare only the routing options its controls and your organization's policy allow. Don't defeat a required kill switch to run the test.
- Understand a bypass before using it. Split tunneling sends selected traffic outside the tunnel, so your game traffic may leave outside your chosen privacy path.
- Keep security protections on. Don't turn off firewalls or certificate validation, or open ports, just to try to lower ping.
- Restore the original setup if results get worse. Keep an alternate route only if repeated comparisons show a real improvement and you're comfortable with the privacy trade-off.
A different route may help, but results are specific to your connectionOpens in a new tab. Better results through a tunnel suggest the new path suits that destination better. They don't prove your ISP is throttling game traffic.
If bypassing the tunnel conflicts with a kill switch, required privacy controls or organizational policy, leave those protections in place. Carry on with region comparisons and connection checks instead of weakening security for an uncertain gain.
Know when the fix is outside your home
If ping stays high on a quiet wired connection, the cause is more likely server distance, routing, congestion or a game-service problem. Your ISP may need to look into connection problems or outages that you can't controlOpens in a new tab.
- Repeat quiet wired tests at different times. Keep the game region fixed and note whether the problem is constant or follows a time-of-day pattern.
- Check game-service notices. If only one game or region is affected, look into that service before replacing any home equipment.
- Prepare a useful support report. Include the game and region, timestamps, in-game latency, any packet loss, your connection type and what you've already tried. Note which comparisons helped and which didn't.
- Contact the right support team. Ask game support about game-specific issues and your ISP about persistent connection problems. Describe the pattern instead of naming a cause you haven't confirmed.
Problems that only show up in the evening suggest congestion, but they don't prove throttling or tell you where the congestion is. Likewise, a speed-test result is only a rough baseline for gaming, since it measures a different destinationOpens in a new tab.
Replace equipment only when your comparisons point to a local bottleneck, and consider a plan change when your normal traffic exceeds your capacity. Neither purchase is a reliable answer to unexplained high ping on an idle line.
Distance and network routes put a limit on round-trip delay. More Mbps gives you room for simultaneous traffic, but it can't by itself shorten the trip between your device and the game server.