Is 200 ms a good reaction time?

Against commonly cited ranges, yes — figures of 200–300 ms circulate as the typical adult range, though usually without a stated sample size. Against people who actually take reaction tests it is closer to the sharp end. This page shows how many of our own submissions 200 ms beats, with the sample size stated.

Is 250 ms a good reaction time?

It sits inside the range most sources call typical. Whether that counts as good depends on what you need it for — for driving it is fine, for competitive gaming it is on the slow side. Where it lands among our submissions is shown on this page, not asserted from memory.

Is 150 ms reaction time possible?

On a simple visual test, sustained averages near 150 ms are rare and sit at the edge of what is usually reported for elite players. Single trials below that often involve anticipation — guessing the timing rather than reacting. A five-round average is much harder to fake, which is why our test uses one.

Why is my reaction time different on every site?

Because you are not just measuring yourself. Display refresh rate, input device, browser, and how each site defines the moment of the stimulus all add or subtract tens of milliseconds. Compare runs on the same site, same device — cross-site comparisons mostly measure the sites.

What Is a Good Reaction Time?

Take a reaction test and you get a number — 193 ms, 227 ms, 254 ms — and the obvious next question: is that good? The usual answer is a range: 200–300 ms for a typical adult, under 200 ms fast, elite gamers somewhere near 150. Those figures circulate everywhere, and almost always without a stated sample size — you cannot check how many people, measured how, are behind them.

We cannot fix that for the whole internet, but we can do the opposite thing on this page: show you where your number falls among the runs actually submitted to our reaction time test, with the sample size printed next to the answer.

Where 150, 200, and 250 ms fall in our data

These are the values people actually search for, so here is what our own submissions say — recomputed from the live dataset when this page loads, not written in at build time.

Against the times actually submitted to this test (15 submissions, 2026-07-29 ~ 2026-09-05):

150 ms is faster than 15 of the 15 submissions.
200 ms is faster than 15 of the 15 submissions.
250 ms is faster than 10 of the 15 submissions.

These are counts, not percentages, because the sample is small enough that a percentage would imply more precision than we have.

Two honest caveats. First, people who seek out a reaction test are not a random slice of humanity — our sample skews toward people who care about being fast, so beating half of it means more than beating half of a general population would. Second, the full spread, sample size and all, lives on the reaction time distribution page and updates as runs come in.

"Good" depends on who you compare against

The same 230 ms is a different answer to three different questions:

Against the general population — comfortably inside the commonly cited typical range. Nothing about it should worry you.
Against people who take reaction tests — around the middle. The injected figures above are this comparison.
Against competitive players — slow. Reported figures for esports professionals cluster well under 200 ms; we have collected what is publicly claimed, and what those claims are worth, in esports pro reaction times.

So a useful reading of your score starts with what you need it for. Driving safety margins are built around ordinary human speeds — we walk through the arithmetic in reaction time and stopping distance. Competitive play is the one arena where tens of milliseconds are worth chasing.

Your number is partly your equipment

Before comparing yourself to anything, know that a browser test measures a chain: photons leave the screen, your visual system detects the change, your motor system fires, your input device reports the click, the browser timestamps it. Only the middle of that chain is you.

A 60 Hz display adds about 8 ms of average waiting before the stimulus even appears — roughly 5 ms more than a 144 Hz display; input devices and browser scheduling add more. That is why the same person tests measurably slower on a laptop trackpad than on a gaming setup, and why cross-device comparisons mislead — we measured the effect in refresh rate, input lag, and test scores.

It also means the honest use of any browser number is relative: your trend on one device, or your place in one site's distribution — not your absolute neural speed.

How to get a number worth trusting

If you want your result to mean something, spend two extra minutes:

Warm up first. Discard your first two or three runs — early attempts routinely run tens of milliseconds slow while the task is still novel.
Use a multi-round average. Single trials swing wildly and reward lucky guesses. Our test averages five rounds, and a false start never counts — so the number is not quietly rewarding anticipation.
Fix your setup. Same device, same input, screen not in a power-saving mode. If you switch from mouse to trackpad, treat it as a new baseline.
Test at a consistent time of day. Fatigue and time of day shift reaction speed enough to swamp week-to-week training gains — what actually moves the number long-term is covered in how to improve your reaction time.

What this number is not

A simple visual reaction test measures one narrow thing: how fast you respond to a single expected signal. It is not reflex (which happens in the spinal cord and is an order of magnitude faster), and it is not the choice-under-pressure speed that games and driving actually demand — the distinction, and why it matters, is in reaction time vs reflex. Age moves the baseline too, in a pattern that is more interesting than "younger is faster" — see average reaction time by age.

How our test defines the stimulus moment, what counts as a false start, and what we store are documented in the methodology.