Mouse Latency Test: Input Stability in Your Browser

This test measures the variation in the intervals at which your mouse delivers events to the browser. It does not measure hardware click-to-photon latency.

When people say their mouse "feels laggy", they rarely mean a specific number of milliseconds. They mean the tracking feels uneven, the cursor snags for a fraction of a second, or a click seems to land late but only sometimes. That sensation has a proper name, input jitter, and it is something a browser can genuinely observe. This tool timestamps every mouse event it receives and works out how much those gaps drift apart from one another.

What you get back is a portrait of your input chain's steadiness: the USB port, the cable or wireless receiver, the system driver, the power manager and the browser itself. When everything is healthy, the gaps between events look almost identical and the variation stays tiny. When a background process is chewing through CPU or a power-saving profile is throttling your machine, the variation climbs and the results table makes it obvious straight away.

How This Test Works

mouseTests.latency.howText

How to Read Your Result

The ranges below describe the measured variation between consecutive event intervals, not your system's total latency. Match your reading against them to decide whether further investigation is worth your time.

Measured Variation	What It Indicates	Likely Cause
< 1 ms	Very stable input, events arriving at an almost perfect cadence	Nothing to fix; your input chain is behaving exactly as it should
1–2 ms	Stable and entirely normal for a healthy machine	Ordinary system fluctuation; no action required on your part
2–4 ms	Slight irregularity, noticeable only during very fine movements	System load, or a busy browser juggling other tabs and tasks
4–8 ms	Clear irregularity; tracking may feel uneven under pressure	Background processes running, or a power-saving profile enabled
> 8 ms	Very unstable input with visible stutters and gaps between events	USB problem, driver issue, low battery, or an overloaded browser

Why Input Stability Matters

The total latency you feel is a sum of separate stages, each contributing its share. Polling rate sets how often a new position leaves the mouse; refresh rate sets how often that position can appear on screen; render time inside the game or application adds another slice; and the frame queue can stack up already-rendered images waiting their turn. None of these stages is visible from a web page, which is precisely why no web page can hand you a final number.

Input jitter still matters enormously, though. The brain adapts remarkably well to a constant delay: if everything arrives twelve milliseconds late, every time, you learn to compensate without ever noticing. What cannot be compensated for is a delay that changes from moment to moment, because it breaks the motor prediction that precise aiming depends on. A setup with higher but perfectly regular latency usually feels better than a faster, erratic one.

It is equally worth knowing what skews the reading. An antivirus scan, an active download or a video editor left open will inflate the variation with no fault at all on your mouse's part. Battery modes and power-saving plans drop CPU frequency and stretch the gaps between events. And USB hubs, or ports sharing a controller with a keyboard, webcam or external drive, introduce uneven gaps that vanish once the mouse gets a port of its own.

Tips for a Reliable Measurement

Close heavy tabs and background applications before you start; a browser juggling twenty active tabs will skew the reading far more than any mouse ever could.
Plug the mouse straight into a port on the machine and avoid USB hubs, particularly ones sharing a controller with external drives or webcams.
On a laptop, connect the charger and switch to the maximum performance profile; power-saving plans stretch event gaps and inflate the variation you measure.
With a wireless mouse, check the battery level and move the receiver closer, since many models quietly reduce their polling rate once the charge drops.
Run the test three or four times with a few seconds between attempts and trust the overall trend rather than the number from any single run.
Keep the mouse moving continuously at a moderate speed throughout; sudden stops and violent flicks create gaps that misrepresent your everyday usage.

Frequently Asked Questions

Can I measure my mouse's real latency with this test?

No, and that is worth saying plainly. Real latency runs from the physical click to the photon leaving your monitor, passing through firmware, USB transport, the operating system, the GPU and the panel. A browser only observes one already-processed slice in the middle. Measuring that full path needs external hardware such as an LDAT device, or a high-speed camera filming mouse and screen together.

So what is the number on screen actually telling me?

It tells you how much the intervals between consecutive mouse events vary as they reach the browser. If the gaps are nearly identical, the figure stays low and your input is steady. If some gaps stretch while others shrink, the figure rises and something is interrupting the stream. It is a measure of regularity, not of absolute speed.

Does a high value mean my mouse is broken?

Rarely. In most cases the environment is to blame: background processes, a loaded browser, an aggressive power-saving plan or a congested USB hub. Try a different port first, with the laptop plugged in and heavy applications closed. If the variation stays high across all of those scenarios, then it becomes worth inspecting the cable, the receiver or your drivers.

Does my mouse polling rate affect the result?

It affects the baseline gap between events, since a higher rate means shorter gaps. But this test does not measure that gap, it measures its regularity. A modest, rock-steady polling rate can score better than a very high one whose stream keeps getting interrupted by the system. Stability and frequency are genuinely two different properties.

Will I get the same result in every browser?

Not always. Each browser batches and delivers pointer events slightly differently, and some clamp timer precision for privacy reasons. Active extensions can add their own processing delay on top. If you plan to compare two configurations, always run the test in the same browser with the same extension profile so the comparison actually means something.