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.
Wait for green
Start the session, keep your finger ready, then press Space only after the panel turns green.
Mouse/touch only starts the session · held or repeated keys do not count
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 response from the visual signal to the browser receiving your key press, so your reaction, display, keyboard, connection and computer all contribute. Pure keyboard latency requires external equipment. Use this test for repeatable human-plus-keyboard comparisons, not hardware certification.
What is a good keyboard reaction time?
There is no universal browser cutoff because the score includes both your reaction and the input/display chain. A lower, repeatable five-trial median is better. Keep the same key, keyboard, display and browser when tracking improvement, and compare against your own saved sessions before treating a small difference as meaningful.
Does Bluetooth affect the result?
It can. Wireless transport and power-saving behavior may add delay or variability to the input path, though the amount depends on the keyboard and system. For a useful comparison, keep everything else the same and run several sessions wired and wireless rather than relying on one trial. See Science & Measurement Notes for measurement limits.
Can I use this to compare two keyboards?
Yes, as a practical human-plus-device comparison. Keep the same computer, display, browser, response key and testing conditions, then compare multiple five-trial medians for each keyboard. A repeated difference is more useful than one best press, but the result still does not isolate pure hardware latency from your own reaction variability.