Free reflex test

Reaction Time Tester

Wait for the screen to turn green, then click or tap as fast as you can. Track your latest, best, average, and consistency across a short round.

  • Millisecond timing
  • Mouse or touch
  • Best score saved
  • Attempt history
  • Copyable result

Reflex test

Wait for green, then click

False starts do not count. Your best score is saved in this browser only.

Reflex result

Current round

Waiting for first attempt 0 ms
Latest reaction
0 ms
Round best
0 ms
Round average
0 ms
Browser best
No best yet
Attempts
0 / 5
Consistency
Waiting
Status
Ready

Recent attempts

  1. No attempts yet.

How the reaction time test works

Click or tap the test area to begin. The page waits for a random delay, turns green, and then measures how many milliseconds pass before your next click or tap. A lower number means a faster reaction in that attempt.

What is a good reaction time?

Reaction time varies by device, input method, attention, sleep, and browser latency. Many casual browser tests land somewhere around the low-to-mid hundreds of milliseconds, but the fairest comparison is against your own attempts using the same device.

How to compare scores fairly

Use the same mouse, touchscreen, browser, and round length when comparing scores. Trackpad taps, phone screens, gaming mice, and high-refresh displays can all feel different. This tester is meant for quick fun and consistency practice, not laboratory measurement.

Why false starts matter

If you click before the green signal, the attempt is marked as a false start and does not count. That keeps the game honest: the goal is to react to the signal, not guess when it will appear.

Tips for better attempts

Relax your hand, keep your eyes on the test area, and avoid tensing up during the waiting phase. Short rounds are usually better than long sessions because fatigue and anticipation can skew the result.

Why device latency changes the score

A browser reaction test includes more than your nervous system. Mouse switches, touchscreen sampling, display refresh rate, browser scheduling, and the operating system can all add tiny delays. That is why a phone tap, laptop trackpad, office mouse, and gaming mouse may produce different numbers even when the same person is taking the test.

The fairest way to use this page is to compare your own rounds on the same device. If you switch devices, treat the new score as a new baseline instead of a direct improvement or decline.

Choosing 3, 5, or 10 tries

Three tries is useful for a quick warm-up. Five tries gives a better snapshot without taking long. Ten tries smooths out one lucky click or one distracted attempt, which makes the average more useful if you are comparing sessions.

If your goal is consistency, watch the average and recent attempts instead of only chasing the best score. One very fast click can happen by chance, but several similar attempts usually tell you more.

Reaction time FAQ

What does this test measure?

It measures the delay between the green signal appearing and your next click or tap. It is a simple reflex game, not a clinical or laboratory measurement.

Why do scores change between devices?

Input hardware, display timing, browser behavior, and device latency can all affect the result. Compare scores on the same device when possible.

How many attempts should I use?

Five attempts is a good quick baseline. Use ten attempts for a smoother average and three attempts when you only want a fast warm-up round.

Methodology, Formula & Official Standards

This Visual Reaction Time & Human Visuomotor Latency resource implements the official methodology and technical standards defined by W3C High Resolution Time Level 2 (performance.now()) sub-millisecond timing, Hick-Hyman Law of simple reaction time, and peer-reviewed human psychomotor latency benchmarks. Core calculation rule: Measured Latency (ms) = Timestamp_PointerDown - Timestamp_VisualFramePaint; Total Latency = Retinal Phototransduction (~20–40ms) + Visual Cortex V1 Processing (~50–70ms) + Motor Cortex & Finger Actuation (~70–90ms) + Display/USB Input Lag (~10–35ms). Processing runs 100% client-side in your browser so you can inspect the exact mathematical assumptions and benchmark tiers in real time.

Step-by-Step Worked Example

Worked Example: Across 5 consecutive visual stimulus trials, a user records 212 ms, 198 ms, 224 ms, 205 ms, and 201 ms. The arithmetic mean is (212 + 198 + 224 + 205 + 201) / 5 = 208.0 ms with a 26 ms spread—placing them in the upper 25% of desktop users on a 144Hz monitor.

Reference Benchmark & Comparison Table: Visual Reaction Time & Human Visuomotor Latency Reference Benchmark & Comparison Table

Benchmark Tier / ModePrimary Metric / InputSecondary ParameterExpected Output / ScorePractical Application
140 – 175 ms (Elite / Esports Pro)144Hz–360Hz Monitor + 1000Hz Wired Mouse< 10 ms System LagTop 2% human simple visual reflexRequires pre-tensed finger & low-latency display
180 – 215 ms (Fast Desktop Gamer)120Hz–144Hz Display + Gaming Mouse12 – 20 ms System LagAbove-average adult visuomotor speedTypical score for regular FPS/rhythm players
215 – 250 ms (Average Adult Baseline)60Hz Standard Monitor / Laptop20 – 35 ms System LagMedian human browser benchmark (~230 ms)Reflects 190ms biological + 35ms display lag
255 – 310 ms (Mobile Capacitive Touch)Smartphone / Tablet Touch Digitizer40 – 65 ms Touch PipelineNormal on mobile due to touch scan delayRetest on wired desktop mouse for true baseline
< 100 ms (Anticipation / False Start)Pre-stimulus click before V1 processingPhysiologically impossible visual reflexIAAF sprint rules flag <100ms as false startWait for green color transition before clicking

Frequently Asked Questions

What official standard or formula is used for Visual Reaction Time & Human Visuomotor Latency?

It follows W3C High Resolution Time Level 2 (performance.now()) sub-millisecond timing, Hick-Hyman Law of simple reaction time, and peer-reviewed human psychomotor latency benchmarks, applying the rule Measured Latency (ms) = Timestamp_PointerDown - Timestamp_VisualFramePaint; Total Latency = Retinal Phototransduction (~20–40ms) + Visual Cortex V1 Processing (~50–70ms) + Motor Cortex & Finger Actuation (~70–90ms) + Display/USB Input Lag (~10–35ms) with deterministic client-side precision.

How do I interpret my result using the Reference Benchmark Table?

Locate your output tier in the 5-row comparison table above and compare it with the step-by-step Worked Example to see how small input adjustments change the outcome.

Is any of my input text, files, or performance data uploaded to a server?

No. Every calculation, hash digest, and timer runs locally inside your browser tab with zero server-side data storage.

Can I use these results on both mobile and desktop devices?

Yes. The tool uses responsive HTML5 and high-resolution browser APIs across desktop, tablet, and smartphone browsers.

Editorial Methodology & Disclaimer

Editorial Methodology & Disclaimer: All calculator outputs and reference tables on Utility Stack are educational planning estimates based on published mathematical standards. They are not professional financial, legal, tax, or medical advice.