You were dead
before you knew it

This is every millisecond between an enemy appearing on your screen and them experiencing your headshot. Scroll to ride the signal from your eyeball, through your thumb, your hardware, the internet, the server, and into their brain.

// am i bad, or is my setup bad? let's actually find out //

Configure your shooter

30
Simple reaction time slows roughly 1 ms per year after your mid twenties. Small, but it stacks.
Server logs the kill
… ms
They see themselves drop
…
They feel it
…
Machine share
…
T = 0 // photons

Their head slides under your reticle

starts the clock

Light leaves your screen and hits your retina. Nothing you own can act yet. One dirty secret before we even start: everything between the server and this moment (their ping, your ping, your display) already delayed this frame. If your TV adds 80 ms of processing, the enemy has been standing there for 80 ms you never got to see. Your display lag steals from a budget you spend in the next step.

peeker's advantage

The player who moves around the corner sees you before you see them, because their movement takes a full network round trip to reach your screen. Attacking beats holding an angle in almost every online shooter for exactly this reason.

Stage 01 // meat

Your brain sees, decides, and squeezes

230 ms

Retina to visual cortex to decision to motor cortex to finger muscle. This is simple reaction time, and it is the single largest number in the entire loop. World class competitors live near 120 ms. Most humans live between 200 and 280. No purchase moves this number; only youth, sleep, caffeine timing, and thousands of hours of training do.

Stage 02 // radio

Trigger press travels to the console

6 ms

Your controller samples the trigger and radios it over. Official first party wireless protocols are fast. Generic Bluetooth pads are two to three times slower. A cable is near instant. This is the cheapest real millisecond purchase on the board, and it is still small.

polling rate

How many times per second the controller reports its state. 125 Hz means up to 8 ms of waiting; 1000 Hz means 1 ms. Esports mice poll at 1000+ for this reason.

Stage 03 // silicon

The game fires the shot

20 ms

Your input waits for the next engine tick, the simulation fires the weapon, and the fire packet is built. Sniper rifles in most shooters are hitscan: the bullet is a ray with no travel time. The stages here quantize to frame boundaries, which is why 120 fps genuinely helps: every queue in the pipeline gets cut roughly in half.

hitscan vs projectile

Hitscan weapons (most rifles, snipers) resolve instantly along a ray. Projectile weapons (rockets, arrows) simulate travel time and need you to lead the target.

Stage 04 // uplink

The packet sprints to the server

15 ms

Half of your ping. Fiber moves your kill at two thirds the speed of light. WiFi does not make this much longer on average; what WiFi adds is jitter, the random spikes, and the netcode buffers to your worst moments, not your average. A steady 40 ms connection beats a spiky 20.

ping / RTT

Round trip time for a packet to reach the server and come back. One way is roughly half. Under 40 ms round trip is good for shooters.

jitter

The variance in your ping. The silent killer. Games buffer input to survive your spikes, so high jitter quietly adds latency even when average ping looks great.

Checkpoint 1 // the moment of record

The server declares them dead

15 ms

This is where the kill actually happens. The server rewinds the world to exactly what your screen showed when you clicked, checks the ray against their head hitbox, zeroes their health, and writes the kill to the match. Score, K/D, the killfeed: all settled here, roughly a quarter second after the frame that started your squeeze. The other player is now dead in every way that counts. They do not know it yet.

lag compensation

The server trusts the shooter's view of the world at trigger time. It is why you sometimes die after reaching cover: on the shooter's screen, you never made it.

tick rate

How many times per second the server updates the world. 60 Hz means the server thinks in 16.7 ms steps. Higher tick servers settle fights with finer time resolution.

Stage 05 // downlink

The bad news rides to their console

15 ms

Half of the victim's ping. During this entire southbound trip, and for a while after, they are still playing. Strafing. Maybe lining up their own shot on you. Fully alive on their own screen, in a present the server has already overruled.

Checkpoint 2 // their screen

Their body drops on their display

45 ms

