Free online double click test
Double click test that times the second press
Press deliberately, one click at a time, and the pad times the gap between consecutive presses of whichever button you chose. Under 40 ms is a contact rebounding shut rather than your finger; 40 to 80 ms is a switch on its way there; anything longer is you. Each incident is logged with its interval and the press number it landed on, so a mouse that doubles once in fifty presses leaves a record instead of an argument — and a second mode times the pairs you make on purpose, which is the figure to hold against your system’s double-click speed.
- 100% free
- No signup
- 80 ms fault line
- Per-press log
- Copies as text
20 more presses before this means anything
Press the left button here one press at a time, with a gap you can feel between each. Do not try to click quickly — the point is that you are not double-clicking.
Last gap: —
Every unintended double, newest first
A switch that doubles once in fifty presses will not show up in five. Keep going, and press lightly.
The bounces your mouse already swallowed never arrive here: firmware applies its own debounce window before a press leaves the device, so this page sees the doubles that escaped it rather than every bounce the contact made.
How to catch a mouse that clicks twice on its own
The fault hides from a hard, fast press, so these three steps are arranged to make it show itself.
Pick the button that is misbehaving
Left is where the fault almost always begins, but the selector also covers the right button and the wheel pressed straight down, and each one gets its own run so their intervals never mix. Inside the pad the context menu is held shut and the wheel-press autoscroll widget is canceled, which is the only reason those two can be pressed forty times in a row without something popping up in the way.
Press lightly and slowly, at least thirty times
Resist every instinct to click quickly here: the run only means something if you know that none of the presses you made were pairs. Use the gentlest press the button will accept and let your finger come off it unhurried, because a contact that has lost tension misbehaves on a soft close long before it does on a firm one. Twenty presses is where the verdict appears and fifty is where an occasional fault usually gives itself up.
Read the rows, not the headline
Each row names the two press numbers it sits between, the gap in milliseconds and which band that gap fell in. Three rows under 20 ms is a switch that has already failed; a single row at 71 ms is one that is on its way. Copy the log carries the rows, the date and the browser you ran them in, which is the shape a shop or a manufacturer will actually read.
Technical specifications
| Event timed | pointerdown — it arrives before the browser synthesizes a double click and before any tap delay is applied |
|---|---|
| Fault thresholds | Under 40 ms is a bouncing contact, 40 to 80 ms is a switch on its way there, above 80 ms is a hand |
| Buttons covered | Left, right and the wheel pressed down, one at a time, each on its own run |
| Presses before a verdict | 20 — an occasional fault hides far too easily in five |
| Clock resolution | event.timeStamp, clamped by the browser: near 0.1 ms in Chrome, 1 ms under Firefox's default timer precision |
| Beyond what a browser sees | Every rebound the mouse's own firmware already discarded, typically anything inside its 8 to 12 ms debounce window |
| Second mode | Times the pairs you make on purpose — median, fastest and slowest — against the 500 ms threshold a desktop ships with |
| Data kept | The intervals of the run you are in, held in memory; switching button or mode empties them |
Frequently asked questions
My mouse only does it sometimes. Will thirty presses find it?
Usually, though an early fault can stay quiet for a hundred. What raises the odds is copying the presses that trigger it in daily use rather than clicking the way a test invites you to: soft, unhurried, and from the same finger position you normally use. If a run comes back clean and the mouse still misbehaves on the desktop, run it again with the lightest press you can make land, then try holding the mouse at the angle you hold it while browsing — a contact that only fails under a slight twist of the shell is common enough to be worth ruling out.
Why does the fault disappear when I press harder?
A firm press carries momentum into the contact, and a contact that arrives with momentum behind it settles in one motion. A gentle press lets the metal leaf approach its seat slowly, so the tiny rebound as it lands takes longer to die away — and the whole fault is that rebound outlasting the window the mouse allows for it. The wiping action of a hard press also drags the contact across its mating surface and scrapes off some of the film that builds on it, which is why pressing hard can seem to cure the mouse for an afternoon.
Will changing the double-click speed in Windows or macOS stop it?
No, and the two settings are unrelated in a way worth understanding. That slider decides only how close together two separate presses must be before the system treats them as one gesture; it ships at 500 ms and moves roughly between 200 and 900 ms on Windows. A failing switch delivers its second press somewhere between 5 and 40 ms after the first, which is inside every position on that slider, so dragging it to the fast end changes nothing except how hard your deliberate double clicks become.
Can software fix a mouse that has started doing this?
It can hide it, and the hiding has a price. Several gaming mice expose a debounce setting in their own software — Razer, Glorious and a number of the smaller brands ship one — and raising it from around 4 ms to 12 or 16 ms makes the mouse discard its own rebound before it leaves the device. What you buy with that is a mouse that now waits longer before reporting your real presses, which is a poor trade if you paid for a fast one, and it stops working once the contact has degraded past the largest window on offer.
It only doubles inside one program. Is the mouse still to blame?
Probably not, because a worn contact has no idea which window has focus. Check three things in this order: whether the vendor software loads a profile of its own when that program starts, whether the button carries a macro that sends two clicks by design, and whether an accessibility setting — sticky keys, filtered clicks — is changing what one press means. If this page shows a clean run and the doubling survives all three, the last suspect is the program's own handling of rapid input rather than anything under your hand.
Is a chattering mouse worth repairing?
That depends on whether you can solder, because the fix is a component swap rather than a setting. The switch under most left buttons is a 6 mm micro-switch of the Omron D2FC family or a clone of it, it costs about a dollar, and replacing it is three joints on a through-hole board — well within a first soldering project, though it does mean opening a mouse whose warranty may still be alive. Contact cleaner squirted through the shell buys weeks rather than months, because it washes the film away without restoring the tension the leaf has lost.
What should I send a shop that says the mouse is fine?
Give them a reading rather than a description, which is what Copy the log produces. The block of text names the date, the browser and operating system the run happened in, the button under test, how many presses you made, and then one line per incident with the two press numbers and the gap in milliseconds. Twelve presses out of sixty arriving in pairs 9 ms apart is a measurement a support desk can escalate; “it sometimes clicks twice” is a sentence they have a script for.
About the switch that fires twice
Under a mouse button sits a micro-switch about six millimeters square, usually an Omron D2FC or one of its many clones, sold in variants rated for 10 million and 20 million actuations. Inside it a springy metal leaf is pushed onto a fixed contact, and metal landing on metal never lands cleanly: it rebounds a few times before it settles, making and breaking the circuit in the space of a few milliseconds. Every mouse already knows this, so its controller ignores anything that happens for a short window after a press is first detected — commonly 8 to 12 ms. The fault this page looks for is what happens when the leaf loses tension and grows a thin film where it lands: the rebound stretches out until part of it falls beyond that window, and one press leaves the mouse as two.
Two things follow from that, and both surprise people. The first is that the fault arrives on light presses before it arrives on hard ones, because a slow, gentle close gives the leaf the most room to bounce and does the least to scrape its contact clean — which is why a mouse can double reliably while you read and behave perfectly the moment you sit down to test it. The second is that your operating system’s double-click speed setting has nothing to do with any of it. That setting is a gesture threshold: it decides how close two independent presses have to be before the system decides you meant one action, and a rebound at 12 ms is far inside every value it can hold. If you want to confirm the button is reporting at all rather than reporting twice, the mouse tester checks all five switches in a single pass, and if what you actually wanted was a score for how fast you can click on purpose, that is the CPS test.
What a browser can offer here is narrower than it looks, and worth stating plainly. It never sees the switch — it sees the events the mouse chose to send after its own debounce had its say, so the rebounds swallowed inside the device are invisible and the count on this page is a floor rather than a total. It also has to time the right event: reading click would mean measuring the browser’s own double-click synthesis instead of the hardware, so the gap here is taken between two pointerdown events, before any of that machinery runs. Within those limits the measurement is exact, and it is the one thing a warranty conversation can use. The same wear shows up elsewhere in a machine, incidentally: a keyboard whose contact has started rebounding doubles letters in ordinary prose, which the typing speed test surfaces as words you never typed, and a wheel whose encoder has begun to misread itself makes a page jump back a line, which the scroll wheel test catches by watching the direction of every step.
What the interval log holds
Every number on this page is worked out by JavaScript running in the tab you are reading it in. Nothing you type, paste or open is uploaded, logged or kept, which is also why the tools carry on working after you disconnect from the network.
An incident row is two numbers — which press it followed and how many milliseconds after it arrived — and the run is a list of those numbers for as long as the pad stays on screen. Copy the log puts them on your clipboard because you pressed the button; changing the button under test, switching mode or reloading discards them, and no second copy exists to be discarded.