About Reaction Time Test
Free browser-based reaction time tools and guides focused on accurate timing, clear benchmarks, and results that stay on the device.
What the site offers
Reaction Time Test provides laboratory-grade reaction time benchmarks in the browser, without proprietary hardware. Accurate reaction timing once required dedicated tachistoscopes or university neurophysiology equipment that cost thousands of dollars.
The site uses modern browser capabilities: the High Resolution Time API, hardware-accelerated Canvas and DOM rendering, and Web Audio synthesis. Athletes, competitive gamers, researchers, and other users can measure neuro-motor processing speed with transparent methods and practical guides.
Timing engine and sub-millisecond precision
Accurate reaction time testing requires isolating measurement timestamps from operating system clock drift and browser garbage collection. The timing engine uses three web standards to keep measurement precise:
1. DOM High Resolution Time API (performance.now()): Unlike Date.now(), which can shift with system clock updates (NTP) and often resolves only to 1ms, performance.now() provides a strictly monotonic timestamp with sub-millisecond precision.
2. Hardware render synchronization: Stimulus delivery uses window.requestAnimationFrame() so visual changes align with the display vertical blanking interval (VBLANK). That reduces tear-related stimulus delay.
3. Web Audio oscillator generation: Auditory tests synthesize tones through the Web Audio API AudioContext, so sound starts within about 1 to 3ms of the trigger and avoids compressed file decode delay.
Biological speed versus hardware latency
A digital reaction score is not biology alone. It is the sum of biological latency and peripheral hardware delay.
Biological latency includes retinal phototransduction (~35ms), optic radiation to visual cortex (~45ms), parietal and premotor decision integration (~60ms), corticospinal axonal conduction (~30ms), and neuromuscular junction actuation (~25ms). That sets a practical floor near 140 to 150ms for visual stimuli.
Hardware latency includes display frame interval (16.67ms at 60Hz versus 4.16ms at 240Hz), pixel response time (1 to 10ms GtG), USB polling (1ms at 1000Hz versus 8ms at 125Hz), and operating system event queuing (2 to 6ms). Each test page discloses these offsets so scores can be read against a biological baseline.
Research foundations
Each benchmark follows established experimental psychology and neurophysiology work:
• Franciscus Donders (1868): Mental chronometry and the subtraction method, showing that choice reaction time equals simple reaction time plus decision discrimination time.
• William Edmund Hick (1952) and Ray Hyman (1953): Hick's Law, where cognitive latency rises as a logarithmic function of stimulus-response alternatives: RT = a + b · log2(n).
• J. Ridley Stroop (1935): Semantic interference in color-word naming, tied to executive conflict resolution in the anterior cingulate cortex.
• Herbert Simon (1969): Spatial stimulus-response compatibility (the Simon Effect), where irrelevant location cues interfere with motor selection.
• George Sperling (1960): Iconic sensory memory and its rapid millisecond-scale decay.
• Anne Treisman and Garry Gelade (1980): Feature Integration Theory, separating preattentive feature pop-out from serial visual search.
• Harold Pashler (1994): The psychological refractory period (PRP) and the central cognitive bottleneck in dual-task performance.
Client-side processing and privacy
Reaction scores are personal performance data. The site keeps that data local by design.
Timing loops, trial calculations, consistency scores, and history charts run in the browser with Alpine.js and native JavaScript.
Individual reaction times, IP-linked performance metrics, and test scores are not stored or sent to remote tracking servers. Export files (JSON or CSV) are built on the device and saved to local storage only when the user chooses to export.