"What's a good reaction time?" is the most-asked question about reflexes — and almost every answer online ignores the biggest variable: the hardware you measured it on. Let's fix that. For the broad testing workflow, start with the reaction time test hub.
Rough simple reaction-time ranges
Simple reaction time (one stimulus, one response - what PulsarMS measures) varies by age, attention, hardware, task design, and input method. Treat the ranges below as orientation, not diagnosis or lab-grade norms:
| Context | Visual median guide | Notes | |---|---|---| | Rested desktop user | ~200-260 ms | Common simple visual baseline on ordinary hardware | | Practiced gamer or athlete | ~150-200 ms | Fast, but still setup-dependent | | Phone or touch input | Often slower | Touch posture and device pipeline differ | | Fatigued or distracted session | Often slower and less consistent | Watch the slow tail and false starts | | Older adult sessions | Often slower on average | Age, health, task design, and hardware all matter |
Auditory reaction time is often faster than visual reaction time in controlled simple tasks, but the gap is not a universal constant. Output device latency can erase the advantage. Run both our visual and audio tests on the same setup, then compare visual median against the audio average from its 10 cues.
Reaction-time sessions often have a slow tail: a few late responses caused by attention lapses or distraction. That's why we report your median, which is more robust than a small sample mean.
The variable nobody controls for: your screen
Here's the uncomfortable truth. A reaction-time number measured on a 60 Hz laptop and one measured on a 240 Hz gaming monitor are not cleanly comparable. Display refresh, panel behavior, input device, browser mode, and posture all change the practical response loop before your training does anything.
That's why we:
- record your display refresh rate with every visual result,
- show a ± confidence band that reflects your hardware,
- and label audio results as relative unless calibrated.
So what's your real number?
The honest answer: your browser-observed response is only as meaningful as the setup and confidence band around it. The consistency of your results matters as much as the median. A player with a steady median and tight spread has a more repeatable baseline than one bouncing between a fast guess and several slow lapses.
Related guides
If you are comparing your score against an average, read these next:
- Reaction time score interpretation explains why median and spread matter more than a single best run.
- Visual reaction time measurement guide covers screen-based reflexes and display timing.
- Auditory reaction time measurement guide covers sound-cue reflexes and output latency.
- Monitor refresh rate and reaction time explains why 60 Hz and 600 Hz results should not be compared casually.
Sources & context
These ranges synthesize public simple-reaction-time literature and PulsarMS's hardware-aware measurement model. For background, see this PMC review of factors influencing simple reaction time and the PubMed record for a visual/auditory reaction-time comparison. Read exactly how we measure before comparing scores across devices.