The fastest reaction time score is not always the best score. If a result is too fast to plausibly come from seeing or hearing the stimulus, it is probably anticipation. That is why PulsarMS treats false starts as part of the measurement, not as a side note.
What counts as a false start?
A false start happens when you respond before the actual go cue. In a visual test, that means clicking before the visual target appears. In PulsarMS's current audio test, pre-cue clicks are ignored because each cue interval is randomized; post-cue responses that are too fast to verify can still be excluded by plausibility checks.
False starts usually come from:
- clicking to a rhythm instead of reacting,
- trying to beat your previous best,
- guessing after a long wait,
- treating the randomized wait as a countdown,
- fatigue and impatience,
- touchscreen slips or mouse tension.
Why sub-100 ms scores are suspicious — but not automatically fake
Human sensory detection, decision, motor preparation, and input reporting all take time. For most people, a simple reaction below roughly 100 ms is not a clean response to a new stimulus — it is a guess, a perfectly timed anticipation, or a measurement artifact.
But "usually" is not "always," and this is where most reaction tests get lazy: they hard-discard everything under a fixed line, which silently erases the genuinely fast tail of the population. PulsarMS takes the other route. The only hard line is the physical one — below roughly 50 ms (visual) / 40 ms (audio), a press cannot have been caused by the stimulus at all, because sensory transduction, nerve conduction, and muscle activation alone take longer. Between that physical floor and the textbook line, a result counts — it is flagged "exceptional" and has to earn its place behaviorally: a clean false-start record across randomized waits, and human variance. Speed alone is never the verdict; the pattern is.
PulsarMS's reaction time score interpretation guide explains why the median is more useful than one extreme best trial.
Why there are no catch trials
Some reaction tests add catch trials — rounds where no cue ever comes, to punish rhythm-clicking. PulsarMS deliberately doesn't. A catch trial injects a go/no-go decision into what should be a pure speed measure: honest users start hesitating before every click, which inflates exactly the number the test exists to measure.
The randomized wait does the same job without the tax. Each trial's foreperiod is drawn from a wide 1.5–4.5 second window, so clicking to a rhythm produces early clicks — and every early click is logged as a false start on your record. Guessing gains nothing; it just leaves evidence. The cleaner strategy is to stay calm, wait for the cue, and accept a realistic median.
How to reduce false starts
- Relax your hand before the test starts.
- Watch or listen for the cue, not the timer in your head.
- Do not chase your best trial.
- Run another session instead of forcing a miracle score.
- Compare medians after false starts are removed.
If you are training for FPS games, false starts have a direct analog: pre-firing, flinching, or committing before the cue is confirmed. Fast wrong actions are still wrong actions.
How PulsarMS handles anticipation
PulsarMS uses wide randomized waits, early-click flags, median scoring, and server-side re-scoring for leaderboard submissions. Audio mode uses 10 randomized cues and ignores pre-cue clicks. The screening logic is deliberately behavioral: a fast median combined with repeated early clicks is guessing and doesn't rank, while a fast median with a clean false-start record counts — flagged exceptional, not erased. That does not make a web leaderboard impossible to fake, but it makes casual fake scores less useful and keeps honest users — including genuinely fast ones — from being compared against obvious anticipation or quietly deleted by a textbook cutoff.
Start from the reaction time test hub, then read simple vs choice reaction time to understand why raw speed and correct decisions are not the same metric.
Sources & context
For simple reaction-time background and latency factors, see this PMC review of factors influencing simple reaction time. PulsarMS deliberately uses randomized timing rather than catch trials in both modes — a catch trial adds a go/no-go decision to a pure speed measure. The physical-floor screen (~50 ms visual / ~40 ms audio), the behavioral verification of the exceptional band, and the server-side re-scoring referenced here are documented in how we measure.