Statistics
Reaction Time by Device
Your measured reaction time includes your device's latency. Here's how results compare across device types in real tests.
Median reaction time by device type
Classic reaction time test. Shorter bars are faster.
- Mobile50 sessions · avg 384 ms352 ms
- Desktop / laptop36 sessions · avg 423 ms412 ms
Where device latency comes from
| Source | What happens |
|---|---|
| Display refresh | The signal can only appear on the next screen refresh: up to ~16.7 ms at 60 Hz, ~6.9 ms at 144 Hz. |
| Display processing | TVs and some monitors add processing delay; “game modes” reduce it. |
| Input device | Mice and keyboards are polled at fixed rates (125–8000 Hz); wireless links and debouncing add delay. |
| Touchscreens | Touch controllers scan the panel at fixed intervals and filter input before the browser receives it. |
| Browser & OS | Busy CPUs, background tabs and power-saving modes can delay frames and events. |
Getting comparable results
- Compare yourself against results from the same device type.
- Use a wired mouse or keyboard and close heavy background apps.
- Turn off battery-saver modes, which can throttle refresh rates.
Frequently asked questions
Is reaction time slower on a phone?
Phones and tablets can register touches with a different delay from a mouse, and screens differ in refresh rate. Compare results within the same device type for fairness.
Does a 144 Hz or 240 Hz monitor help?
Higher refresh rates show changes sooner (a 60 Hz frame is ~16.7 ms; a 240 Hz frame ~4.2 ms), so they can reduce measured reaction time slightly.
How do you know which device I used?
We classify the device type (desktop, mobile or tablet) from the browser's user agent. No device identifiers are stored.
Add your result to the data
Every completed test is saved anonymously and helps make these statistics more accurate.