reaction time test

Reaction time test

Wait for the panel to turn green, then press any key as fast as you can. The test reports every attempt in milliseconds, keeps your personal best locally, and shows median and spread so you can judge consistency rather than one lucky run.

Reaction time

Wait for the panel to turn green, then respond as fast as you can with any key.

best 0.00 ms
median 0.00 ms
samples
0
median
0.00ms
mean
0.00ms
min
0.00ms
p95
0.00ms
max
0.00ms
jitter (σ)
0.00ms
distribution
no samples yet

Reaction time includes your nervous system. Most people land between 200 and 300 ms; only the few milliseconds above your measured input latency belong to the machine.

What this reaction time test measures

It measures simple visual reaction time: the gap between the moment the green cue is actually painted on your screen and the moment your key press reaches the page. That includes your own perception and motor response plus a small amount of display and input delay from your hardware.

Unit
milliseconds (ms)
Cue delay
random 1.2–3.8 s
Reported
best, median, average, spread
Storage
personal best, local only

How to use it

  1. 01Press Start and keep your hand resting in a normal position.
  2. 02Do not press early — an early press is flagged and does not count.
  3. 03React the instant the panel turns green, using any key.
  4. 04Run at least five attempts so the median becomes meaningful.
  5. 05Compare runs on the same machine, screen and refresh rate.

How the result is calculated

The cue timestamp is taken after the browser confirms the green frame has been painted, not when the state changes. Your reaction time is the difference between that timestamp and the key event. The summary shows the median, which resists outliers, alongside your fastest attempt and the spread across the session.

What affects your score

Monitor refresh rate and panel response, keyboard polling rate, browser and system load, fatigue, caffeine, sleep, and how much you anticipate the cue. Wireless peripherals and power-saving modes can add a few milliseconds. Because a browser only sees part of the chain, treat this as a consistent relative measure rather than an absolute hardware figure.

Frequently asked questions

What is a good reaction time?+
Most people land between 200 and 300 ms on a simple visual reaction time test. Regular gamers often sit in the 180–220 ms range. Anything under 150 ms usually means you anticipated the cue rather than reacted to it.
Why is my reaction time slower here than in a game?+
This test measures a cold, unpredictable cue. In a game you often pre-aim, read patterns and start moving before the visual confirmation, which feels faster than a pure reaction.
Does my monitor affect the result?+
Yes. Refresh rate, panel response and any frame buffering add time between the cue being drawn and you seeing it. A 60 Hz screen can add roughly 8 ms of average display delay compared with 240 Hz.
How many attempts should I take?+
Take at least five and read the median rather than your single fastest run. One quick sample says very little about how consistently you respond.

Related tools