Press and release each mouse button on its own inside the test area, then scroll up and down. The Misfires counter flags same-button gaps under 80 ms for you to check, not as a diagnosis of a worn switch. Everything runs locally in your browser; nothing you click is sent anywhere.
How this test works
The test listens for pointerdown events inside the diagram, or mousedown events in browsers without Pointer Events. Clicks totals the presses it counts; Button names the latest one. The diagram uses the standard button indices: 0 for left, 1 for the wheel button, 2 for right, and 3 and 4 for back and forward. Events marked as touch or pen input are skipped. The mouse-event fallback has no pointer type to make that distinction.
Interval is the gap between the last two counted presses of the same button, timed when the page handles each event. A button's first press shows no interval. The displayed milliseconds are rounded, but the label uses the unrounded gap: under 80 ms adds to Misfires; 80 ms up to, but not including, 150 ms is labeled fast. These are test cutoffs, not limits on human clicking speed. Try single clicks with a full release between presses, and look for flags that recur when you did not intend a second click.
Scroll counts wheel events with a nonzero vertical delta, and the arrows show the reported direction. Horizontal-only events do not add to the count. The page asks the browser to block wheel scrolling, the context menu, middle-click actions and side-button navigation inside this area only. Some browser-level actions can still take priority; outside the area, these listeners do not block your usual controls.
Frequently asked questions
Why does my browser go back when I press a side button?
Some browsers handle the back and forward buttons (X1 and X2) outside the events this page can cancel. The tester tries to suppress navigation inside the test area. If you still move to another page, the press triggered navigation, but this test may not have received or counted it.
What does the Misfires counter mean?
It counts gaps under 80 ms between recorded presses of the same button. Choose Reset test, then make single clicks with a full release between each one. Rapid intentional clicks can also trigger the counter. If flags recur when you did not intend a second click, compare the mouse in another app or browser before drawing a conclusion about its switch.
My mouse has extra buttons that don't register here. Why?
The diagram labels five standard buttons: left, middle, right, back and forward. Mouse software may handle extra buttons itself or map them to shortcuts or macros instead of mouse button events. If the browser sends another button index to this test, the readout shows Button followed by its number. For a button mapped to a keystroke, try the keyboard tester; browser-reserved shortcuts may still be intercepted.
Why doesn't the scroll count match the notches I feel?
Scroll counts wheel events with vertical movement that reach the test area, not physical notches or scroll distance. The number of events for one movement depends on the device, driver and scrolling settings; touchpads can produce the same kind of events. Try scrolling both ways and watch which arrow lights instead of expecting a notch-for-notch count.
Can this test fix a double-clicking mouse?
No. This page reads browser events; it does not change the mouse or its settings. If your mouse software offers a debounce setting, it can filter closely spaced presses, but it may also discard intentional clicks and does not repair a worn switch. If unwanted double-clicks also happen in other apps, check the manufacturer's troubleshooting and warranty options. Whether a switch repair or replacement is appropriate depends on the mouse and the cause of the problem.
Device Bench