How Your Monitor, Mouse and Browser Change Your Reaction Time

Your score is your reaction plus your hardware

A reaction time score feels like a measurement of you. In a lab, with purpose-built equipment, it nearly is. At home it is a measurement of you plus your setup, and the setup is never free. Before the test can show you a signal, the computer has to draw a new frame, hand it to the display, wait for the display to refresh, and let the panel's pixels physically change. After you react, the mouse has to detect the press, wait for its next report to the computer, and the operating system and the browser have to deliver that click to the page.

None of those steps is slow on its own. Most cost a few milliseconds, and some cost less than one. But they stack, and every one of them is added to your score. A 2 ms saving here and a 5 ms saving there can look trivial, yet the gap between a strong setup and a weak one is often 20 to 40 ms, which on most score ladders is the difference between one grade and the next.

Researchers who study online experiments know this well. Timing studies that checked browser-based tests with external light sensors and robotic button pressers found that recorded reaction times run consistently longer than the true response, and that the extra amount depends on the browser, the operating system and the hardware. The practical conclusion they reach is the one this guide reaches too: treat the delay as a fixed overhead per device, keep the device the same, and compare like with like.

How a browser test actually times you

A well-built browser test does two things to keep its own error small. It records the start time at the frame the signal is actually painted, not at the moment the code decides to change colour, and it uses performance.now(), a high-resolution clock accurate to well under a millisecond. Our methodology explains how ReactionBench does both. That removes the test's own sloppiness, but it cannot remove the hardware on either side of the clock.

On the output side, the frame the browser paints still has to travel through the graphics pipeline and the monitor before light reaches your eye. On the input side, your click still has to travel through the mouse, the USB stack, the operating system and the browser's event queue before the page sees it. Both delays are invisible to the page, so both are silently added to whatever your nervous system did.

This is why two honest tests can disagree. Neither is wrong; they are measuring different chains. It is also why a single score on an unfamiliar device tells you less than you might think, and why the most useful thing you can do is keep your chain fixed while you track your own numbers over time.

What your monitor adds

The display is usually the largest share of hardware delay, and it is made of three separate parts. Refresh interval: a new image can only appear at the next refresh, so on average you wait half a frame. Processing: the monitor's electronics scale, sharpen and sometimes smooth the image before showing it. Pixel response: the panel's pixels take a moment to physically change from one colour to another.

Refresh rate is the delay most people know about, and the arithmetic is simple. A signal arrives at a random point inside the refresh interval, so the average wait is half of one frame, or about 500 divided by the refresh rate in Hz. That is roughly 8 ms at 60 Hz, 3.5 ms at 144 Hz and under 2 ms at 240 Hz or above. Our pro gamer article walks through the same table from a competitive angle.

Processing lag is where the big differences hide. Gaming monitors usually process a frame in a few milliseconds. Office monitors and laptop panels are often slower but rarely dramatic. Televisions are the worst offenders: with motion smoothing, noise reduction and other picture enhancements switched on, many add 50 to 100 ms or more, which is enough to drop a score by two whole grades. Switching the TV to its game mode, or to a PC input mode, usually brings that under 20 ms.

Pixel response matters least for reaction tests. A colour change from red to green on a modern LCD completes in a few milliseconds, and OLED panels switch in well under one. It is worth knowing about, but it is rarely the reason a score looks slow.

What your mouse and keyboard add

A mouse does not tell the computer about a click the instant it happens. It reports at a fixed polling rate. A basic office mouse polls at 125 Hz, once every 8 ms, so a click waits about 4 ms on average before the computer even hears about it. A gaming mouse at 1000 Hz cuts that to about 0.5 ms. Rates of 4000 or 8000 Hz shave off fractions of a millisecond that no human can feel.

The click itself has a cost too. A mechanical switch bounces electrically for a moment when pressed, so the firmware waits a short debounce period to be sure the press is real. Depending on the model and its settings, that can add anywhere from about 1 ms to 10 ms or so. Optical switches, found on some gaming mice, detect the press with a light beam and skip most of that wait.

Keyboards work the same way, often more slowly. A keyboard scans its key matrix, debounces the press and then reports at its own polling rate. Gaming keyboards keep this to a few milliseconds, while some office and laptop keyboards take 20 ms or more. That is worth remembering if you compare the Spacebar Reaction Time Test with a mouse-click test: part of any gap between them can be the keyboard, not your hand.

