Start without guessing.
Press Start test and wait through the randomized pause. The field stays dark while the signal is prepared. Clicking before the change counts as an early click, so anticipation cannot masquerade as reaction speed.
Browser reaction benchmark
Run five randomized visual-signal rounds, then inspect your median, P95, consistency and early clicks. This online reaction time test is designed for repeatable self-comparisons, not a leaderboard or an official performance rating.
01 / reaction time test
Visual response drill
Wait for the field to turn chartreuse, then click once. Early clicks remain visible as errors.
Click start, then click the stage as soon as it turns chartreuse.
02 / results
Use the median as the main comparison point. P95 shows the slow tail, consistency shows spread, and accuracy makes early clicks visible.
Finish five rounds above to populate this panel with a real browser measurement.
Trial trace
Exact values are also listed in the table below.
Read the result
A completed run will explain what this metric says and what it does not say.
| Date | Median | Accuracy | P95 |
|---|
03 / how it works
A useful reaction speed test is a controlled comparison. Keep your device, browser and posture stable, then judge the run as a set rather than chasing one unusually fast click.
Press Start test and wait through the randomized pause. The field stays dark while the signal is prepared. Clicking before the change counts as an early click, so anticipation cannot masquerade as reaction speed.
When the field turns chartreuse, click anywhere in the work area. The timer begins at the visual change and ends at your pointer response. Five rounds create a small personal sample without turning the test into a fatigue exercise.
After the fifth round, use median, P95, consistency and accuracy together. A fast median with more early clicks is a different result from a slightly slower run with a tighter spread.
A clean comparison session
Short sessions are easier to repeat. If you are checking a monitor, browser or FPS warm-up change, change one variable at a time and keep a note of the setup.
Use the same display, browser and pointer.
Close tabs or apps that may steal focus.
Run one warm-up before recording a comparison.
Compare median, P95, spread and early clicks.
Example. If your median falls from 250 ms to 225 ms but P95 rises and accuracy drops, you may be rushing or anticipating. If the median and P95 both move down while accuracy stays at 100%, the change is a cleaner personal baseline. Neither result is an official rank or a guarantee of in-game performance.
04 / measurement
This tool measures a narrow visual-to-click task. It is useful for a repeatable baseline, but it should not be treated as a full reflex, latency or skill assessment.
The median is the middle valid round after sorting. It is less sensitive than an average to one slow interruption, so it is a practical number for comparing your own sessions.
P95 shows how slow the upper end of the run became. A wide gap between median and P95 can point to hesitation, focus changes, fatigue or an inconsistent setup.
Accuracy reflects valid responses out of five rounds. Early clicks remain an explicit error signal so a low number produced by guessing is easier to spot.
Scope note. A browser reaction time test includes display refresh, browser scheduling, operating-system load, pointer hardware and human anticipation. It is not a calibrated mouse-latency test, monitor-latency test, medical measurement, anti-cheat diagnostic or population leaderboard.
05 / interpretation
The same person can produce different scores across a day. Treat changes as clues about the test conditions and your current state, not as a permanent label.
Refresh behavior, browser load, pointer hardware and the distance between hand and button can change a browser measurement. Keep the same setup when the goal is comparison, and do not compare two devices as if they were one instrument.
Familiarity, attention, sleep and anticipation all affect a response. A short warm-up may make the task feel easier, while repeated attempts can also teach you to predict the timing. That is why randomized pauses and error counts matter.
Use this page for a general online reaction time test or a simple FPS reaction baseline. For CS2-specific target acquisition, use the CS2 aim trainer; for the full reaction, flick and tracking lab, return to the CS2 reaction test.
Your recent results are stored locally when the browser allows local storage. No account is needed. Clearing site data, using a private window or blocking storage can remove or prevent the local history. Read the privacy policy for advertising and data disclosures, and the terms and disclaimer for use boundaries.
06 / faq
There is no universal cutoff for an online reaction time test. Use the same browser and device, compare the median across several short sessions, and treat the result as a personal baseline rather than an official ranking or a promise about game performance.
The test waits a randomized interval, changes the field to a response signal, and measures the time between that change and your click. Five rounds are summarized with median, P95, consistency, accuracy and early clicks.
They are useful for comparing your own setup, but a browser result also includes display, operating-system, browser and input-path effects. It is not a calibrated mouse or monitor latency instrument, so do not treat a single number as a laboratory measurement.
Repeating a test can improve familiarity and anticipation, so a lower score is not automatically a permanent skill improvement. Use short, consistent sessions, keep the setup stable and compare the full trace rather than the fastest click.
Yes. It can provide a simple visual-to-click baseline for FPS practice, including a CS2 warm-up comparison. It does not predict an in-game rank or measure crosshair placement, movement, recoil control, peeking, aim transfer or network latency.
Displays, browser scheduling, operating-system load, pointer hardware and input paths differ between devices. Compare results only when the main setup is stable, and record any hardware or browser change beside the run.
One warm-up followed by two recorded sessions is a reasonable starting protocol when comparing a change. Constant retesting adds fatigue and anticipation, so leave enough time between comparisons to keep the result meaningful.