Why Low Latency Matters So Much to Online Game Players

My friend Dana once spent a whole evening convinced she had forgotten how to play Rocket League. Shots she would normally hit were whiffing, the ball seemed to teleport, and she kept arriving a fraction late to every challenge. Her internet plan was 500 Mbps. Her ping in the scoreboard, which none of us had thought to check, was jumping between 40 and 190 milliseconds.

That gap between "fast internet" and "a good connection for games" is the thing I most want new players to understand. Online games barely care how many megabits you can download. They care how quickly a tiny packet can get to the server and back, and whether that time stays steady.

What latency really is in a game

Latency is the delay between something happening on your side and the server learning about it, plus the delay coming back. Games usually show it as ping, measured in milliseconds of round trip time. When you click to shoot in Counter-Strike 2 or Valorant, your input travels to the match server, the server decides whether you hit, and the result travels back to you and everyone else.

Three numbers matter, not one:

• Ping, the average round trip time. Under 30 ms feels crisp, 30 to 70 ms is fine for most games, and above about 100 ms you start feeling it in fast shooters and fighting games.
• Jitter, how much ping varies from moment to moment. A steady 60 ms is often nicer than a ping that bounces between 20 and 90.
• Packet loss, the share of packets that never arrive. Even 1 or 2 percent shows up as rubber banding and actions that do not register.

Dana's average ping was not terrible. Her jitter was awful, and that is what made the ball seem to jump around.

How games hide the delay

No online game can make latency disappear, because light in fiber is not instant and routes between cities are not straight lines. So developers hide it with netcode, which is the set of tricks a game uses to keep things feeling responsive.

Prediction and lag compensation

In most shooters, your client predicts your own movement immediately instead of waiting for the server. You press forward and your character moves now, and the server corrects you later if it disagrees. When you shoot, the server rewinds its record of where enemies were by roughly your ping and checks whether you hit them at that moment in the past. This is lag compensation, and it is why you sometimes die after you are already behind cover on your screen. On the shooter's screen, you were still exposed.

Rollback in fighting games

Fighting games went a different route. Titles like Guilty Gear Strive and Street Fighter 6 use rollback netcode. Each side guesses the opponent's next input, usually "same as last frame", and plays on. When the real input arrives and the guess was wrong, the game rewinds a few frames and replays them correctly. With good connections the corrections are invisible. With bad ones, characters visibly snap. Older delay based netcode simply waited for both inputs, which made every move feel sluggish once ping rose.

Tick rate plays a part too. A server running 64 updates per second only checks the world every 15.6 milliseconds, so there is some built in delay no matter how good your line is. I covered why studios pick particular tick rates in how online game servers keep millions of players connected.

The advice I would ignore: buy a faster plan

The most common fix people suggest for lag is upgrading the internet package. For gaming specifically, that rarely helps on its own.

A competitive match in most shooters uses well under 1 Mbps in each direction. Going from 100 Mbps to 1 Gbps changes nothing about how long a packet takes to reach a server in Frankfurt or Virginia. What does change latency is distance to the server, the route your provider takes, and what is happening on your own home network.

That last one is where Dana's problem lived. Her roommate was uploading a large video backup while she played. The upload filled the router's buffer, so every small game packet had to wait in line behind chunks of video. This is called bufferbloat, and it is the single most common cause of "my ping goes crazy in the evening" that I see among friends. A faster plan would have moved the queue around but not removed it. Turning on a feature called smart queue management, sometimes labeled SQM or QoS in router settings, fixed it in about five minutes. Her jitter dropped from roughly 150 ms of swing to under 10.

Speed tests measure how wide the road is. Games care how long the queue is at the on ramp.

Things that genuinely lower latency

From most effective to least, in my experience with my own group:

1. Use a wired connection. Wi-Fi adds variable delay and occasional loss, especially through walls or with lots of neighbors on the same channel. A long Ethernet cable from the router is ugly and works.
2. Fix bufferbloat. Run a bufferbloat test from a browser while someone else uploads, and enable smart queueing if your router supports it.
3. Pick the right server region. Many games let you choose. Playing on a region one country closer can shave 20 ms or more.
4. Close background uploads. Cloud photo sync, game launchers patching other titles, and video calls on another device all compete.
5. Update router firmware. Less dramatic, but older firmware sometimes has poor queueing behavior.

Things that usually do not help: "gaming" DNS servers, which only affect how fast a name is looked up and not the game traffic itself, and many paid ping booster services, which can help in rare cases with a bad provider route but often add a hop instead of removing one.

When you host the server yourself

Latency feels different from the other side. When I host a Valheim or Minecraft server at home, my own ping is near zero, so I am the worst person to judge whether it feels good. My friends across town might see 15 ms, and my friend who moved to Montreal sees around 90. I now ask everyone to post their ping in chat on the first night of any new server, and I pick a hosting spot that is fair to the group rather than perfect for me.

If you host game nights at home with several consoles or PCs on the same network, the bufferbloat problem multiplies. I wrote about laying out a home network for that in finding a home setup for multiplayer gaming nights.

Here is something to try tonight. Open the network stats overlay in whatever game you play most. Most shooters have one in the settings. Play one match and watch ping, jitter and packet loss rather than just the single ping number. If the numbers swing when someone else in the house starts streaming, you have found your real problem, and it was never the size of your plan.