The short version
- Your absolute number is mostly your own reaction time (150–220 ms is normal) — it is not your controller's latency.
- The useful signal is relative: test wired vs wireless, or one pad vs another, and compare.
- Run several trials. A single result tells you almost nothing.
- If it's your overlay that looks delayed rather than the game, that's a Browser Source setting — not your hardware.
Jump to
"Input lag" gets blamed for a lot of things that aren't actually input lag — dropped frames, a laggy overlay, or just an unfamiliar controller. Before changing hardware, it's worth actually measuring what's going on. That takes two minutes with a browser tool and no install.
Test your controller now
Free Gamepad Latency Test
Our free tool measures your controller real report rate, its jitter and any dropped inputs — an actual hardware reading, with no reaction time mixed in — and can also compare reaction latency between two setups. It runs unlimited trials, works with PS5 DualSense, Xbox and most PC controllers, and needs no signup.
What actually affects controller latency
- Wired vs wireless: USB is consistently the lowest-latency connection. Bluetooth and 2.4GHz wireless add a small but measurable delay.
- USB hubs: passing through an unpowered or cheap hub can add polling delay versus a direct port.
- Report rate: around 125Hz is typical over Bluetooth, 250-500Hz over wired USB, and 1000Hz on high-rate competitive pads. A lower rate means more time between input updates.
- Jitter: under 1ms is a stable link; above 5ms something is interfering. Jitter, more than raw latency, is what makes an overlay look like it stutters.
- Background load: a busy CPU or throttled browser tab can distort test results independent of the controller itself.
- The game or app, not the controller: in most cases, in-game input buffering and frame pacing matter far more to "feel" than raw controller latency.
How to interpret your results
Because this is a browser reaction-time test, your absolute average (usually 150-220ms) mostly reflects human reaction time, not pure hardware latency. The useful signal is relative: run the test wired, then wireless, on the same controller and same trial count, and compare. A consistent 10-30ms gap between the two is expected; anything much larger, or highly inconsistent trial-to-trial results, points to a connection or hub problem worth investigating.
Controller lag vs overlay lag
If you're troubleshooting because your stream overlay looks delayed rather than the game itself, that's a different, usually easier fix — it's almost always a Browser Source setting in OBS or Streamlabs, not your controller's actual latency.
See the most common causes and fixes for controller overlay delay.
Fix overlay lag →