- Click your blocker’s icon in the toolbar (uBlock Origin, AdBlock, Ghostery, Brave Shields, etc.)
- Turn it off for
clickspeedtest.info - Reload the page
Reaction benchmark
Reaction Time Test
Click the moment the panel turns green. Five attempts, then your average, your best and how consistent you were — plus an honest estimate of how much of that number is your hardware rather than you.
Click to begin
Wait for green, then click as fast as you can. Five attempts.
Average
—
Best
—
Consistency
—
Too early
0
Your score is not purely your reaction time. Somewhere between 20 and 60 ms of it is your monitor and mouse, not your nervous system. The next section breaks that down — it is the reason two people with identical reflexes can score 40 ms apart.
What a reaction time test measures
This is a simple visual reaction test: one stimulus, one response. The panel turns green, you click, and the gap between those two events is recorded in milliseconds. Repeating it five times and averaging is what makes the result meaningful — a single attempt tells you almost nothing, because the variation between consecutive attempts from the same person is routinely 30 ms or more.
What you are measuring is a chain: light reaches your eye, your retina converts it, the signal travels to the visual cortex, your brain recognises the change and issues a motor command, the command travels down your arm, and your finger contracts. Most of the elapsed time is neural processing rather than nerve travel.
Why your score is not purely your reaction time
This is the part most reaction tests leave out, and it explains most of the confusion about scores.
When a browser decides to turn the panel green, the colour does not appear instantly. It waits for the next display refresh, then the monitor takes time to actually change the pixels. When you click, the mouse waits for its next polling interval, then the operating system and browser deliver the event. All of that sits inside your measured number.
- Display refresh wait — up to 16.7 ms at 60 Hz
- Panel response — about 8 ms typical
- Mouse polling — 8 ms at 125 Hz
- OS and browser handling — a few ms
- Your actual reaction — about 200 ms
| Source of delay | Typical contribution | Notes |
|---|---|---|
| Display refresh wait | 0–16.7 ms at 60 Hz 0–6.9 ms at 144 Hz | Random per attempt — you land somewhere in the frame |
| Panel response time | 1–20 ms | Highly variable: OLED and fast TN are quick, older IPS and VA slower |
| Mouse polling | 1 ms at 1000 Hz 8 ms at 125 Hz | See the polling rate test |
| OS and browser event handling | A few ms, variable | Higher under load |
| Your actual reaction | ~150–250 ms | The part that is genuinely you |
The practical consequence: a 60 Hz monitor and a 125 Hz office mouse can add 25–45 ms compared with a 144 Hz display and a 1000 Hz gaming mouse. Someone scoring 240 ms on the first setup and someone scoring 205 ms on the second may have identical reflexes. Compare your score against your own previous scores on the same hardware, not against a stranger’s.
What counts as a good reaction time
These ranges are for the average of several attempts on a simple visual test, measured in a browser — so they include the hardware overhead described above.
| Average | Tier | What it means |
|---|---|---|
| Under 180 ms | Exceptional | Rare on browser-based tests; usually fast hardware plus genuine speed |
| 180–220 ms | Fast | Strong, typical of practised younger adults on good hardware |
| 220–270 ms | Average | Where most adults land |
| 270–320 ms | Below average | Common when tired, distracted, or on a 60 Hz display |
| Over 320 ms | Slow | Worth retesting rested before reading anything into it |
How this test measures
- The delay before green is randomised between roughly 1.5 and 5 seconds, so you cannot learn the rhythm and anticipate it.
- Clicking before green counts as too early and does not produce a time. It is tracked separately, because a low average built from anticipation is not a reaction time.
- Five attempts, then the average, the best single attempt, and a consistency figure derived from how much your attempts varied.
- Consistency matters more than people expect. Someone averaging 240 ms with tight spread is more reliably fast than someone averaging 230 ms who ranges from 180 to 300.
- Your best average is stored in your browser only. Nothing is uploaded.
One honest limitation: browsers deliberately coarsen timer precision as a defence against timing-based attacks. At the scale of a 200 ms measurement that is negligible, but it is another reason to treat single-millisecond differences between attempts as noise.
What actually changes your reaction time
Things with a large effect
- Sleep. The single biggest lever. A night of poor sleep can add 30–50 ms, more than most hardware upgrades will ever save you.
- Attention and expectation. Knowing roughly when the stimulus is coming is worth tens of milliseconds, which is exactly why this test randomises the delay.
- Age. Simple reaction time is fastest in the late teens and twenties and slows gradually after, though the effect within any age band is smaller than the difference between individuals.
- Alertness and fatigue. Time of day, hours awake, and mental load all move the number measurably.
Things with a smaller effect
- Caffeine. A modest improvement in alertness-limited conditions, which mostly means it helps when you are tired rather than making a rested person faster.
- Practice. Repeated testing produces a real but limited improvement, and much of the early gain is learning the task rather than reacting faster.
- Hand and finger used. Small and inconsistent between people.
What does not meaningfully change simple visual reaction time is anything marketed as a reflex supplement or a brain-training app promising transferable gains. The honest position is that you can be well rested, alert and practised at this specific task, and that is roughly the extent of the control you have.
Simple versus choice reaction time
This test measures simple reaction time: one stimulus, one response, no decision. It is the fastest kind and the easiest to measure consistently.
Choice reaction time — where you must decide which of several responses to make — is substantially slower, typically by 100 ms or more, because a decision stage is added. This is the more realistic model for gaming and driving, where you rarely just react to a single known cue. A fast simple reaction time does not guarantee a fast choice reaction time, which is part of why this number predicts real-world performance less well than people assume.
Troubleshooting an odd result
| What you see | Likely cause |
|---|---|
| Every attempt over 300 ms | 60 Hz display plus a slow mouse, background CPU load, or genuine tiredness. Retest rested with other tabs closed. |
| Wildly inconsistent attempts | Anticipating rather than reacting, or something intermittently loading in the background |
| Repeated “too early” | You are guessing the timing. Let the colour actually change before moving. |
| Much slower than another site reported | Different tests measure differently, and hardware overhead differs by machine. Only compare like with like. |
| Under 120 ms | Almost certainly anticipation rather than reaction — human visual reaction does not go meaningfully below about 150 ms |
FAQ
What is a good reaction time?
On a browser-based visual test, most adults average between 220 and 270 ms. Under 220 ms is fast and under 180 ms is exceptional. Those ranges include monitor and mouse delay, so they are not purely your nervous system.
What is the average human reaction time?
Around 250 ms for simple visual reaction is the figure usually quoted, drawn from large web-based datasets. Treat it as a rough anchor rather than a precise benchmark — those datasets do not control hardware, attention or effort.
Why is my reaction time slower on this test than another site?
Different tests randomise differently, count differently, and run on your specific hardware. A 60 Hz monitor with a 125 Hz mouse can add 25–45 ms versus a 144 Hz display with a 1000 Hz mouse. Compare your scores against your own, on the same setup.
Can I improve my reaction time?
Somewhat. Sleep and alertness are by far the largest levers, and practice at this specific task produces a real but limited gain. Faster hardware lowers the measured number without changing your actual reflexes. Claims of large transferable improvements from training apps are not well supported.
Does reaction time matter for gaming?
Less than commonly assumed. Games mostly demand choice reaction — deciding between responses — which is slower and less correlated with simple reaction time. Game sense, positioning and aim consistency generally matter more than raw reflex speed.
Why does clicking early not give me a score?
Because it is not a reaction. If you move before the stimulus appears you are anticipating the timing, which would produce an impossibly low number. Those attempts are counted separately so the average stays meaningful.
How is this different from a click speed test?
A reaction test measures how fast you respond once to a single cue. A click speed test measures how many times you can click in a set window. One is latency, the other is throughput — they are unrelated skills.
Sources
- MDN Web Docs — Performance.now(). Why browsers deliberately reduce timer precision, and why sub-millisecond differences between attempts are noise.
- MDN Web Docs — Event.isTrusted. The flag separating a real click from one produced by a script.
About · Contact · Privacy Policy · Affiliate Disclosure
Related tests and guides
- Click Speed Test — measure your CPS, 1 to 60 seconds
- Mouse Polling Rate Test — how much of your latency is the mouse
- Mouse Click Test — check your buttons register cleanly
- Keyboard Test — chatter, rollover and auto-repeat diagnosis
- Spacebar Speed Test — spacebar counter with auto-repeat filtered out
- Jitter Click Test — the tension-based clicking technique
- Kohi Click Test — the Minecraft PvP clicking benchmark
- CPS Test — clicks per second for left, right, both buttons or spacebar