Mouse Test
Check every button, the scroll wheel, and whether your mouse is double-clicking.
Loading the test…
About the Mouse Test converter
The commonest mouse fault is not a button that stops working — it is one that works twice. A worn switch bounces, so a single press registers as two clicks, and files open twice while drags turn into double-clicks.
This catches that directly by timing the gaps between clicks, alongside the ordinary checks: every button, both scroll directions, and how often the mouse reports its position.
The double-click fault, measured
Nobody clicks twice in under about sixty milliseconds — human muscles do not move that quickly. So any two clicks arriving closer together than that were not two presses; they were one press and a switch bouncing as its contacts wear.
The counter records every occurrence. One or two over a long session can be a quirk of the browser, but a steady stream while clicking normally means the switch is failing, and it only gets worse.
Report rate, and why it is an estimate
A mouse tells the computer where it is at a fixed rate — 125 times a second on an ordinary one, up to 8000 on a gaming mouse. Measuring the gaps between movement events and taking the median gives a good approximation, snapped to the nearest rate hardware actually uses.
It is an approximation rather than a measurement, because browsers sometimes group movement events together for efficiency. A mouse may well report faster than the page can observe, so treat a low figure as a floor rather than a verdict.
Buttons a browser can see
Left, middle and right are universal. The side buttons on many mice report as back and forward and are tested here too, though some mice send keyboard shortcuts instead, in which case they will not appear.
The right button would normally open a context menu, which would end the test — so the page suppresses that inside the testing area, and only there.
Frequently asked questions
My mouse is double-clicking. Can it be fixed?
Sometimes. The fault is usually a worn switch, and cleaning or replacing that switch fixes it properly. Software workarounds that ignore rapid clicks exist, but they hide the symptom rather than curing it, and make genuine fast clicks unreliable.
Why is the measured report rate lower than my mouse claims?
Browsers can batch movement events together, so the page sees fewer than the mouse sent. The figure is a floor rather than a ceiling. Moving the pointer continuously for a few seconds gives the best estimate.
My side buttons do nothing here.
Some mice send keyboard shortcuts for those buttons rather than mouse buttons, in which case a browser sees a key press and not a click. They are working; they are simply not reporting as buttons.
Does this measure DPI or sensitivity?
No. A browser cannot see the physical distance a mouse moved, only how far the pointer travelled on screen after the operating system has applied its own scaling and acceleration.
Is anything recorded or sent anywhere?
No. Everything is measured by the page itself and forgotten when you close it. Nothing is uploaded, and no permission is asked for, because none of these tests need one.