What Is a Good Reaction Time? Averages, Age and How to Test It

You take an online reflex test, it says 287 ms, and a friend posts 190 ms. Are you slow? Probably not. A single reaction time number mixes your nervous system with your screen, your input device, your browser and how much you guessed. This guide explains what a realistic "good" reaction time is, what changes it, and how to measure yours so the result means something.

What reaction time actually measures

"Reaction time" is used loosely, but researchers separate several different tasks. They are not interchangeable, and comparing a number from one with a number from another is a common source of confusion.

• Simple reaction time: one stimulus, one response. You wait for a colour change and tap as soon as you see it. The TimerBattle reaction time test works this way.
• Choice reaction time: several possible stimuli, each with its own response (for example, press left for red and right for blue). Because you must identify the stimulus and pick the response, it is slower than simple reaction time.
• Timing or anticipation: the event is predictable and the goal is to act at the right moment rather than after a signal. Catching a ball, hitting a note on the beat or stopping a stopwatch at exactly 5.00 seconds all belong here.

The main TimerBattle game measures the third kind. You get a target between 2 and 6 seconds and try to stop the timer as close to it as possible. Nothing surprises you, so raw reflex speed barely matters; what counts is your internal sense of time and how consistently you press. That is why someone with an average reflex test score can be excellent at timing, and the reverse. It is worth testing both, because they tell you different things.

Typical reaction time ranges

For simple visual reaction time, healthy young adults are commonly measured somewhere around 200–250 ms in laboratory conditions. Individual results spread wider than that, and the exact average depends on the stimulus, the equipment and how the test handles early presses. A few patterns are well established:

• Auditory is usually faster than visual. Simple reactions to a sound are typically quicker than to a light, which is one reason sprint starts use a gun or beep.
• Choice reactions are slower, and get slower with more options. In 1952 William Hick showed that choice reaction time rises roughly with the logarithm of the number of equally likely alternatives, a relationship now known as Hick's law (often called the Hick–Hyman law). Two choices cost more than one, four cost more than two, but each doubling adds a similar extra amount rather than doubling the time.
• Responses faster than about 100 ms are usually not reactions. Researchers commonly treat them as anticipations, meaning you started moving before the stimulus could have been processed. If a test shows 80 ms, you most likely guessed.

So what is a "good" reaction time? On a well-built simple visual test, consistently landing near or under the low 200s is a solid result. Consistently landing in the 300s on a desktop setup usually points to something worth checking first, such as a slow display, a distracting environment or fatigue, before concluding that your reflexes are slow.

What affects your reaction time

Your number is not fixed. Several factors move it, some within a single evening.

• Age. Reaction time tends to be fastest in early adulthood and slows gradually with age, with the change becoming more noticeable later in life. Choice tasks typically show the age effect more than simple ones.
• Sleep and fatigue. Sleep deprivation reliably slows responses and, just as important, makes them inconsistent, with occasional very slow responses or lapses. This is the basis of the Psychomotor Vigilance Task used in sleep research.
• Attention and expectation. If you know roughly when the stimulus will appear, you respond faster. Good tests randomise the delay so you cannot simply count.
• Warm-up and practice. The first few trials of any session are often slower and noisier. Familiarity with the specific test also helps, which is a practice effect rather than faster nerves.
• Substances and health. Alcohol and sedating medications slow reactions. Moderate caffeine can improve alertness, especially when you are tired, but it does not turn an average result into an elite one.

Why online reaction tests disagree

Every online test measures your biology plus the latency of the system in between. The software records the moment it asked the screen to change and the moment it received your input. Everything in the chain adds time:

1. Display refresh. A 60 Hz screen draws a new frame every 16.7 ms, so a colour change can wait up to one frame before it even starts to appear. A 144 Hz or 240 Hz monitor shortens that wait. The panel's own processing and pixel response add more.
2. Input device. Mice and keyboards report at a fixed polling rate, and touchscreens sample touches at their own rate. Wireless Bluetooth devices can add noticeable delay.
3. Operating system and browser. Browsers schedule rendering and input events in their own loop. Background tabs, power-saving modes and heavy extensions can add delay and, worse, variability.

Together these commonly add tens of milliseconds, and the exact amount differs between devices. That is why your score on a gaming PC can be noticeably lower than on an older laptop, even though your brain did not change. For a deeper look at the hardware side, read our guide to input lag.

The practical lesson: online reaction times are comparable only on the same setup. Comparing your phone result with someone else's 240 Hz desktop result tells you very little about who actually reacts faster.

Reaction time test on mobile vs desktop

A reaction time test on mobile is convenient, but it behaves differently. Touchscreens need to register contact, the browser has to deliver the touch event, and many phones run at 60 Hz (though 90 Hz and 120 Hz screens are increasingly common). Tapping with a thumb is also a different movement from clicking a mouse button with an index finger that is already resting on it.

