Keyboard Reaction Time Test
Wait for the visual signal, then press your selected key as fast as you can. Complete five valid trials to measure your keyboard-response median, best result and consistency.
5-trial median
Keyboard-only response
Local historyWait for green
Start the session, keep your finger ready, then press Space only after the panel turns green.
Mouse/touch can start the session but never counts as a measured response
Keyboard reaction history
Results are grouped by response mode. Keep the same keyboard, connection and browser when comparing sessions.
Complete a session to begin your keyboard-reaction history.
| Date | Median | Best | Consistency | Key mode |
|---|
Your response plus the input chain
The timer starts when the browser presents the visual go state and stops when the matching keydown event reaches the page. Your result therefore includes perception, decision and finger movement plus switch actuation, keyboard firmware, USB or wireless transport, operating-system handling and browser delivery.
Not pure keyboard hardware latency
A browser cannot see the instant your finger physically actuates the switch, so it cannot isolate switch debounce, scan rate, USB polling or true key-to-photon hardware latency without external measurement equipment.
Use this page for a repeatable keyboard-response task, not as a laboratory certification of the keyboard itself.
One input method per benchmark
The main Reaction Time Test allows a general response. This page fixes the response channel to the keyboard so repeated sessions are easier to compare.
Keyboard reaction test FAQ
Is this a keyboard latency test?
Not in the hardware-lab sense. It measures the full browser-observed response from visual signal to keydown, which includes your human reaction and the keyboard/input path. Pure hardware latency requires external equipment.
Why use Spacebar or Enter?
They are easy to hold a finger over without needing to search for a letter. The Any Key mode is available if you want to use another normal key consistently.
Do held keys count?
No. Auto-repeat keydown events are ignored, so holding a key cannot generate valid trials.
Does Bluetooth affect the result?
Potentially. Wireless transport and power-saving behavior can change the input path. Compare the same setup across runs, or deliberately compare wired and wireless sessions on the same computer.
Can I use this to compare two keyboards?
Yes as a practical human-plus-device comparison, provided you keep the same computer, display, browser, response key and testing conditions. It still does not isolate hardware latency from your own reaction variability.