Your internet speed test says 500 Mbps down and 50 up. Your ping in-game says 80ms and keeps spiking. This is not a contradiction. Speed and latency are different things, and chasing more bandwidth when lag is your problem is one of the most common mistakes gamers make.
Bandwidth is how much data your connection can carry per second. Ping is how quickly a single packet makes the round trip to the server and back. You can have gigabit internet and still have terrible ping if your router has bufferbloat, your ISP has poor routing to the game server, or your own network is congested. Understanding which problem you have is the entire first step.
Test for bufferbloat first
Bufferbloat is the most common cause of lag spikes during gaming and almost nobody tests for it. It happens when your router buffers too much data under load. When someone starts a download or a stream, the router fills a large buffer to keep the connection smooth, and your gaming packets have to wait behind that queue. Your average ping looks fine in quiet conditions, then spikes to 200ms the moment anyone else on the network does anything.
Go to DSLReports Speed Test (dslreports.com/speedtest) and run the bufferbloat test specifically. It grades your connection A through F for bufferbloat. If you get a C or below, bufferbloat is almost certainly the source of your lag spikes. The fix is enabling SQM (Smart Queue Management) or a proper QoS configuration on your router, not upgrading your internet plan.
Ethernet first. Everything else second.
I can list every other tip in this guide, but nothing matters as much as this one. A decent Wi-Fi connection might average 15ms ping to your router but add 5 to 20ms of jitter, inconsistent variation in delay. In competitive gaming, consistent 25ms feels better than average 15ms with spikes to 60ms. Jitter is what makes games feel laggy even when average ping looks acceptable.
Run Cat6 Ethernet from your router to your gaming machine. If that is physically impossible, a powerline adapter (which sends data through your home’s electrical wiring) is a significant improvement over Wi-Fi for most setups. MoCA adapters (which use coaxial cable) are even better. Both add under $50 and eliminate most of the instability that Wi-Fi introduces.
If you genuinely must use Wi-Fi: use the 5GHz band rather than 2.4GHz (lower congestion, lower latency), make sure your router is not surrounded by walls and appliances, and check which channel your neighbors are using. A congested channel adds latency. Switching to a less crowded channel in your router settings can help significantly in dense apartment buildings.
QoS: configure it correctly or not at all
Quality of Service settings tell your router to prioritize certain traffic over other traffic. When configured correctly, gaming packets jump the queue ahead of a 4K Netflix stream or a background software update. When configured badly, QoS can actually make things worse by adding processing overhead.
Log into your router’s admin panel (usually 192.168.1.1 or 192.168.0.1 in your browser). Find QoS settings. The location varies by manufacturer but is usually under Advanced or Traffic Management. The simplest approach: add your gaming PC or console as the highest priority device. More advanced routers let you prioritize by application or port, which is more precise.
If your router supports SQM or CAKE (a modern queue management algorithm), use those instead of basic QoS. They handle bufferbloat at the source rather than just prioritizing traffic, which produces better results for gaming under load. Routers running OpenWrt or DD-WRT firmware support both.
Close background bandwidth before you play
Steam, Epic Games, Windows Update, Google Drive, OneDrive, iCloud, Xbox app: all of these can be actively uploading or downloading in the background while you play. You will not see a notification. Your in-game ping will just be higher than usual and spike more frequently.
Before a competitive session, pause all downloads and cloud sync clients. Set Windows Update to active hours so it does not download mid-match. Check Task Manager’s network column to see which processes are using bandwidth. Anything above zero that is not your game is worth closing.
DNS: change it once, forget about it
Your ISP’s default DNS servers are often slower than third-party alternatives. DNS affects how quickly domain names resolve, not your ping to game servers directly, but it can affect connection time and occasionally routing. Switch your DNS to Cloudflare (1.1.1.1 and 1.0.0.1) or Google (8.8.8.8 and 8.8.4.4). Do it at the router level so every device benefits. Takes two minutes and costs nothing.
Always select the nearest server region
Data cannot travel faster than the speed of light. Physical distance to a game server adds irreducible latency, roughly 1ms per 100 miles. Most games auto-select servers, but some pick poorly. Check your in-game network settings and make sure you are connected to the region closest to you. In games that let you see server ping before joining, use it.
Under 20ms ping: excellent, you will not notice latency. 20 to 50ms: good for competitive play. 50 to 100ms: acceptable for casual gaming, frustrating in ranked. Above 100ms: you are fighting the connection as much as the game.
When the problem is your ISP
Sometimes your home network is fine and the issue is upstream. Signs that your ISP is the problem: ping is consistently high only at specific times of day (peak hours congestion), lag is worse in the evenings and on weekends, and running a ping test to your router shows low latency while a ping test to game servers shows high latency.
Run ping 8.8.8.8 -t in Command Prompt while gaming to watch for packet loss to Google’s DNS. If you see packet loss there, the issue is your connection to the internet, not within your home network. Contact your ISP with this data. It is harder for them to dismiss than a vague complaint about lag.
Fiber internet has lower and more consistent latency than cable for gaming. If you have the option and competitive gaming matters to you, fiber is worth the switch, not because of the speed numbers, but because of the latency stability.
The quick fix list
In order of impact: run a bufferbloat test and fix it if needed, switch to Ethernet, enable QoS or SQM on your router, close background bandwidth before playing, change DNS to 1.1.1.1, select nearest server region in-game, update router firmware, check for ISP-side issues if everything else is already done.
Network latency is separate from the input lag and frame time issues covered in the guide on how to reduce input lag, but they compound. Fix both and the game feels genuinely different.
