QUICK ANSWER
HOW DEVICE LATENCY CHANGES YOUR REACTION TIME
Yes, monitor refresh rate can affect a reaction-time score—but it is only one link in the chain.
An online score includes your response plus the browser, display, operating system, and input device. A faster setup may report a lower number even when the person reacts the same way.
DEVICE LATENCY REACTION TIME TEST
A browser score measures an end-to-end journey
The timer starts in software and stops when the browser receives your input event. Between those moments, several stages can add delay or variation.
- 01BROWSER SCHEDULES CUEMain-thread and frame timing
- 02DISPLAY RECEIVES FRAMEGraphics and display processing
- 03PIXELS BECOME VISIBLERefresh scanout and pixel transition
- 04YOU DETECT AND RESPONDPerception, decision, and movement
- 05DEVICE REPORTS INPUTMouse, keyboard, or touch path
- 06BROWSER LOGS EVENTEvent delivery and timestamp
WHAT CAN MOVE THE NUMBER
Each link changes timing in a different way
| PART OF THE CHAIN | HOW IT CAN AFFECT THE SCORE | WHAT TO KEEP FIXED |
|---|---|---|
| Refresh rate | Changes how often a new visual frame can begin. | The same monitor and refresh-rate setting. |
| Display processing and scanout | Adds processing time; different screen positions can illuminate at different moments during a scan. | The same display, mode, cable path, and target position. |
| Mouse, keyboard, or touch | Switches, polling, firmware, wireless transport, and OS event handling can differ. | One device and one response action. |
| Browser and workload | Frame scheduling and event delivery can shift when the main thread or system is busy. | The same browser, tab state, power mode, and background workload. |
| Audio route | Buffering, codecs, and wireless transport delay when a sound cue becomes audible. | The same output route; prefer built-in or wired audio for comparisons. |
DOES MONITOR REFRESH RATE AFFECT REACTION TIME?
Higher refresh rate shortens the frame interval
At 60 Hz, one refresh interval is about 16.7 ms. At 120 Hz it is about 8.3 ms, and at 240 Hz about 4.2 ms. A cue that just misses a refresh may wait for the next one, so shorter intervals can reduce that waiting window.
That does not mean changing from 60 Hz to 120 Hz automatically removes exactly 8.3 ms from every result. Browser scheduling, rendering, synchronization, display processing, and pixel response remain part of the path.
DISPLAY SCANOUT
A frame does not always appear everywhere at once
Many displays update in a scan pattern. A target near the bottom can become visible later than one near the top during the same refresh. Display electronics and pixel transitions add their own behavior too, which is why refresh rate alone cannot tell you total monitor latency.
MOUSE VS TOUCHSCREEN REACTION TIME
Changing the response changes the measurement
A mouse click, keyboard press, and screen tap are different movements recorded through different hardware and event paths. Their scores should not be treated as interchangeable.
Mouse
Button switch, device firmware, polling or wireless reports, USB scheduling, and the operating system all sit before the browser event. Keep the same mouse and button.
Keyboard
Switch travel, scan matrix, debounce, polling, connection, and event handling vary by board. Use the same key and press style across runs.
Touchscreen
The touch sensor, sampling, gesture recognition, and browser event path differ from a physical switch. The finger also begins and ends in a different posture.
Hardware-timed web research has found that response-time overestimation varies across devices and browsers, including keyboard and touchscreen setups. This supports comparing relative changes on one setup instead of ranking people by raw results collected on different hardware.
BROWSER SCHEDULING
The software clock is not the screen
A browser can record when code requested a cue and when it received an input event, but those timestamps do not directly measure the physical onset of light or sound.
Animation frames are scheduled around rendering opportunities. Busy tabs, power saving, thermal limits, and background work can add missed or delayed frames and alter event delivery.
BLUETOOTH INPUT AND AUDIO
Wireless adds another variable path
Wireless mice and keyboards can add radio, polling, firmware, and power-management behavior. Performance differs by device and connection mode, so “Bluetooth” is not one fixed delay.
For sound tests, Bluetooth audio also uses encoding, transport, decoding, and buffering. Keep the route unchanged, or use built-in or wired output when comparing sound and visual scores.
Auditory vs visual reaction timeSAME-DEVICE CALIBRATION
Make your comparisons useful without fake precision
You cannot calibrate away exact hardware latency with browser software alone. You can make repeated results more comparable by controlling the setup.
- 01
Choose one setup
Use the same computer or phone, display, browser, input device, key or button, and audio route.
- 02
Lock the settings
Keep refresh rate, display mode, power mode, browser zoom, window size, and target position unchanged.
- 03
Reduce interruptions
Close heavy background work, keep the tab visible, silence notifications, and avoid testing during updates or thermal throttling.
- 04
Warm up, then run blocks
Discard a few practice trials. Record several equal-size blocks rather than choosing one unusually fast response.
- 05
Compare distributions
Use the median or average, note false starts, and look at consistency. A repeated within-device change is more informative than a tiny one-off difference.
- 06
Label the setup
When sharing a score, include the device, refresh rate, browser, and input method. Do not compare it directly with an unknown setup.
Track your own repeated performance on the same setup. Treat cross-device leaderboards and mouse-versus-touch comparisons as entertainment unless the hardware path is measured and standardized.
QUICK QUESTIONS
Device latency and reaction time FAQ
Does monitor refresh rate affect reaction time?
It can affect the measured score because a visual cue normally waits for a display update. Higher refresh rates shorten the interval between update opportunities, but total latency also depends on the browser, graphics path, monitor processing, scanout, and pixel response.
Can a reaction time test detect my device latency?
Not exactly. A web test sees software timestamps, not the physical light onset and switch movement. Measuring end-to-end hardware latency requires external sensors or specialized equipment.
Is a mouse faster than a touchscreen for reaction tests?
There is no universal answer. The movement and hardware pipeline differ, and results depend on the specific mouse, touch device, browser, posture, and task. Compare each method only under a fixed setup and do not treat the raw scores as equivalent.
Should I subtract one frame from my reaction time?
No. A cue may wait anywhere within a refresh interval, and other delays vary too. Subtracting a fixed frame duration creates false precision unless the full system has been measured externally.
Why did my score change on another browser?
Browsers, operating systems, and devices can differ in frame scheduling and input-event timing. Background load, tab visibility, and power state also matter. Use one browser for progress tracking.
SOURCES
Research and technical references
- Pronk et al. (2020), touchscreen and keyboard timing accuracyExternal hardware measurements of visual presentation and response recording across commodity devices and browsers.
- Bridges et al. (2020), realistic precision and accuracy of online experimentsHardware tests of visual display timing and keyboard-response logging across online platforms, browsers, and devices.
- Saunders & Woods (2014), direct measurement of system latencyHigh-speed-camera measurements and an explanation of refresh waiting, vertical scanout, rendering, and display delay.
- WHATWG HTML Standard, animation framesThe browser specification for scheduling animation-frame callbacks around rendering updates.
- W3C Event Timing specificationThe web performance model for timestamps and delays in user interaction event processing.
- Bluetooth SIG, Introducing Bluetooth LE AudioOfficial technical material on codec frame size, buffering, retransmission, and latency in Bluetooth audio.