How to use the Reaction Time Test
Start a round, keep your eyes on the target, and click or tap as soon as it changes state. The delay is randomized to reduce anticipation. Complete all five rounds, then repeat after a warm-up; a single unusually fast response is not a reliable baseline.
How to interpret your result
The average combines five measured intervals and is easier to compare than one round. Early clicks are excluded because they represent anticipation rather than a response to the signal. Look at spread as well as average: a consistent 230 ms can be more useful than a 190 ms outlier surrounded by slow attempts.
Important limitations
The number includes display scan-out, browser scheduling, input latency, and human response time. It is not a clinical neurological assessment and cannot separate those components. High-refresh displays may reduce presentation delay, but they do not guarantee a faster human response.
Troubleshooting checklist
Keep the tab visible, close demanding background work, and use a wired mouse when diagnosing inconsistent results. If the target appears late, test another browser and disable power-saving modes. Touch results should be compared only with touch results because input paths differ.
Practical use cases
Use repeated sessions to compare devices, browser settings, or refresh-rate modes. Coaches can track a player's median over time, while developers can use it as a rough input-latency sanity check. Always record device, display mode, and input method with the result.
Try the live tool
Frequently asked questions
What is a normal reaction time?
Results vary widely by person and setup. Compare your own median under controlled conditions rather than chasing a universal number.
Why was my first result so fast?
Anticipation or a lucky timing interval can create an outlier; the five-round average is more representative.