INPUT TESTS / CHALLENGE

What is your reaction time?

Wait for the signal. React as fast as you can. Compare against yourself.

Reaction time

Reaction challenge

—msThis attempt
—msSession best
—msSession average

Wait for green, then click as fast as you can. Space or Enter also works.

No account. Just your browser.See the method

What a reaction-time score really measures

Your score is the gap between the go signal appearing and your click landing — and that gap includes more than your nervous system.

What this measures

The tool records the milliseconds between the go signal being triggered (when it switches to green) and your response arriving — a mouse click, a touch tap, or a Space/Enter key press, each labelled by its real input type. That path runs through your monitor’s refresh, the browser’s event loop, the operating system’s input stack and your device, so the number reflects your whole human-plus-hardware loop, not an isolated “neural” speed. The start is the moment the signal is set, a frame or so before it actually paints, so if anything the figure is slightly generous. Responses made before the signal are voided as “too soon,” so anticipation cannot inflate the result.

How to read your result

How your score compares

Simple visual reaction times are commonly cited in psychology references at roughly 200–250 ms for adults, but those come from controlled lab displays. A browser on a 60 Hz screen adds up to about 16 ms of display latency on its own, so treat any cross-site comparison with caution and compare mainly against your own earlier runs.

Reference: Mental chronometry (simple reaction time), Wikipedia

Practical tips

This is practice feedback, not a medical, cognitive or esports assessment. It measures how fast a click reached this page in this session on this hardware. See the full method →

Use a result as a starting point

Reaction scores include browser, display and input delays. Compare your own attempts with the same setup; session best and average include only valid attempts.

Does this measure hardware latency or polling rate?

No. Browser event delivery is affected by scheduling and input processing. These tools do not certify hardware latency, USB polling rate, DPI accuracy or switch lifespan.

Where do my results go?

The last 30 runs stay in this browser’s local storage. Use the history button to copy a readable report, export JSON or remove them. Raw keyboard and pointer event streams are not sent to a server by this app.

Your recent tests

Up to 30 runs on this browser. Clearing site data also removes them.

No completed or interrupted runs saved yet. Start with a quick test.