Reaction Challenge
5 rounds · wait for blue, then press any buttonDetection Delay
Report timestamp → pageReaction Time
What This Test Measures
Two different numbers, both useful.
Detection Delay
Time between the gamepad report timestamp and the moment this page sees the press.
Reaction Time
Wait for blue, then press. Five rounds give you an average and best time.
Limits
End-to-end latency also includes the controller, the OS and your display — only a high-speed camera can capture all of it.
How to Test Controller Input Latency
- 1
Connect the controller with the connection you want to measure.
- 2
Read the detection delay first. It shows how quickly the page notices each new report.
- 3
Start the reaction test and press a button as soon as the screen changes.
- 4
Repeat for at least ten rounds, then compare the median, not the best single result.
- 5
Switch to another connection and repeat to compare.
What This Test Measures
Total delay runs from your thumb to the screen: controller scan, wireless link, the operating system, the browser and your display.
A browser cannot isolate the controller alone. Your reaction time adds 150–300 ms, so look at the difference between setups, not the absolute number.
Wired vs Wireless
A cable usually saves a few milliseconds compared with Bluetooth. A 2.4 GHz dongle often sits between the two.
Display settings matter more. Game mode on a TV can cut tens of milliseconds, far more than switching the controller connection.
Comparing Two Setups Fairly
Run the same number of rounds on each setup, at the same time of day, with the same browser. Fatigue changes reaction time more than you might expect.
Compare medians, not averages. One slow round can pull an average up, while the median stays stable.
Where Input Delay Comes From
Rough ranges for each stage of a typical setup.
| Stage | Typical delay | How to reduce it |
|---|---|---|
| Controller scan and report | 1–8 ms | Use a cable or a high-rate pad |
| Wireless link | 2–10 ms | Use USB or a dongle |
| Game and frame rate | 8–50 ms | Raise FPS, lower settings |
| Display | 5–60 ms | Enable game mode |
How to Reduce Input Lag
Try these changes in order. Each one is free.
Use a cable
Wired connections avoid radio delay and interference.
Enable game mode
Turn on game mode on your TV or monitor to skip image processing.
Close extra apps
Overlays, recorders and remapping tools can add delay.
Raise the frame rate
Higher in-game frame rates reduce the time before your input shows on screen.
Frequently Asked Questions
What is a good reaction time?
Most people land between 180 and 260 ms.
Why is detection delay so low?
It only covers the browser side — controller and wireless delays happen before the timestamp.
Can the browser add lag?
Yes, slightly. Close heavy tabs and keep the window focused.
Does my monitor matter?
For reaction time, yes: a high-refresh display shows the cue sooner.
What is a good input latency?
For the whole system, under about 50 ms feels responsive. The controller itself usually adds only a few milliseconds.
Why do my results vary so much?
Human reaction time changes from press to press. Run more rounds and trust the median.
Is a lower detection delay always better?
Yes, but differences of one or two milliseconds are hard to feel. Focus on large gaps between setups.
Related guides
More tools you might need
Stick Drift Test
Find out if your controller has stick drift.
Open tool →Deadzone Test
Measure stick rest noise and preview inner and outer deadzones live.
Open tool →Circularity Test
Rotate your sticks to measure circularity error, outer range and quadrant accuracy.
Open tool →Polling Rate Test
Measure your controller's polling rate in Hz with interval statistics and a live graph.
Open tool →