Why Online Game Players Notice Every Millisecond of Lag

A web page that responds in 200 milliseconds feels fast. An online game that responds in 200 milliseconds feels broken. Same number, completely different experience, and the reason is not that gamers are fussier than everyone else. It is that games put the player inside a tight loop of seeing, deciding and acting, where every delay is felt directly in the hands.

Having spent years testing performance across browsers and devices, I find lag fascinating because it is so rarely one thing. It is a sum of small delays from different places, and players usually blame the wrong one.

Why games are more sensitive than web pages

When you click a link, you expect a short pause, and as long as it is under a second or so the experience feels fine. Research on human perception suggests people perceive responses under about 100 milliseconds as instant for discrete actions like a click.

Games are different because the interaction is continuous. You are steering a character, tracking a target or timing a jump, and your brain is constantly comparing what your hands do with what your eyes see. In that kind of loop, players can detect added delays as small as 20 to 50 milliseconds, and skilled players often notice less. A web page asks for one decision. An online game asks for a decision every fraction of a second.

The latency chain: where the milliseconds come from

Total lag, sometimes called end-to-end or motion-to-photon latency, is the time between pressing a button and seeing the result. It passes through several stages:

• Input device. A controller or keyboard polls a few hundred to a thousand times per second. Wireless devices may add a few milliseconds.
• Game processing. The game reads input once per frame, so at 60 frames per second, an input can wait up to 16.7 milliseconds before being processed.
• Rendering. The frame is drawn and handed to the display, often with one or more frames of buffering.
• Display. Monitors add processing time, and some televisions add 30 to 100 milliseconds unless game mode is turned on.
• Network. For online games, inputs travel to the server and results travel back.

Players tend to blame only the last one, but on a typical setup the local stages often add up to more than the network ping.

Frame pacing: why 60 is not always 60

A frame rate counter showing 60 can still feel rough. What matters is not the average but how evenly frames arrive. If most frames take 14 milliseconds and every so often one takes 40, the average stays near 60 but the motion stutters visibly.

This is called frame pacing, and it is a common cause of games that "feel laggy" despite good numbers. Garbage collection pauses, shader compilation and assets loading mid-game are typical culprits, especially in browser games. We cover how the code side manages this in the web code behind smooth online game animations.

Network latency, jitter and loss

Ping is the round-trip time to the server. It is the number everyone quotes, but it is only one of three network measures that matter.

Jitter is how much ping varies from moment to moment. Netcode can compensate well for a steady delay by predicting and interpolating. It struggles when the delay keeps changing, because it cannot predict when the next update will arrive. Packet loss is when data simply never arrives, forcing the game to guess or resend.

A steady 70 millisecond connection usually plays better than one that averages 40 but jumps to 150 every few seconds. The mechanisms games use to hide delay are explained in how netcode decides who wins in fast online game matches.

The "high refresh monitors are just marketing" view

You will often hear that the human eye cannot see beyond 60 frames per second, so 144 Hz or 240 Hz displays are a gimmick. This is not right, and it is worth explaining why.

Higher refresh rates help in two ways. First, motion looks smoother, which many people can clearly see in side-by-side tests. Second, and more important for lag, each frame arrives sooner. At 60 Hz a new image appears every 16.7 milliseconds. At 144 Hz it is every 6.9 milliseconds. That alone can cut ten milliseconds or more from the latency chain, before any network effect.

Where the marketing does overreach is in the claim that a faster monitor will transform a casual player's results. It reduces delay, but it will not make up for a congested wifi network or a game running at an unstable frame rate. Fix the biggest delay first.

Browser games have a few extra stages

Games running in a browser tab pass through some additional layers. The browser has its own event handling and compositing, and it may limit frame rate in background tabs or when the device is on battery. Extensions can add work to every page. An outdated browser may have slower JavaScript and graphics paths than a current one, a point we make in why online game players should keep their browser up to date.

Browsers are also improving here. Newer APIs reduce input delay, and WebTransport lets online games send real-time data without the head-of-line blocking that plain WebSockets suffer from.

A practical order for reducing lag

If a game feels sluggish, work through the chain from the cheapest fixes:

1. Turn on game mode on your television, or use a monitor rather than a TV.
2. Use a wired connection, or at least move closer to the router, to cut jitter and loss.
3. Lower graphics settings until the frame rate stays stable, not just high on average.
4. Turn off extra frame buffering or enable a low-latency mode if the game or graphics driver offers one.
5. Pick the closest server region.
6. Only then consider new hardware like a higher refresh monitor.

Players notice every millisecond because games are built around fast feedback, and every stage in the chain spends some of a very small budget. Knowing where those milliseconds go is the first step to getting them back. See more in our Games section.