Reaction Challenge
Four reflex modes: simple tap, lights-out start, go/no-go and arrow choice, with per-input stats and personal best.
Trial 1 of 5
Challenge status: idle · 0/5
Private by design: times never leave your browser. History and bests live only in this device storage.
Session summary
—
Personal best (this mode): —
Recent sessions
No sessions yet — finish one to start your history.
Tip: Compare only within the same mode and input: touch sampling and key travel add their own milliseconds.
Play four reflex modes in a few minutes
- Pick a mode first: Simple tap, Lights start, Go/No-Go or Arrow choice. Each measures a different skill, so their times are never mixed.
- Choose 5 trials for a quick check or 10 for a steadier average, and a wait range — quick (0.8–2.5 s), standard (1–5 s) or long (2–7 s).
- Press Start session and answer only inside the arena: click, tap, or press Space/Enter. Arrow choice needs the matching arrow key or on-screen arrow.
- Answering before the signal is anticipation, not speed: it never enters the average, and Lights mode names it a jump start.
- Worked example: hits of 210, 240, 230, 250 and 220 ms average 230 ms, with a median of 230 ms and a spread of 15.8 ms — a tight spread means a steadier hand than one lucky fast tap.
- Go/No-Go adds misses and false alarms, Arrow choice adds wrong keys: every error is tallied apart and never blended into the times.
- Finish the session to compare against your personal best for that mode, stored only in this browser. There are no population percentiles here.
Reaction Challenge questions
Why is my jump start not a valid time?
Because reacting means responding to the signal, and the signal in Lights mode is the lights going out. Moving during the red sequence is guessing the end of a random hold — the trial is discarded and your average keeps only real responses.
What is the difference between a miss and a false alarm?
A miss (omission) is staying silent when GO appeared; a false alarm is answering when NO-GO appeared. Both are control errors, counted separately, and neither touches the average — which uses valid GO hits only.
Why is Arrow choice slower than Simple tap?
Choice adds a decision: see the arrow, pick the matching key, move the finger. That decision plus key travel costs real milliseconds, so compare Choice times only against Choice times, never against Simple tap.
Why do you split stats by mouse, keyboard and touch?
Each input adds its own lag — touch sampling, key travel, click mechanics — so a touch average and a mouse average are different measurements. The tool detects the input of every trial and keeps the splits apart for fair comparison.
How good is my time compared to other people?
This page cannot say: it holds no population data, only your personal best per mode. Treat the numbers as device-relative too — display lag adds milliseconds, and the clock measures the render commit, not the physical instant light leaves your screen.