Reaction Time Test
Around 250 milliseconds is common in simple visual browser tests; around 200 ms is fast. Test your reaction time in five trials and see your median, best score and consistency. Browser and device timing affect results.
Click to begin
Wait for green, then click or tap as fast as you can. Early responses do not count.
or click the panel · Space also works
These are approximate visual-test reference points, not a clinical standard or a percentile. Different tasks and devices produce different timings. How to interpret your score →
Your browser and device are part of the timing. We do not guess away hardware delay.
Your setup changes the number
Your display, input method and system can shift the result. ReactionMetric uses the closest comparison with enough real results.
One lucky click is not your reaction time
ReactionMetric also reports your best result and consistency so you can separate a repeatable baseline from one exceptional click.
Milliseconds Test: Measure Your Reaction Time in ms
A milliseconds test measures how long it takes you to respond after a signal appears. One second equals 1,000 milliseconds (ms), so a 250 ms result is one quarter of a second.
How does a millisecond reaction test work?
ReactionMetric measures from the browser switching the test to GO on an animation frame until your click, tap or key response is detected. Your display and input hardware still add delay, so this is browser-observed timing rather than the exact instant a screen pixel changes. Five valid trials are used, with the median shown as your main score so one unusually fast or slow attempt has less influence.
How this relates to a reaction time test
They are the same core task here: your reaction time is reported in milliseconds. The number includes browser, display and input-device timing, so compare repeated results on the same setup instead of treating a small cross-device difference as a pure change in human reaction speed.
Test a different kind of speed
Keyboard Reaction Test
React to a visual signal with Space, Enter or another normal key across five valid trials.
Sound Reaction Test
React to a browser-generated tone across five valid trials and compare your local audio median with visual reaction history.
F1 Reaction Test
Face a five-red-light start sequence across five valid launches, with false-start tracking, median and consistency.
Double Click Test
Check for accidental rapid repeat events with guided single-click sampling, button lock and interval evidence.
CPS Test
Measure clicks per second across 1, 5, 10, 30 and 60 second modes, with peak speed, consistency and local personal bests.
Visual Reflex Test
Find the green target among distractors and measure a different visual-response task.
Understand and improve your score
Average Reaction Time
See research-backed context for common scores, browser/device limits, age effects and first-party benchmark rules.
How to Improve Reaction Time
Use your local baseline, run a controlled practice block, and follow a repeatable training and measurement protocol.
Reaction Time by Age
Explore study-level age trends without fake age percentiles or browser-score correction.
Reaction time test FAQ
What is a good reaction time?
On a simple visual browser test, a repeatable median around 200 ms is fast, around 170 ms is very fast, and roughly 250 ms is still common. One lucky click matters less than your five-trial median. For a 13-year-old, use age-specific evidence rather than a universal cutoff. See Average Reaction Time for broad context and Reaction Time by Age for age-specific evidence.
Is a 100 ms reaction time possible?
A true 100 ms visual response is possible but exceptional. ReactionMetric excludes responses under 100 ms because they are too early to treat as reliable post-signal reactions. Scores near 100 ms should be repeated across several trials, since responding early, display timing and input hardware can all push a browser result downward. See the Methodology for the exact validity rules.
Why is my score different on another test or device?
Because browser reaction tests measure the whole path from visual change to your input, not your nervous system alone. Different displays, refresh rates, mice, keyboards, browsers and test rules can shift the result. Compare repeated runs on the same setup first, then treat cross-site differences cautiously. See Science & Measurement Notes for why equal millisecond gaps are not always equivalent.
Does monitor refresh rate affect my score?
Yes, it can affect the browser-observed number. A higher refresh rate can shorten the wait for a new frame to appear, which may reduce part of the measured delay, but it does not make your nervous system faster by itself. Keep the same display when tracking improvement, and see Science & Measurement Notes for device-stack limitations.
Should I compare my best score or my median?
Use your five-trial median as the main benchmark. Your best click is useful as a ceiling, but it is more sensitive to luck and unusually early responses. The median better represents repeatable performance because one extreme trial has less influence. Use the best score as supporting context, and see the Methodology for why ReactionMetric makes median the headline result.
Is this the same as a reflex test?
Not exactly. This page measures simple visual reaction time: one signal appears and you respond. The Visual Reflex Test adds spatial target detection and distractors, so it is a different browser task. Neither is a clinical neurological or tendon-reflex exam. If you want the target-finding version, use the Visual Reflex Test.