None of this makes mobile testing useless. It just means you should compare mobile results with mobile results. For stable results, turn off low-power mode, close other apps and use the same finger every time.

How to test your reaction time properly

A single trial is mostly noise. Use a simple protocol instead:

1. Pick one device and stick with it. Same screen, same browser, same input, ideally the same posture.
2. Warm up. Do three to five trials you do not count.
3. Record a set of trials. Ten to twenty is a reasonable set for a quick check.
4. Use the median, not the best. Your fastest trial often includes a lucky near-guess. The median ignores outliers in both directions and describes your typical performance.
5. Discard false starts. Anything under about 100 ms, or any press before the change, is an anticipation, not a reaction.
6. Note the spread. If your results range from 210 to 400 ms, consistency is the bigger opportunity than raw speed.
7. Repeat at different times. Testing in the morning, after work and late at night will show you how much sleep and fatigue matter for you personally.

You can run this protocol on the reaction time test, then try a few rounds of the timing game to see how your anticipation compares.

Interpreting your numbers

Treat your median as a personal baseline rather than a grade. What matters is how it moves on the same setup over weeks, and how tight your spread is. A drop of 10 to 20 ms in median after a few weeks of regular, rested testing is meaningful. A single 160 ms trial is not.

If you want to improve, the most useful levers are usually sleep, a short warm-up, a stable low-latency setup and regular practice on the specific task you care about. We cover practical routines in Reflex Training: Drills That Actually Help, and esports-specific advice in How to Improve Reaction Time for Esports.

Timing is a different number

Everything above is about simple reaction time: how long it takes you to respond to something you could not predict. TimerBattle's main game measures something else. You see a target such as 3.412 seconds, the clock runs in front of you, and you try to stop it at exactly that moment. The result is not a delay but a miss: how far from the target you stopped, early or late. The two numbers should not be compared with each other, and a good score on one does not guarantee a good score on the other.

Here is how players compare. These are the 463 players with at least ten recorded rounds; for each one we took their median miss, then ranked the players.

The numbers look similar in size to reaction times, which is exactly why they get confused. They measure different things:

• A reaction time can never be zero. It always includes the time to see the change, decide and move, so even an excellent result is around 200 ms. A timing miss can be zero, because you start the press before the moment arrives. In our data, 46 rounds out of 25,300 were stopped at exactly 0 ms.
• Reaction time has a direction; a miss has two. You cannot react too early without it being a false start. In timing, being early is just as wrong as being late, and players split almost evenly: 52% of stops were early, 48% late.
• Speed versus prediction. A reaction test rewards how fast your nervous system responds. A timing test rewards how well you predict when the clock will hit the target and how consistently you launch the press. The sensory and motor delay is still there, but you learn to start earlier to cover it.
• Practice affects them differently. Simple reaction time usually improves modestly with practice. Timing improves faster: the 34 players in our data with ten or more games cut their typical miss by about 30% between their first game and games five to ten. That figure covers a small group, so treat it as an estimate.

Device delay plays a different role, too. In a reaction test, every millisecond your screen and input add goes straight into your result. In a timing test with a visible clock, a constant delay mostly shifts you slightly late, and practice partly corrects for it; the frame-to-frame variation that cannot be learned is usually much smaller than the 114 ms typical miss. We cannot fully separate device from human error, though, and our numbers include both.

If you want to see both sides of your own performance, take the reaction time test and then play a few rounds of the timing game. The full breakdown of the timing data, including why longer targets are not harder and why short targets run late, is in What 25,300 Rounds Taught Us About Timing.

Data: 25,300 rounds by 1,843 players, Feb–Oct 2026, from TimerBattle's daily challenge and championship with the running clock visible. Results flagged by anti-cheat are excluded. Benchmarks use players with at least 10 recorded rounds (463 players). Full analysis.

FAQ

What is a good reaction time for a reflex test?

On a simple visual test with a decent setup, a median around 200–250 ms is typical for healthy young adults, and consistently reaching the low 200s or below is a strong result. Always judge the median of several trials, not your single best.

Why is my reaction time slower on my phone?

Phones often add touch-sampling and browser delay, many still refresh at 60 Hz, and tapping is a different movement from clicking. Compare phone results only with other phone results.

Is a reaction time under 100 ms possible?

Not as a genuine response to an unpredictable visual stimulus. Results that fast are almost always anticipations, where you pressed before you could have processed the change.

Does reaction time get worse with age?

On average, yes. It tends to be fastest in early adulthood and slows gradually, more so on choice tasks. Staying active, well rested and practised helps you perform closer to your own best.

Is TimerBattle a reaction time test?

The main game is a timing test: you stop a clock as close as possible to a known target, which measures your internal timing and consistency. Across 25,300 rounds the median miss is 114 ms, a different kind of number from a reaction time. For classic simple reaction time, use the separate reaction time test.