Reaction time hub
Reaction Time Test
A reaction time test measures the interval between a stimulus and your response. PulsarMS separates the two most useful simple-reflex modalities: a visual reaction time testfor screen-based reflexes and an audio reaction time test for sound cues. The result is not just one number; it includes the uncertainty created by your display, browser clock, input device, and audio path.
Click when the screen changes. Best for measuring screen, mouse, and visual-processing latency together.
React to a sound cue. Useful for footstep, callout, rhythm, and alert timing, with wireless latency warnings.
Prefer a gamified challenge? The 3D training Arena beta turns reaction, aim, and decision-making into scored games — training-grade, same-setup, and built on the same server-re-scored core as these tests (not a lab-grade replacement).
What does a reaction time test measure?
A simple reaction time test uses one stimulus and one response. You are not choosing between targets or solving a tactical problem; you are waiting for a signal and reacting as soon as it appears. That makes the test useful as a baseline because it isolates the fastest loop you can repeat: detect, decide, move, and click.
The number still includes more than your nervous system. In a visual test, the monitor refresh interval determines when the color change can be presented. In an audio test, speakers, headphones, codec buffering, and the browser's audio output path affect when the cue reaches your ears. That is why PulsarMS reports a visible confidence band and keeps the scoring rule explicit: visual uses median, while audio ranks by average over 10 cues.
What counts as a good reaction time?
| Visual reaction time | Interpretation | How to read it |
|---|---|---|
| < 50 ms | Not a reaction | Below the physical stimulus-to-muscle limit; excluded as anticipation. |
| 50-100 ms | Exceptional — verified | Counts when the false-start record is clean; flagged for review, not discarded. |
| 100-150 ms | Very fast / verify | Check false starts, consistency, and hardware. |
| 150-200 ms | Fast | Often seen in practiced users on controlled setups. |
| 200-260 ms | Common desktop range | A useful baseline, especially on consistent hardware. |
| 260-320 ms | Needs context | Fatigue, mobile input, low refresh rate, or distraction may be involved. |
| > 320 ms | Retest and inspect setup | Retest when rested and check the device setup. |
Audio reaction time is often faster than visual reaction time, but the comparison only means something when the output device is controlled. Wired speakers or wired headphones make the cleanest audio baseline. Bluetooth results are still useful for your own setup, but they should be treated as relative.
Why visual and audio tests need separate pages
A visual reaction time test answers a screen-first question: how quickly can you react to something that appears on a display? That matters for flicks, peeks, aim duels, traffic lights in a simulator, and any task where the visual frame is the trigger. The visual pipeline is bounded by refresh rate: 60 Hz means a new frame about every 16.7 ms, while 600 Hz means a new frame about every 1.7 ms.
An audio reaction time test answers a different question: how quickly can you react to a sound? It matters for footsteps, callouts, rhythm games, warning tones, and sports starts. Browser audio can schedule sound precisely, but a web page cannot directly measure the physical delay inside your headset or speakers. That limitation is the reason our audio test is explicit about output latency and Bluetooth uncertainty.
Build your baseline before you optimize
Run five clean trials, ignore your single best score, and track the median. A new mouse, monitor, warmup routine, or sleep schedule is only meaningful if your median improves beyond the confidence band and stays improved across multiple sessions. The best score is often luck. The median is closer to your repeatable ability.
For a deeper explanation of result quality, read the guide to reaction time score interpretation. For hardware effects, compare monitor refresh rate and reaction time with input lag vs reaction time.
The reaction time guide library
Visual reaction time measurement guide
How visual stimulus timing works, why refresh rate matters, and when a score is anticipation instead of a reaction.
Auditory reaction time measurement guide
How auditory reaction tests work, why audio is usually faster, and why browser audio still needs honest uncertainty.
Visual vs auditory reaction time
A modality comparison for gamers, coaches, and researchers who need to separate human speed from device latency.
Monitor refresh rate and reaction time
What 60 Hz, 144 Hz, 240 Hz, and 600 Hz displays change in a visual reaction-time measurement.
Input lag vs reaction time
The millisecond stack from stimulus to click: display, browser, mouse, USB polling, operating system, and scoring.
Reaction time score interpretation
What your median, best trial, standard deviation, false starts, and confidence band actually mean.
Browser reaction time test accuracy
What a browser can timestamp well, what it cannot observe, and why uncertainty belongs in the result.
How many trials you need
Why one click is not a measurement and how to use medians, repeated sessions, and clean protocols.
Compare scores across devices
A controlled protocol for comparing monitors, mice, keyboards, phones, browsers, and audio devices.
Simple vs choice reaction time
Why PulsarMS measures a reflex floor and why game decisions take longer than simple reactions.
False starts and anticipation
How early clicks, randomized waits, and sub-100 ms results change the meaning of a fast score.
Average reaction time by age and hardware
Benchmarks by cohort, modality, and hardware so you compare your number against the right baseline.
How to improve reaction time for FPS gaming
Training, sleep, caffeine, warmup, and setup changes that can move your median over weeks.
Reaction time training drills
A drill framework for separating reflex speed, go/no-go discipline, recognition, and fatigue.
Sleep and reaction time
Why fatigue creates slower medians, bigger spreads, and costly lapses.
Caffeine and reaction time
How to test whether caffeine helps your median or just increases guessing.
Mobile vs desktop testing
Why phone, tablet, laptop, and desktop scores should be compared in their own lanes.
Keyboard vs mouse vs touch
How input method changes movement, event timing, and fair comparison rules for reaction tests.
TV game mode and display latency
Why couch and console setups need game mode, low processing, and their own visual baseline.
Bluetooth audio latency and reaction time
Why wireless audio can hide more delay than the human auditory reaction itself.
Wired vs wireless audio latency
How wired, 2.4 GHz, Bluetooth, and speaker paths affect auditory reaction baselines.
Audio cue design
How tone attack, volume, masking, and output path change auditory reaction-time results.
Time of day and reaction time
How sleep inertia, fatigue, caffeine timing, and daily rhythm can change your median and spread.
Reaction time vs aim speed
Why fast detection is only one part of FPS aiming, flicking, tracking, and accuracy.
FPS peeker's advantage
How human reaction time interacts with display, input, server, and network latency in corner duels.
Frequently asked questions
What is a good reaction time?
For a simple visual reaction time test, 200 to 260 ms is common for healthy adults and 150 to 200 ms is fast. Results below 100 ms are usually anticipation — but not always, so PulsarMS verifies them behaviorally — false-start record against randomized waits, and consistency — instead of discarding them outright. Only results below the ~50 ms physical limit are treated as non-reactions. Audio reaction times are often faster than visual times, but device latency can distort both.
Is visual or audio reaction time faster?
Auditory reaction time is usually faster because the signal path and processing load differ from visual detection. On the web, audio scores must still be interpreted carefully because speakers, headphones, Bluetooth codecs, and browser output latency can add delay.
Does monitor refresh rate affect reaction time tests?
Yes. A 60 Hz display presents a new frame every 16.7 ms, while a 600 Hz display presents one about every 1.7 ms. A higher refresh rate reduces visual quantization and can make measured scores more consistent, but it does not make your nervous system faster by itself.
Why does PulsarMS show a confidence band?
The confidence band shows timing uncertainty from browser clocks, display refresh, and modality-specific limits. It stops a single millisecond number from pretending to be more exact than the browser and hardware can support.
Methodology and sources
PulsarMS uses randomized foreperiods, 10-cue audio sessions, and modality-specific confidence bands to reduce anticipation and expose measurement uncertainty. The browser timing model is based on frame-aligned visual presentation and Web Audio scheduling. For implementation background, see MDN's documentation for requestAnimationFrame and the Web Audio API. For a public benchmark comparison, Human Benchmark notes that its reaction test is also affected by computer and monitor latency.