Skip to content
Language: EN
Theme: SystemTheme: LightTheme: Dark

Mouse button test

The mouse button test counts every button press and wheel step, times your double-click and flags unintended double-clicks. No install needed.

Click every button and turn the wheel inside the test area. There the wheel does not scroll, and right-click, back and forward stay on this page; outside it, or after Stop test, your mouse works as usual. Taps are not counted: use a mouse or touchpad.

Runs in your browser. Test data stays on your device.

Double-click speed
–
Unintended double-clicks
–
Presses
–Left–Middle–Right–Back–Forward–
Wheel steps
–Up–Down–Left–Right–

How to use the mouse button test

  1. Click Start mouse test.
  2. Inside the test area, click the left, middle and right buttons, then the two side buttons. A button lights up while you hold it, and its count goes up by one per click.
  3. Turn the wheel up and down, and tilt it left and right if it can. Double-click a few times to read your double-click speed.
  4. Click about 20 times in total at an ordinary pace, so the test can give a verdict on unintended double-clicks.
  5. Click Stop test when you have finished.

Inside the test area the wheel does not scroll the page and right-click opens no menu, and in Chrome and Edge the back and forward buttons do not leave the page. Outside it, or after you stop, the mouse works as usual. Stop test keeps the counts, starting again carries on from them, and Reset counts clears them. Use a mouse or a touchpad, because taps and pen touches are not counted.

What the results mean

Four cells show what the buttons, the wheel and your double-clicks did: Presses, Double-click speed, Unintended double-clicks and Wheel steps.

ResultWhat it meansWhat to do
A button’s count goes up by 1 per click and the button lights while heldThe button works.Nothing to fix.
A button’s count stays at 0No press reached the browser. The button may be remapped, may send a keyboard shortcut instead, or may have a dead switch.Check your mouse software and the system settings, then try another USB port or another mouse.
One click adds 2 to a count, and Unintended double-clicks says FoundThe switch bounced. The same button registered again less than 20 ms after a release, or less than 80 ms after its previous press with under 30 ms up in between.Blowing dust out around the button may help for a while. If it keeps happening, replace the switch or the mouse.
Unintended double-clicks: Verdict after 20 pressesFewer than 20 presses so far, which is too few to judge.Keep clicking at an ordinary pace.
Unintended double-clicks: None, with the number of presses checkedNo press was flagged among that many.Nothing to fix. A bounce can be occasional, so repeat the test after some use.
Double-click speed: a value in msThe time between the two presses of your latest double-click.Nothing to fix. Change the double-click speed in your system’s mouse settings if it feels off.
Double-click speed: a dash after double-clickingThe second press was flagged as unintended, which clears an earlier value, or no double-click has been counted yet.Double-click again at an ordinary pace. If the dash comes back, see the rows above.
Wheel steps go up in the direction you turnThe wheel sends events. A notched wheel gives one step per notch, a smooth wheel or touchpad gives many small steps.Nothing to fix.
Back and Forward stay at 0 in FirefoxFirefox does not pass these two buttons to websites.Test them in Chrome or Edge.

Wheel steps counts one step per wheel event and direction: up and down from vertical movement, left and right from a tilting or horizontal wheel. Ctrl with the wheel zooms the page and is not counted. A flagged press adds a warning mark to its button, and Presses shows the total across all five buttons.

Double-click speed is a pace, not a pass mark. Your system decides how slow a double-click may be, and the Windows default is 500 ms. A value in the cell means the system accepted the two presses as one double-click.

Mouse not working?

The mouse test needs no permission, so it can show only one error message of its own.

Your browser does not support this test

The test needs pointer events. A browser without them shows this message in place of the test area. Update the browser, or open the page in Chrome, Edge, Firefox or Safari.

A button does nothing

Mouse software such as Logitech G HUB or Razer Synapse, or the system settings, may have remapped it, so that it sends a keyboard shortcut or a macro instead of a button press. Set the button back to its default and test again. If its count still stays at 0, the switch or the cable may be at fault, so try another port or another computer.

One click counts twice

The switch under that button is bouncing, which points to a worn microswitch in most cases. Blowing dust out around the button may help for a while, and the switch or the mouse needs replacing if it keeps happening.

Back or forward leaves the page

In Chrome and Edge the test cancels the back and forward buttons inside the test area. If the page still leaves, your mouse software may send a keyboard shortcut instead of a button press, so set the button back to its default.

Firefox does not count back and forward

Firefox passes no events for these two buttons to a page and navigates by itself. While the pointer is over the test area, pressing them, reloading or closing the tab asks you to confirm leaving the page. Test the two buttons in Chrome or Edge.

The wheel scrolls the page or is not counted

The wheel is blocked from scrolling only over the test area while the test runs. If the page scrolls, the pointer is outside the area or the test is stopped. Ctrl with the wheel zooms the page and is never counted.

Taps are not counted

On a phone or tablet the test shows a notice that taps and pens are ignored. Connect a mouse, or use a touchpad on a computer.

The test stopped by itself

Switching to another tab or leaving the page stops the test. The counts stay on screen, and Start mouse test carries on from them.

How we measure

The test reads pointer events with their button numbers and timestamps, counting one press per button-down and one wheel step per wheel event and direction. A press is unintended when it comes less than 20 ms after a release of the same button, or less than 80 ms after its previous press with under 30 ms up in between. The verdict None needs 20 presses, and the double-click speed is the gap between the last two left presses when the browser reports a double-click. A browser cannot report the switch itself, DPI, polling rate or buttons beyond the standard five, so the test shows only what the browser receives.

Frequently asked questions

How do I test whether my mouse double-clicks by itself?

Click each button slowly in the test area, about 20 times in total. Unintended double-clicks shows Found and names the button as soon as one press comes too soon after the previous press or release, and it shows None only once 20 presses have been checked. Repeat the test after a single Found, because fast clicking can cause one.

Does a click that counts twice always mean a worn switch?

Usually, but not always. The test flags only presses faster than anyone clicks on purpose, so a worn microswitch is the likely cause. Very fast techniques such as butterfly clicking can be flagged too. Your system’s double-click speed setting has no effect on this flag, because the test counts raw presses. Click slowly and repeat the test before you replace the mouse.

Why does the test not count my back and forward buttons?

Because Firefox does not pass those two buttons to web pages. Test them in Chrome or Edge instead, and see “Firefox does not count back and forward” further up this page for what the test does in Firefox.

What double-click speed should I set in my system settings?

That depends on how you click. Do a few double-clicks in the test area and note the largest value in Double-click speed. The system should accept at least that long between clicks, so if it misses your double-clicks, move the double-click slider in your mouse settings toward Slow.

Does the mouse test work with a touchpad, a phone or a tablet?

With a touchpad, yes, because the browser reports its buttons as a mouse. A phone or tablet needs a mouse connected, since a tap is not a mouse button and the test would show buttons as working that it never tested. It shows a notice when it sees a tap or a pen.

Is the mouse test private?

Yes. Clicks and wheel turns are handled only in your browser, and the results never leave your device. The test listens to the mouse only while it runs.

Related tests

Reaction time testGamepad testKeyboard testTyping speed test