Wireless is no longer the problem it was. Modern gaming mice with a 2.4 GHz USB receiver measure close to wired ones. Bluetooth mice and keyboards are a different story: they often report less frequently and less consistently, and can add several milliseconds or more. For scores you want to compare, use a wired or 2.4 GHz connection.

Phones, tablets and the 20–50 ms touchscreen tax

A touchscreen has more work to do than a mouse button. It has to scan the whole panel, filter out palms and accidental contact, decide where your finger actually landed and only then pass a tap to the browser. That pipeline typically adds 20 to 50 ms compared with a desktop and mouse, and the phone's own display latency comes on top of that.

Research on touch interfaces shows people can notice delays far smaller than what most devices deliver, which tells you how much room there is between a typical touchscreen and an ideal one. Newer phones with high touch-sampling rates and 120 Hz displays narrow the gap, but they rarely close it.

This is the main reason mobile scores run slower, and the reason our methodology keeps desktop and mobile results apart. A slower phone score does not mean slower reflexes. It means a longer chain. Compare phone scores with phone scores, and desktop scores with desktop scores.

The browser, the operating system and the jitter problem

Between the hardware layers sits software. The browser composites the page, the operating system's window manager composites the browser, and vertical sync lines the result up with the display. Each of these can hold a frame for a moment. In practice the software layer usually adds around one frame of delay, and on a busy machine it can add more.

The average matters, but the variability matters as much. A setup that is sometimes 10 ms slow and sometimes 30 ms slow does not just push your scores up; it makes them noisier, so a genuine improvement is harder to see. Timing studies of online experiments found exactly this kind of device-to-device and trial-to-trial spread.

Several everyday things make the software layer slower and less consistent: many open tabs, video playing in the background, battery-saver or low-power modes, an overheating laptop, browser extensions that hook into every page, and remote-desktop or screen-sharing sessions. None of them change your brain. All of them can change your number.

Why online scores are slower than lab numbers

Textbook figures for simple visual reaction time usually sit around 200 to 250 ms. Large online tests tend to report averages nearer 270 ms. Part of that gap is the people taking the test: online samples include every age, every level of alertness and plenty of first attempts. But a large part is hardware. Lab equipment is designed to keep delay near zero, while a typical home setup adds 10 to 40 ms and a phone adds more.

This is worth keeping in mind when you read any benchmark. Our average reaction time article and score guide are written for real devices, not lab rigs, so they already allow for a normal amount of hardware delay. If your setup is unusually slow, expect to land a little lower on those ladders than your reflexes deserve; if it is unusually fast, a little higher.

Sound tests have their own trap

Hearing is normally faster than sight, by about 30 to 50 ms in simple reaction tasks, as our visual vs auditory article explains. Audio hardware can wipe that out. Bluetooth headphones and speakers often add 100 to 200 ms or more while they buffer sound, which is far larger than any display delay.

If your result on the Audio Reaction Time Test is slower than your visual score, the headphones are the first suspect. Switch to wired headphones or the device's built-in speakers and retest before drawing any conclusion about your ears.

Upgrades ranked by what they actually save

Not every upgrade is worth the money if your goal is a fair, comparable score. The biggest wins are usually free settings changes, and the most expensive hardware buys back the fewest milliseconds. The table assumes you start from a typical laptop or office setup.

Notice the shape of it. Fixing a TV's picture mode or moving from a phone to a desktop can recover more time than every premium upgrade put together. Going from 60 Hz to 144 Hz is a real and noticeable gain. Beyond that, each step costs more and saves less, and quickly falls below the natural variation between your own rounds.

How to get a score you can trust

You don't need expensive gear to get a meaningful score. You need the same gear every time. A fixed chain turns hardware delay into a constant, and a constant cancels out when you compare today with last week.

Before you test: use one device, one screen and one mouse or keyboard, and stick with them. Plug the laptop in and turn off battery saver. Close video and heavy tabs. If you use a TV, switch it to game mode. Use wired audio for sound tests. Sit at a normal distance and test when you are reasonably alert.

While you test: take several rounds and look at your median, not your single best, because one lucky round says more about anticipation than about speed. Start with the Classic Reaction Time Test as your baseline, add the Aim Reaction Test if you play shooters, and log your results.

After an upgrade: retest straight away on the new hardware and treat the new number as a fresh baseline. If your score drops by 5 ms the day you plug in a 144 Hz monitor, that is the monitor, not a breakthrough. The real progress is whatever happens after that.