Event delivery
From click to screen
Not startedHow to test
About 30 secondsTipClose heavy programs first: the readings will be steadier.
How a web page measures latency
A click travels through the mouse, the computer and the monitor. A page sees when the system stamped the click and when the page received it. That gap is the click latency measured here.
Event delivery
Both stamps come from the computer: about 1 ms, more when busy.
Two waits
On average, half a polling interval for the report and half a frame for the screen. The page measures both rates.
Mouse and you
Debounce and the wireless link happen before the click reaches the computer, out of the browser's sight. Reaction time (200–250 ms) is not measured.
Readings that look wrong
4 casesDelivery often over 2 ms
CauseThe computer is busy, not the mouse
FixClose heavy programs
Polling rate only 125 Hz
CauseSet to 125 Hz in the software, or plugged into a dock or hub
FixSet 1000 Hz, use a port on the computer
Frame wait is the longest part
CauseA 60 Hz screen adds 8.3 ms on average
FixUse the highest refresh rate; in games, fullscreen without V-Sync, or G-Sync/FreeSync
Polling rate not readable
CauseOne move event per frame
FixTest again in Chrome or Edge
To lower latency, change this first
The bars show the wait before and after each upgrade. A faster monitor usually saves the most.
FAQ
8 questionsHow do I check mouse latency in a browser?
Three measurable partsClick repeatedly and move the mouse in the test area. This mouse latency tester measures the wait for a report, delivery to the page and the wait for the next frame. Debounce and the wireless link happen before the click reaches the computer, so no browser can measure them.
Is this an input lag test?
Part of itInput lag is the whole delay from click to screen. This page measures the parts a browser can see and shows the rest as typical ranges, so you can see which part takes longest. Keyboards, controllers and monitors each need their own tester.
What is a normal event delivery time?
Under 2 msUsually about 1 ms. If it is often above 5 ms, the computer or the browser is busy, and the mouse has little to do with it.
Why do the results change every time?
NormalThe system's scheduling, the browser's drawing cycle and the timing of each report each add a millisecond or so of variation.
How much does the monitor's refresh rate matter?
Often more than the mouseAt 60 Hz you wait 8.3 ms on average to see a change, at 144 Hz about 3.5 ms. That gap is usually bigger than the gap between two mice.
Do 4000 Hz or 8000 Hz polling rates lower latency?
By under 0.5 msThe average report wait drops from 0.5 ms at 1000 Hz to 0.06 ms at 8000 Hz, about 0.44 ms, and uses more CPU. The polling rate test shows your rate. Polling rate test →
Do wireless mice have more latency?
2.4 GHz: very littleCurrent 2.4 GHz wireless mice are close to wired ones. Bluetooth is slower and not suited to games, so use the 2.4 GHz receiver and keep it near the mouse.
Does this test measure reaction time?
No, that is youReaction time is how long you take to press after you see a change, typically 200–250 ms. It is not mouse latency, and this page does not measure it.