Reaction Lab
Testing methodology

HOW ACCURATE ARE ONLINE REACTION TESTS?

Browser reaction tests can be excellent for consistent personal comparisons, but consumer hardware is not a laboratory timing instrument. Knowing where latency comes from helps you interpret the number.

What an online score actually measures

Your result is not only the time your nervous system took to see and respond. It includes the time needed for the stimulus to reach the screen and the time needed for your input to travel back through the device, operating system and browser.

Main sources of delay

What research says

Calibrated reaction-time research has shown that hardware/software delays can meaningfully inflate measured reaction times. Woods et al. measured an 11 ms display delay on one LCD setup and corrected their reaction results for hardware. PC-PVT researchers similarly noted that general-purpose computers can introduce timing uncertainty unless the system is characterised carefully.

This does not make browser tests useless. It means the strongest use case is relative measurement: same device, same browser, same test, repeated over time.

How Reaction Lab improves consistency

Reaction Lab timestamps responses in the browser with performance.now(), uses random delays so the signal is harder to predict, and stores personal bests locally where appropriate. It still cannot remove your device's physical display/input latency.

Research sources

  1. Woods et al. — Factors influencing simple reaction-time latency.
  2. PC-PVT — Computer timing accuracy for psychomotor vigilance testing.
  3. Garaizar et al. — Software timing errors in visual-stimulus presentation.
RUN A CONSISTENT TESTTry the relevant Reaction Lab test and compare your own results on the same device.
PLAY →

More Reaction Lab guides

Continue with: Input lag vs reaction time · Mobile vs desktop · How many reaction trials? · Why scores vary.

How to test reaction time more reliably at home

Use the same device, browser, display and input method when comparing sessions. Run several attempts, ignore obvious false starts, and use an average or median rather than treating the fastest attempt as your “true” reaction time. Five to ten clean trials is a practical range for a casual browser benchmark.

Browser tests are useful for repeatable personal comparisons, but the number includes system latency as well as human response time. That is why a mouse result on a high-refresh desktop should not be treated as directly interchangeable with a touchscreen result on a phone.

Why repeated trials matter

Reaction time naturally varies from trial to trial. Attention fluctuates, the timing of a display refresh can vary, and anticipation can pull some responses earlier. Repeating the task helps separate a stable pattern from a lucky or unlucky single attempt. If the first few tries are noticeably slower, treat them as warm-up rather than hiding them.