Reaction Time Test
Measure visual reaction time with five valid attempts, false-start detection, and local history. Results include your full input and display chain.
Tests run locally in your browser. We do not upload keystrokes, pointer paths, or media.
Important
- Results include user, input device, browser, and display pipeline latency — not pure hardware delay.
Loading…
Results
- Last
- —
- Average
- —
- Median
- —
- Best
- —
- Worst
- —
- False starts
- 0
- Local best avg
- —
- Progress
- 0/5
Result distribution
No samples yet.
Local history
No local history yet.
How to use
- Click Start and wait for the green signal.
- Respond with a click/tap or Space as soon as the area turns green.
- Complete five valid attempts. False starts do not count as valid samples.
- Review average, median, best, worst, and local history.
What the result means
- Each sample is the time from the painted green signal to your response event.
- Average and median summarize five valid trials; false starts are counted separately.
- Local best average is stored only in this browser.
Limitations
- Results include user decision time plus input device, browser event path, and display pipeline latency.
- This is not a pure mouse or keyboard hardware latency lab measurement.
- Background tabs, focus loss, and reduced performance mode can interrupt or distort trials.
Troubleshooting
- Clicks do nothing after Start
- Make sure you wait for green. Early responses are false starts. Refocus the page and press Start again.
- Test stops unexpectedly
- Leaving the tab or unfocusing the window aborts a running trial for accuracy.
Related tools
Keyboard Tester
Press keys to verify browser keydown and keyup events across Windows, Mac, compact, and full-size layouts.
Mouse Test
Check mouse buttons, hold stability, movement path, and basic wheel events using the browser Pointer Events API.
Double Click Test
Analyze click intervals and possible unintended double-clicks using configurable browser event thresholds.
FAQ
Is this my true hardware latency?
No. It is total reaction time through you, the input device, the browser, and the display path.
Why five attempts?
A small fixed set balances speed with a stable average and median without turning the page into a game.