Mouse test online
See whether every button responds, whether one double-clicks on its own, and the rate at which the mouse reports its position.
Ready
BUTTONSClick here with each button and spin the wheel
To look for double-click, click the left button about twenty times, fast.
Left
—
Middle
—
Right
—
Back
—
Forward
—
Wheel: 0 up · 0 down
Ready
HzClick start and keep moving the mouse inside this area for 5 seconds.
Also try
How the test works
Two tests on one page, nothing to install. The first checks that every button responds and looks for the double-click defect — the most common failure in a mouse with a few years on it, where one press of the finger turns into two clicks. The second measures the polling rate: how many times per second the mouse reports its position to the computer. A 1000 Hz mouse reports a thousand times a second; a 125 Hz one, eight times less — and it is common for a mouse capable of 1000 to be set to 125 without the owner knowing.
How the tests work
- Buttons: the page listens for the pointer press event and records which button arrived. If a button does not light up in the grid, it never reached the browser — so the problem is the mouse, the cable or the driver, not the test.
- Double-click: the page stores the instant of every click and shows the SHORTEST interval between two consecutive clicks on the same button. A worn switch "bounces" and generates two press-release pairs from a single press, with an interval too short for a finger.
- The button test gives no verdict on its own: it shows the number of milliseconds and leaves the conclusion to you, with the ranges explained below. A finger slip also produces a short interval, so what counts is repeating.
- Polling rate: every time the mouse reports a new position, the browser fires an event. The test counts those events for 5 seconds.
- It uses raw pointer events when the browser offers them. Without them, the count is capped at the screen refresh rate, and a 1000 Hz mouse would show up as 144 — in that case the page warns you before you measure.
- The result is the sustained peak: the best full one-second window, not the average over the period. Since nobody moves the mouse continuously, the average would be dragged down by the still moments.
- The number is compared with market rates (125, 250, 500, 1000, 2000, 4000, 8000) to suggest the closest one.
What each range means
- Double-click under 50 ms: no human finger closes two clicks in that interval. It is a faulty switch, and the fix is replacing the switch or the mouse.
- Double-click between 50 and 100 ms: suspicious. Repeat the test a few times; if the number keeps coming back, treat it as a defect. If it happened only once, it was probably a finger slip.
- Button that does not light up in the grid: no event from that button arrived. Try another USB port before concluding it is the mouse — and remember that side buttons need the manufacturer’s driver on some models.
- 125 Hz: the default for office mice and for gaming mice at factory settings. One position every 8 milliseconds.
- 500 Hz: one position every 2 milliseconds. For most people, the perceptible difference from 1000 Hz is small.
- 1000 Hz: the current gaming mouse standard, one position per millisecond. It is the point where the gain starts getting subtle.
- Above 1000 Hz: found in recent mice with a dedicated receiver. The gain is measurable, but it needs a PC that can keep up — a very high rate with a limited processor can even make things worse.
- Well below what you expected: check the manufacturer’s software and the USB port. USB hubs and front-panel case ports often cap the rate.
Where these tests stop
- The button test only sees what the browser receives. A side button that depends on the manufacturer’s software may not arrive — and that does not mean it is broken.
- The double-click test does not replace opening the mouse. It shows the signature of the defect, not the cause: it could be the switch, it could be dirt under the button.
- On a touchscreen there is no button to test. The page ignores touch events on purpose, so nobody gets a "left OK" just for tapping their phone.
- The polling rate measurement depends on you moving the mouse continuously. Slow movement or pauses generate fewer events and a lower number than the real one.
- Firefox and Safari do not expose raw pointer events. In those, the count is capped at the screen rate and the result comes out underestimated — use Chrome, Edge or Opera to measure for real.
- The browser may batch events when the system is overloaded. Close heavy programs before measuring.
- This test measures what reaches the browser, not what leaves the mouse. They match in most cases, but a bad cable, a USB hub or a faulty driver can lower one without changing the other.
- Polling rate is not the same as DPI. One sets how often the mouse reports, the other the precision of each reading.
Common problems
My mouse double-clicks on its own. Can it be fixed?
Yes, and not always expensively. If the mouse is still under warranty, contact the manufacturer. Out of warranty, replacing the switch is cheap and any repair shop can do it — the same defect shows up in mice of every price range after a few million clicks. Before that, it is worth cleaning: dirt under the button produces the same symptom and comes out with compressed air.
A side button does not register in the test.
On many mice the side buttons only send a signal when the manufacturer’s software is installed and the profile is loaded. Test first with the software open. If it still does not arrive, switch USB ports before concluding it is a defect.
I set 1000 Hz in the software, but the test says 125.
Three common causes, in this order: the software profile was not saved to the mouse, the mouse is plugged into a USB hub or a front-panel case port, or the browser does not expose raw events. Test first on a rear USB port, straight into the motherboard, using Chrome or Edge.
The number keeps fluctuating while I move.
That is expected. The rate shown during the test is the one from the last second, and it varies with the speed of your movement. What counts is the final result, which uses the best sustained window.
Is it worth going from 500 to 1000 Hz?
The difference exists but is subtle, and smaller than going from 125 to 500. If your mouse supports it and the PC can keep up, leave it at 1000. If you are at 125, then the change is noticeable.
My polling rate is right but the mouse still feels delayed.
Polling rate is just one link in the chain. Mouse acceleration enabled in Windows, the graphics card’s frame buffer, display sync and background processes all add milliseconds. If the test came out fine and the feeling of delay persists, the problem is at another point in that chain.
What next?
Did the test find something odd?
If the polling rate is correct and the mouse still feels delayed, the delay is in another link: pointer acceleration, the graphics card’s frame queue, display sync or DPC latency. Reducing that is system tuning, not a peripheral swap — the guide on mouse delay walks the whole chain.