Visual Reaction Time Test
Measure your visual response time and display-to-input latency across five randomized trials, with automatic filtering for early clicks and held buttons.
Ready
How it works
This tool measures the elapsed time in milliseconds between a visual change on your screen and the moment your browser registers a click or tap. Each round begins with a randomized waiting period so you cannot predict the cue by rhythm. If you click before the visual cue appears, or if you keep the button held down during the wait, the tool rejects that attempt and asks you to repeat the trial. After five valid rounds, the tool calculates your mean score and places it on a rough reference curve.
Steps
Step 1: Click or tap the test area to start the first round and enter the randomized waiting state. Step 2: Keep your finger ready without holding the button down, then click or tap the moment the visual cue appears. Step 3: Complete five valid trials to view your five-trial average in milliseconds and your approximate percentile.
Controls
The interactive test area acts as both the visual signal and the input target. During a run, the screen tracks your current trial number out of five and shows the millisecond time for each valid click. Holding a button down or clicking during the random wait triggers a fault notice instead of a score. After five trials, the summary displays your five-trial average and an estimated percentile on a rough reference curve.
Examples
Example A: You complete five trials at 210 ms, 225 ms, 215 ms, 230 ms, and 220 ms. Your five-trial average is 220 ms, which places you above the middle of the rough curve on a typical desktop setup. Example B: You click during the random wait on round two; the tool flags an early click, ignores that attempt, and repeats round two until five clean trials are recorded. Example C: A run on a 60 Hz phone screen averages 285 ms, reflecting touch sampling and display delay alongside human response.
How to read your result
Your score reflects the combined delay of your eyes, your hand, and your hardware. Every millisecond figure includes your monitor refresh cycle, operating system input handling, mouse or touchscreen polling rate, and browser frame timing. Because hardware latency varies widely across devices, treat your five-trial average and rough percentile as a combined benchmark of you and your current setup, not as a medical, clinical, or neurological assessment.
Reference ranges
These informal ranges are commonly cited for browser-based visual tests on standard hardware and are not a medical, psychological, or clinical scale. On a wired gaming mouse and a high-refresh monitor, many practised users land around 170 to 210 milliseconds. On typical office desktops and laptops, many people land around 215 to 260 milliseconds. On phones, tablets, or wireless setups with power saving enabled, scores between 260 and 330 milliseconds are common because touch digitizers and 60 Hz panels add noticeable system delay.
Tips
On a desktop, use a wired mouse or a low-latency wireless receiver, set your monitor to its highest available refresh rate, and close background tabs that might cause frame drops. Rest your index finger lightly on the primary mouse button without pressing it down during the random wait. On a phone or tablet, disable low-power mode so the screen runs at full refresh rate, and tap with the pad of your thumb or index finger held just above the glass.
FAQ
What does this reaction time test actually measure?
It measures the total time in milliseconds between the browser drawing the visual cue and receiving your click or tap across five valid trials. It always includes device and display latency, and it does not provide a medical, clinical, or psychological measurement of pure human reflexes.
Why do two runs on the same device give different averages?
Human attention naturally fluctuates from moment to moment, and the randomized wait prevents rhythm guessing. In addition, your screen refreshes at fixed intervals and background browser tasks can shift frame timing by several milliseconds between trials, causing small changes in your five-trial average.
How should I run this test on a phone or tablet?
Hold the device steady or rest it on a flat surface, and tap the test card with your finger hovering just above the screen. Do not rest your finger on the glass during the waiting phase, as the tool ignores held touches and early taps.
Where are my reaction time results stored?
All trial times and averages stay in your browser on this device. Nothing is collected or uploaded to any server. Your lowest average scores may be saved in local storage on this device so you can compare future runs, and clearing site data removes them.
What do a low millisecond score and a high millisecond score mean here?
In this test, a lower millisecond number means a faster combined response from your hardware and your hand, which places you higher on the rough percentile curve. A higher millisecond number simply means more delay occurred, often due to a 60 Hz display, touchscreen buffering, wireless lag, or momentary distraction.
Privacy
This page runs entirely in your browser on this device; no test results are collected or uploaded, though personal records may be saved in local storage on this device.