Is an online reaction time test accurate?

What does the number on the screen actually include?

It includes everything from the moment the code decides to change the color to the moment it logs your click. Only part of that is you. The rest is a chain of machinery. Each link adds a few milliseconds that nobody can see, and trying harder won't remove them.

This matters because the research everyone quotes was not gathered this way. The most quoted modern figure is 231 ms, from Woods and colleagues (2015). They measured 1,469 adults on calibrated lab equipment. Their own hardware added 17.8 ms, and taking that out brings the average down to 213 ms.

A site that shows your raw browser time next to that figure is comparing two different measurements. It lets you conclude you are slow when you may not be. The good reaction time chart puts the two scales side by side.

Where do the extra milliseconds come from?

From four places. The table gives the typical size of each link. The last row is what one study measured for the whole chain, end to end: roughly 71 to 87 ms.

That measured total is bigger than the four typical values added up. The chain also waits between links, and the study caught the slow cases as well as the typical ones. The sections below the table explain each link.

The screen

Display refresh comes first. A 60 Hz screen only draws a new image every 16.7 ms. So when the code decides to turn the panel green, the panel is not green yet. It turns green at the next redraw, about 8 ms later on average and up to 16.7 ms later.

A 120 Hz or 144 Hz display cuts this by half or more. That is a real, measurable advantage, and it has nothing to do with the player. The panel then has to physically change color. A good OLED does this almost instantly. An ordinary LCD takes a few more milliseconds before the change is clear enough to react to.

The mouse

Input sampling adds the next slice. A mouse only reports itself so many times a second. Many office mice report 125 times a second, which can leave up to 8 ms between your click and the computer knowing about it. Gaming mice at 1000 Hz cut this to about 1 ms. Bluetooth adds more than a cable, and touchscreens are slower and less steady again.

The software

The software stack finishes the chain. The operating system delivers the event, the browser queues it, and JavaScript stamps the time. Each hop is small. But the browser can be busy drawing the page or cleaning up memory at exactly the wrong moment.

Because the total differs from machine to machine, this site applies no flat correction to reaction time. You see your raw browser number as measured. The figure of roughly 80 ms, the middle of that range, stays documented only as a guide for reading your score. Treat it as an estimate, because your own machine may add more or less.

What did we find while building the test?

We ran into two things you won't find in research papers. They are engineering problems, not psychology.

First, a background tab wrecks timing outright. Browsers deliberately slow timers in tabs you aren't looking at, to save battery. We ran the timed tests with a script while the tab sat in the background. Rounds that normally take about two seconds blew past a twenty-five second limit.

That is not a small bias you could correct for. It is a broken measurement, and you can't see it, because the test still produces a number. So the reaction test here stops and shows a notice the moment the tab is hidden, and the memory tests do the same. If a reaction site happily records a score while you are in another tab, we would treat its numbers with suspicion.

Second, color transitions leak into the measurement. An early version of our reaction stage had a 120 ms CSS transition on the color change, because it looked smoother. But that meant the signal faded in instead of appearing, and part of the fade sat inside every recorded time. We removed the transition entirely. If a test fades its go signal in, part of every score it records is the fade.

How much can hardware move your score?

About 20 to 30 ms between a fast setup and a slow one. That is less than the 40 ms your own tries swing from round to round.

Picture two people with identical nervous systems. One uses a 144 Hz monitor with a 1000 Hz wired mouse. The other uses a 60 Hz laptop screen with a Bluetooth mouse. The gear alone can explain 20 to 30 milliseconds between them, which is roughly the gap between an average result and a good one. It can make you feel slow or fast, but it says nothing about your nerves.

Now compare that with the noise inside one person. Woods and colleagues found that a person's own tries swing about 40 ms around their own average. That is why a single round means almost nothing, and why this site scores the median of five. It is also why, in our view, watching your median across a week tells you more than chasing a best time from one lucky click.

How should you read your own number?

Treat the exact figure as rough and the comparison with yourself as real. Keep the conditions the same: same device, same input method, same browser, tab in front, similar time of day. Under those conditions, a 15 ms improvement across several sessions probably means something. Across different devices, a 30 ms difference might mean nothing at all.

Be wary of scores that look too good. Human reaction time never goes below about 100 ms. That floor is set by how fast nerves carry signals, and no amount of effort changes it. So this test voids anything under 100 ms as physically impossible, and counts everything above that line in full, however fast. The wait is random for a related reason: guessing when the change will come doesn't pay off.

Frequently asked questions

Can I compare my score here with another site?

Only loosely, and only if you know what each site does. Sites differ on almost everything. Some subtract the hardware delay and some do not. Some score the median and some the average. They also run different numbers of rounds and treat early clicks differently. So 250 ms on a site that reports raw averages is not the same measurement as 250 ms here. The only comparison that holds up is your own history on one site.

Would a native app be more accurate?

Somewhat. A downloaded app removes the browser layer, but not the screen, the mouse or the operating system. It narrows the gap without closing it. True lab precision needs dedicated hardware: a response box instead of a mouse, and a screen whose refresh timing is known to the millisecond.