Mouse Input Lag Test: Check Your Click Response Time

What causes mouse input lag

"Input lag" isn't one single delay, it's the sum of several stages that happen in sequence between your finger pressing a button and something happening on screen:

• Switch and debounce time: the physical microswitch under the button has to actuate, and the mouse's firmware waits a short window (debounce time) to make sure it's reading a clean single press rather than the switch contacts bouncing.
• Firmware processing: the mouse's internal microcontroller processes that signal before sending it onward.
• Transmission: the signal travels over USB, or for wireless mice, over a 2.4GHz receiver or Bluetooth connection, each with its own small delay.
• Polling rate: how often the mouse reports its status to your computer, which sets an upper bound on how quickly a click can be reported even after it's happened.
• Operating system handling: Windows, macOS, or Linux processes that incoming signal as an input event.
• Application or browser processing: whatever software is listening for that event, a game, an app, or in this case a webpage, has to receive and act on it.
• Display response: finally, your monitor has to actually refresh and show the result, which depends on its refresh rate and pixel response time.

Every one of those stages adds some amount of delay, usually somewhere between a fraction of a millisecond and a few milliseconds each. The total is what people mean by "input lag," and it's genuinely important for competitive gaming and generally relevant to how responsive a computer feels.

What this test can and can't actually measure

Here's the part worth being completely upfront about, because it changes how you should read your results.

A webpage can only start timing once your browser actually receives a click event. Everything listed above, switch debounce, firmware, transmission, polling, and OS-level handling, has already happened by that point. There's no way for JavaScript running in a browser tab to reach back and measure any of those earlier stages directly. That part isn't a limitation specific to this tool, it's a hard boundary of what a web page is able to see, full stop.

That leaves one more thing to account for: this test works by showing you something and having you click in response. The time between the prompt appearing and your click landing includes your own reaction time, the time it takes your brain to notice something and your hand to act on it. For a simple visual cue like this, human reaction time typically runs somewhere in the range of one to a few hundred milliseconds, and it varies a fair amount from person to person and moment to moment. That's dramatically larger than the hardware-level delays (typically well under 10 milliseconds combined) that make up actual mouse input lag. In practical terms, this means the number this test shows you is overwhelmingly a measurement of your reaction time, not your mouse's hardware latency, and any browser-based test built the same way faces the identical limitation, regardless of what claims it makes about precision.

So what is this test actually good for? Two honest things: checking whether your clicks feel consistent and responsive session to session, and comparing your own results back to back, for example testing the same mouse in two different USB ports, or comparing a wired versus wireless connection on your own setup under the same conditions. Used that way, relative changes in your results are meaningful even though the absolute number isn't a certified hardware spec. If you need an actual, isolated hardware latency figure, that requires specialized measurement equipment (high-speed camera rigs or dedicated latency-testing hardware) that sits entirely outside what any website, including this one, can do from inside a browser tab. If a click feels off in a way that seems more like a hardware fault than plain reaction time, it's worth taking a separate pass to check your buttons and clicks.

How to use the mouse input lag test

• Get into a normal, comfortable position with your mouse the way you'd usually use it.
• Start the test and click as soon as the prompt appears.
• Repeat for several rounds, the test will show you results across multiple attempts rather than a single click.
• Look at the overall pattern of your results rather than fixating on your single fastest or slowest click.

If you're comparing two setups (say, two different mice, or wired versus wireless), test them back to back in the same sitting, same posture, same level of attention. That controls for the biggest source of variation, which is you, not the hardware.

What your results mean

Reading your numbers as relative, not absolute

Don't treat your result as "my mouse has X milliseconds of input lag." Treat it as a baseline for your own comparisons. If switching USB ports, disabling wireless power saving, or changing a setting measurably shifts your average result in repeated testing, that's a meaningful relative signal worth paying attention to, even though the raw number itself is dominated by reaction time rather than hardware delay.

Why results vary between runs

Expect noticeable variation from one attempt to the next, and even more between different testing sessions. This is normal and expected given what the test is actually measuring: human reaction time naturally fluctuates based on attention, fatigue, and even how anticipated the prompt felt on a given try. A wide spread across your attempts isn't a sign anything is wrong with your mouse, it's simply how reaction-based measurement behaves. Looking at your average or median across several attempts gives a steadier picture than any single click.

Polling rate vs latency: they're related, not the same thing

Polling rate, measured in Hz, is how often your mouse reports its status to your computer. A 1000Hz mouse can report up to once every millisecond, a 125Hz mouse once every 8 milliseconds. A higher polling rate lowers the maximum amount of time a click could theoretically sit waiting to be reported, which is a real, legitimate factor in overall latency.

But polling rate is only one stage in the pipeline described earlier. A mouse with a very high polling rate can still have meaningfully more switch or firmware delay than a mouse with a lower polling rate but a more efficient internal design. Polling rate is worth knowing and worth setting to your mouse's rated maximum in its companion software, but it isn't a complete stand-in for overall input lag, and a polling rate number alone won't tell you how responsive a mouse actually feels.

Does your display affect what you're testing?

Yes, and it's easy to overlook. Everything you perceive from this test, the prompt appearing and your own visual confirmation that it appeared, passes through your monitor. A display with a lower refresh rate (60Hz, updating the image 60 times per second) introduces more potential delay before a change is even visible to you than a 144Hz or 240Hz display would. That delay happens before you can react to anything, and it's part of what you're experiencing during this test, even though it's a property of your monitor, not your mouse. If you're comparing results across two different computers or monitors, keep in mind that display differences alone could account for some of the gap you're seeing.

Wired vs wireless input lag

Modern wireless mice using a dedicated 2.4GHz receiver have closed most of the practical gap with wired connections for typical use, largely because manufacturers have optimized their wireless protocols specifically for low latency in gaming mice. That said, this varies by specific mouse and receiver technology, and isn't a blanket guarantee. Bluetooth connections generally carry more inherent delay than a dedicated 2.4GHz receiver due to how the protocol itself is designed. A genuinely weak or degraded wireless connection, from interference, distance, or an aging battery, can also introduce inconsistency that a healthy wired connection wouldn't show. If you're trying to determine whether wireless is adding meaningful lag for your specific setup, testing the same mouse in both wired and wireless mode back to back, if it supports both, is more informative than any general rule.

Troubleshooting and reducing input lag

• My results feel inconsistent from one run to the next. Expected, given this test is largely measuring reaction time. Focus on your average across several attempts rather than any single result, and try to keep your attention and posture consistent between test sessions if you're comparing them.
• I want to actually reduce input lag, not just test it. A few things that genuinely help: set your mouse to its highest stable polling rate in its companion software, use a wired connection if latency is a specific concern, keep drivers and firmware updated, and close background applications that might be competing for system resources.
• My wireless mouse feels less consistent than I'd expect. Check battery level first, low battery is a common and often overlooked cause of degraded wireless performance. Also check for physical interference, other 2.4GHz devices nearby, or a receiver positioned too far from the mouse.
• I switched settings and don't see any difference in my results. That's plausible and doesn't necessarily mean the change did nothing. Given how much reaction time dominates this kind of test, a small, genuine hardware improvement can easily be masked by ordinary human variability between test runs.

If click responsiveness turns out fine but something still feels off, it's worth taking a moment to test your click speed too, since raw clicking speed and reaction-based latency point at two different things.

FAQ