About this tool

A reaction zone switches from red to green after a randomized delay, and the tool measures how long it takes you to click after that change, reporting your last, average, and best times across five attempts.

Timing is captured with performance.now() from the moment the color change is painted to the moment mousedown fires, which measures human visual reaction time plus your mouse's own response — not true click-to-photon display latency, a distinction the tool is explicit about. It's still a useful, consistent way to compare your own reaction/setup speed over time or against a different mouse.

Key features

• Randomized-delay red-to-green visual reaction trigger
• Five-attempt test sequence with last, average, and best time reported
• High-precision performance.now() timestamping from stimulus to click
• Clear disclosure that this measures reaction time, not true display-to-click latency

Why use it

• Compare your own reaction speed consistently across sessions, mice, or setups
• Spot unusually slow average times that might point to input or display lag, not just human reflexes
• A quick, honest baseline rather than an inflated "input lag in milliseconds" marketing number

Why mouse testing testing matters

Mouse specs on the box are rarely what you actually get in practice. A mouse sold as "16000 DPI" is a sensor ceiling, not what it's configured to right now, and polling rate can silently fall back to 125Hz if a USB hub or driver misconfigures the connection. These tools measure what your system is actually reporting, not what the marketing says.

Tips for accurate results

• For the DPI analyzer, use a real ruler and move in one slow, straight line — jerky or curved movement inflates the counted distance and skews the result.
• Run polling rate and input lag tests with the mouse on the same surface and DPI setting you play on, since sensor behavior can shift with surface material.
• For click speed tests, remember that sustained "CPS" over 10+ seconds is a more honest measurement than a 1-second burst.
• If results seem inconsistent, check for OS-level mouse acceleration or pointer smoothing, which can distort raw sensor readings.

Frequently asked questions