Their console applies the death on its next tick, renders the ragdoll, and their display draws it (their TV's game mode matters here exactly like yours does). Fun symmetry: your skull medal and their death animation land at nearly the same wall clock instant, about 50 ms after the server's verdict.

Checkpoint 3 // their meat

"Dang, dude. He shot me."

100 ms detect, +250 to process

Photons from their own death reach their retina, and their nervous system needs about 100 ms to detect that something happened and another couple hundred to comprehend it: sniper, that ridge, dead. Their conscious experience of your shot arrives a third of a second after the server logged it, and roughly half a second after the frame where you started squeezing.

The full loop, human to human, is a third to half a second. And most of it is meat, not machine.

Stop guessing. Measure the meat.

Everything above this line is an estimate built from the settings you picked. This part is not. Ten rounds, one number, and the loop above rebuilds itself around your actual reflexes.

Do it once now to get a baseline. Then do it the way you actually play: same chair, same screen, same controller, at the hour you normally game. Run it again after coffee, after a full day of work, after you change one thing. Save each run with a note and the pattern shows up in a week. The number you are chasing is not the lowest one, it is the one that holds steady when everything else is normal.

Find your actual problem

Pick your platform. Everything below is sourced from the platform holder's own documentation, and everything that is not gets a mark saying so. The myths section exists because most lag advice on the internet is repeated from a forum post written in 2013.

Worth doing, in order

    Do not bother

      Now pick your game

      True everywhere, and almost nobody says it

      Myths, every platform, every game

      What this page cannot measure. A web page can time its own round trips and estimate throughput. It cannot see the UDP path your game actually uses, your NAT type, your router's internals, or your ISP's routing. Anything on this page that claims to know those things would be lying, so it does not claim it. The reaction test above is the one number here that is genuinely yours, measured on your hardware.

      So... are you bad, or is your setup bad?

      Here is your loop, split into the parts you can buy and the part you have to earn:

      YOU
      MACHINE
      THEIR MEAT

      Your top fixes, ranked by real milliseconds

      The universal lag reduction checklist

      What actually works, in order of impact, for any console or PC shooter:

      1. Turn on Game Mode on your TV. A TV in movie mode runs the picture through 50 to 100 ms of processing. Game Mode bypasses it. This is the largest instant improvement most players will ever feel, and it is free. saves 50 to 100 ms
      2. Wire your console or PC to the router with ethernet. Not for average ping, for jitter. Steady beats fast. If a cable is impossible, get the console on 5 GHz, close to the router, and off the microwave's side of the house. kills the spikes that feel like 30 to 80 ms
      3. Run 120 fps if your display and game support it. Every queue in the pipeline is a frame long; halving frame time halves the queues. This is the strongest argument for a 120 Hz display purchase. saves 20 to 40 ms across the loop
      4. Use a wired or official low latency wireless controller. Generic Bluetooth pads are the slow option. saves 5 to 10 ms
      5. Pick the closest server region and turn crossplay matchmaking to your region where the game allows it. Every 1,000 miles is roughly 10 ms of round trip you cannot buy back. saves 10 to 60 ms depending on the game's matchmaker
      6. Sleep, and play your ranked games early in your session. Reaction time degrades measurably with fatigue. The meat is 60 to 70 percent of your loop; it deserves at least as much attention as your router. the biggest number on the board lives here

      Speak the lingo

      input lag / motion to photon
      Total time from pressing a button to seeing the result on screen. Good console setups: 60 to 100 ms at 60 fps.
      ping / RTT
      Packet round trip to the server. Under 40 ms is good. One way is half.
      jitter
      Ping variance. Worse than high ping, because netcode buffers to your worst spike.
      tick rate
      Server updates per second. 60 Hz is common; some shooters run 120+.
      hitscan
      Weapons whose bullets arrive instantly along a ray. Snipers in most arena shooters.
      lag compensation
      Server rewinds to the shooter's view to judge hits. Why you die behind cover.
      peeker's advantage
      The mover sees the holder first, by roughly one round trip.
      game mode / ALLM
      TV setting that bypasses picture processing. ALLM turns it on automatically when a console connects.
      VRR
      Variable refresh rate. Kills screen tearing without the added latency of v-sync.
      polling rate
      How often an input device reports. Higher is faster. 1000 Hz mice exist for a reason.