🖱Is your mouse double-clicking on its own?

✓ Tested & verified Updated: Aug 11, 2026 How the test works

Double click test

Click here — normally, not fast

Single clicks, about one a second. The test watches the gap between two presses, not your speed.

Double fires

0chatters

Two presses closer together than the threshold below cannot come from a human finger — that is switch chatter, the contact bouncing inside the button.

Clicks counted—
Shortest gap—
Typical gap—
Worst run—

Chatter threshold

Try also

How do you tell if a mouse is double-clicking on one press?

The double click test counts how often one press produces two button-down edges less than 50 milliseconds apart, and that is switch chatter rather than anything your hand did. Fifty milliseconds is the cutoff because no hand moves that fast: a deliberate double click lands between 100 and 500 milliseconds, and Windows treats anything up to 500 as one double click by default.

The fault is mechanical. The contacts inside the button bounce every time they close, and the mouse firmware ignores that bounce for a few milliseconds. As the contacts wear, the bounce outlasts the window, and the computer receives a second click that is entirely real.

Click one button at least fifty times, slowly and deliberately. Chatter is intermittent, so a clean run of ten proves nothing while two hits in a hundred is conclusive.

The whole diagnosis is one measurement: how long between the two presses. Human intent and switch bounce live in completely different parts of the scale, which is what makes the fault provable rather than a matter of opinion.

Gap between two press edges	What it is
Under 1 ms	usually swallowed by the mouse firmware; the page never sees it
1–25 ms	switch chatter, far faster than any hand
25–50 ms	still chatter, and where this test’s threshold sits
50–100 ms	physically possible on purpose, rare in ordinary use
100–500 ms	a deliberate double click; Windows accepts up to 500 ms by default
Over 500 ms	two separate single clicks

Note the gap in the middle of the scale. Between roughly 25 and 100 milliseconds almost nothing happens on a healthy mouse, and that empty band is what lets a 50 millisecond threshold separate the two causes cleanly.

If a button produces no click at all rather than two, start with the mouse tester. If movement stutters while the buttons behave, the polling rate test measures how often the mouse is reporting. Keys chatter for the same mechanical reason, and the keyboard tester will show it.

Frequently asked questions

My mouse clicks twice on one press. Is it broken?

Yes, if the two clicks land under about 50 milliseconds apart, because nothing a hand does is that fast. The switch under the button has worn to the point where its contact bounce lasts longer than the firmware’s debounce window. It never recovers, and it gets more frequent with use: a mouse that chatters once a day this month usually chatters hourly in a few months.

Can I fix chatter without replacing the switch?

Sometimes, and only as a delay. Some mice expose a debounce setting in their software, and raising it from around 4 milliseconds to 8 or 12 hides most chatter at the cost of that much click latency. Contact cleaner sprayed into the switch buys weeks rather than years. The permanent fix is a new switch, which is a five-dollar part and a soldering job.

How many clicks should I do before I trust the result?

At least fifty per button, and a hundred is better. Chatter typically shows up in something like one click in fifty when a switch first starts to fail, so a run of ten can easily come back clean on a mouse that is already faulty. Two or more chatter events in a hundred deliberate clicks is a conclusive result.

Will raising the double-click speed setting in Windows help?

No. That slider only decides how far apart two clicks may be and still be treated as one double click, with a default of 500 milliseconds. Chatter arrives 50 milliseconds apart or less, so it falls inside every setting on the slider. The setting changes how the system interprets two clicks, never whether the second one exists.

Files keep dropping in the wrong folder when I drag them.

That is chatter on the release edge and it is often noticed before the double click is. The button reports up and down again mid-drag, so the system completes a drop wherever the pointer happened to be. If dragging is unreliable but clicking seems fine, run this test on the left button anyway — the same worn contacts cause both.

The test finds nothing but my mouse still misbehaves in games.

Two explanations are worth checking. Chatter is intermittent and often worse when the mouse is warm, so test again after an hour of use rather than from cold. And games usually read raw input directly, while a browser sees events after the operating system has processed them, so a very short bounce can be filtered before this page ever gets it.

How the test works

The test timestamps each button-down and button-up edge from the pointer events the browser delivers, using the page’s monotonic clock so that no system time adjustment can distort an interval. For every button it measures the gap between consecutive down edges and counts every gap below the threshold, which is 50 milliseconds by default because a deliberate double click sits an order of magnitude above it, between 100 and 500 milliseconds. Down edges are used rather than the browser’s own double-click event, since that event is the operating system’s interpretation of two clicks and reports nothing about the interval that produced it. One honest limit belongs on the result: the mouse’s own debounce has already discarded the shortest bounces before the computer hears about them, so this test finds the chatter that escaped the firmware, not every bounce the contacts made. Clicks are counted in the page and nothing is stored or sent.

Worked example

With times of seven deliberate single clicks (ms) 0, 118, 126, 402, 771, 779, 1150, chatter threshold 50 ms, this page works out 2 chatters. Two presses 8 ms apart are not a finger — that is the contact bouncing inside the switch, and it is the same fault that makes one click open two tabs.

Chatters found2
Shortest gap8.0 ms
Median gap197.0 ms

Sources:

Why switches chatter in the first place

Every mechanical contact bounces. Two pieces of metal meeting at speed separate and meet again several times in the first milliseconds, and every switch ever made does it. Firmware hides it with a debounce window of a few milliseconds, which is why a new mouse feels perfect.

Wear lengthens the bounce, not the click. Oxidation and mechanical fatigue stretch the bounce until it pokes out past the debounce window. Nothing about the click itself changed, which is why the fault appears suddenly and feels like software.

Click count is the real odometer. A switch rated for twenty million clicks meets that figure in a couple of years of heavy gaming, and the left button always fails first because it takes the vast majority of them.