Measure input lag
Whether a controller feels slow or you want to compare wired and wireless, here is how to measure input lag and how to read the numbers.
The short version
- In a reaction test, the absolute number is mostly your reaction time, typically 150 to 220 ms, not your controller's latency.
- The useful signal is relative: compare wired and wireless, or one controller against another.
- Run several trials. A single result tells you very little.
- If your overlay looks late rather than the game, the cause is a Browser Source setting, not your hardware.
Input lag gets blamed for many things that are not input lag: dropped frames, a slow overlay, or simply an unfamiliar controller. Before changing hardware, measure what is going on. It takes two minutes in the browser, with nothing to install.
How do I test my controller?
Gamepad latency test. Measures your controller's real report rate, jitter and dropped inputs, a hardware reading with no reaction time involved. It can also compare reaction latency between two setups. Unlimited trials, works with DualSense, Xbox and most PC controllers, no signup.
What affects controller latency?
- Wired or wireless: USB is consistently the fastest link. Bluetooth and 2.4 GHz wireless add a small, measurable delay.
- USB hubs: a cheap or unpowered hub can add polling delay compared with a direct port.
- Report rate: around 125 Hz over Bluetooth, 250 to 500 Hz over USB, and 1000 Hz on competitive controllers. A lower rate means more time between updates.
- Jitter: under 1 ms is a stable link, above 5 ms something interferes. Jitter, more than raw latency, is what makes an overlay look like it stutters.
- Background load: a busy CPU or a throttled browser tab can skew results regardless of the controller.
- The game itself: input buffering and frame pacing in the game often matter more to the feel than the controller does.
How do I read my results?
In the reaction comparison, your average, usually 150 to 220 ms, mostly reflects human reaction time rather than hardware latency. What counts is the difference: test the same controller wired, then wireless, with the same number of trials, and compare. A steady gap of 10 to 30 ms is expected. A much larger gap, or results that swing from trial to trial, points to a connection or hub problem.
Is it controller lag or overlay lag?
If it is your stream overlay that looks late rather than the game, the fix is different and usually easier. It almost always comes from a Browser Source setting in OBS or Streamlabs, not from your controller.
What numbers should I expect?
| Report rate | Time between two reports | What it means |
|---|---|---|
| 125 Hz | 8 ms | A common default. Fine for most games. |
| 250 Hz | 4 ms | Noticeably tighter, especially in fast shooters. |
| 500 Hz | 2 ms | Typical of controllers built for competitive play. |
| 1000 Hz | 1 ms | The top end. Gains past this point are hard to feel. |
Jitter, the variation between reports, matters as much as the average. A few milliseconds is normal over wireless; regular spikes above 20 milliseconds point to interference or a weak battery.
Is a cable always faster?
A cable usually gives the steadiest timing. A 2.4 GHz adapter comes close, and Bluetooth tends to vary more. The honest answer depends on your controller: run the latency test once wired and once wireless, a few minutes each, and compare the average and the jitter. If wireless is close, keep it; if the jitter jumps, use the cable for ranked sessions.
See the common causes of controller overlay delay and how to fix each one.
Fix overlay lag