Reaction Time Test

A reaction time test only measures what it claims to measure if the stimulus is genuinely unpredictable. If the green flip happened at a fixed, learnable interval — say, always exactly 3 seconds after you click to start — your brain would quickly learn that timing and start clicking based on a predicted schedule rather than actually reacting to the color change. That's not reaction time anymore; it's rhythm prediction, a fundamentally different skill that would produce artificially fast, meaningless numbers.

This is exactly why the delay before green appears is randomized between 1.5 and 4.5 seconds on every single trial. There's no pattern to learn, no interval to internalize — the only way to click fast consistently is to actually perceive the color change and respond to it.

Because the delay is unpredictable by design, any click that lands before green actually appears can only mean one thing: you guessed, rather than reacted. A click during the red phase reveals anticipation, not reflexes — and if that click were scored as a valid (impossibly fast) reaction time, it would completely undermine what the test is trying to measure. Treating early clicks as faults rather than results is what keeps every recorded number honest.

| Range | Interpretation |

| --- | --- |

| Below 200 ms | Excellent — comparable to elite athletes and pro gamers |

| 180–220 ms | Typical range for pro gamers and athletes |

| ~250 ms | Average human reaction to a visual stimulus |

| Above 350 ms | On the slower side |

Click anywhere in the panel to start — the panel turns red.

Wait for it to flip to green; the delay before that happens is random each time.

Click immediately when you see green. Your reaction time is shown in milliseconds.

Click again to retry. The last 10 attempts are tracked below.

Mouse and touch input both add a small amount of hardware latency — real, physical delay between the moment your finger or hand physically completes the click motion and the moment the browser registers that click as an event. This latency is tiny, but it's not zero, and it's consistent enough to matter when comparing scores across sessions. Using the same input device across your attempts keeps that hardware latency constant, so differences in your recorded times reflect actual reflex variation rather than switching between a mouse with slightly different latency than a touchscreen.

Pressing the spacebar instead of clicking is supported specifically because keyboard input often has slightly lower latency than a mouse click — fewer intermediate hardware and driver layers between the physical press and the browser registering the event. If you're chasing your absolute best time rather than comparing consistent trials, switching to the spacebar is a legitimate way to shave a small, real amount of latency off your recorded number — just be aware that comparing a spacebar time against a mouse-click time isn't a fully apples-to-apples comparison.

The tool tracks three distinct numbers, each telling a different part of the story: your last attempt shows your most recent single trial, your best captures your single fastest reaction across all attempts, and the 10-trial average smooths out the natural variability every person has from one attempt to the next. Best time is the most persistent record — it's saved in localStorage so it survives across browser sessions — while the full attempt history resets on refresh, meaning the running average you build up during a practice session is temporary unless you note it down yourself.

Trying to anticipate the timing pattern instead of actually watching for the color change — the randomized delay is specifically designed to defeat this strategy.

Switching between mouse and touch input across attempts and expecting perfectly consistent numbers — different input methods carry different hardware latency.

Judging your reflexes from a single fast (or slow) trial rather than the 10-trial average, which better reflects typical performance.

Clicking early repeatedly out of impatience rather than waiting for the actual stimulus — this produces faults rather than a valid measurement.

Benchmarking your visual reaction speed against known human averages and elite-athlete ranges.

Comparing performance across different input devices — mouse, touch, or spacebar — to find your fastest setup.

Warming up hand-eye coordination before a task or activity that depends on quick reflexes.

Tracking whether reaction time improves with practice across repeated 10-trial sessions.

Q: What's a good reaction time?

A: The average human reacts to a visual stimulus in about 250 ms. Below 200 ms is excellent; above 350 ms is on the slower side. Pro gamers and athletes often clock 180–220 ms.

Q: Why use random delays?

A: If the delay were predictable, you could anticipate the green and click before it actually appears. Random delays force a true reaction rather than anticipation — which is exactly why clicking too early counts as a fault.

Q: Does mouse vs keyboard matter?

A: Yes — mouse and touch add a small amount of hardware latency. For the most consistent results, use the same input device across your attempts.

Q: Are my times saved?

A: Your best time is stored in localStorage so it persists across sessions. The full attempt history resets when you refresh the page.

Q: Can I use a keyboard?

A: Yes — press the spacebar instead of clicking. The spacebar often has slightly lower latency than a mouse click.

Q: Why did my time get flagged instead of recorded when I clicked right as the panel turned red?

A: If your click landed on or just before the actual color change, it likely registered as an early click — a fault indicating anticipation rather than a genuine reaction to the stimulus, which is treated differently from a valid post-green click.

Try the Reaction Time Test. Want to test something more targeted? Check the Aim Trainer or CPS Test. Curious about a different cognitive skill? Try the Number Memory Test.