Mouse Double Click Test
Count browser button events; a rapid pair alone does not diagnose hardware failure.
Click the mouse buttons above to test...
How to use the mouse double-click test
Place the pointer over the left target and use your primary button, then place it over the right target and use your secondary button. Make slow single presses first, then try deliberate pairs. Keep the pointer over the target while releasing the button.
Left Clicks counts browser click events. Left Double-Clicks counts the browser's own double-click event, whose timing depends on your platform. The right target counts button-2 releases and non-overlapping pairs separated by at most 500 ms. Three rapid releases form one pair, not two overlapping pairs.
The log shows the latest ten entries. Reset clears all counts, log entries and the pending right-pair timestamp. Neither result is a switch-health certificate. A browser cannot tell whether two events came from an intentional pair, a remapped input or unwanted device behavior.
If a single press seems to register twice
Repeat slow single presses and record the pattern. Check the same action in another application, review button mappings and double-click settings, and compare another device or computer if available. Contact the manufacturer with those observations before opening the mouse or replacing parts.
The W3C UI Events specification defines primary and secondary button values; its double-click event definition is for the primary button. This page therefore reports secondary-button pairs using its own stated threshold.
Frequently asked questions
Can this test prove a mouse switch is faulty?
No. It observes events delivered to the browser, which may be affected by device firmware, operating-system settings, browser behavior and your clicking technique. Repeat slow single presses and compare another application or device before drawing conclusions.
How are right-button pairs counted?
The right target counts releases with MouseEvent.button equal to 2, normally the secondary/right button. Two consecutive releases within 500 milliseconds count as one non-overlapping rapid pair. This is a page-defined timing rule, not the operating system double-click setting.
Why are the left and right totals different?
The left target counts primary click events and browser-generated dblclick events. The right target uses secondary-button release timing because browser dblclick events are intended for the primary button. Button mappings can be changed in your operating system.
Related checks: right-click speed, drag/release behavior and wheel events.