Choose a button
Use Auto to lock the first button you press, or select Left, Right or Middle before starting.
Check whether one mouse press is registering twice with this mouse double click test. Test one button at a time, inspect the intervals, then retest after a simple environment change.
Runs locally in your browser — your clicks are not uploaded, and you can copy an evidence summary for support.
Do not intentionally double-click. Only complete single-button mouse presses are analysed.
Collecting observations
Intervals compare each press with the previous press of the same button. Only complete single-button mouse presses are counted.
Press once at a time inside the test area. The tool compares consecutive presses of the same button, so left and right clicks never get mixed together.
Use Auto to lock the first button you press, or select Left, Right or Middle before starting.
Keep a natural pace. Touch, pen and keyboard-activated clicks do not enter the sample.
If repeated input is observed, change browser, port, receiver position or computer and run another round.
This page reads the input your browser reports; it cannot inspect a mouse switch, identify your mouse model, or confirm an electrical fault. A clean round does not exclude an intermittent problem. On a phone or tablet, a detected pointer is labelled “mouse-like input” because browsers cannot reliably identify the physical device.
Two presses of the same button arriving almost together are the strongest signal this page can see. The bands below are observation ranges used by this test, not a hardware standard.
| Same-button interval | What to do |
|---|---|
| 50 ms or less | Almost impossible to produce deliberately — treat it as a candidate repeat and run a second round. |
| 51 – 100 ms | Fast but ambiguous — a quick intentional double-click can land here. Slow your pace and retest. |
| More than 100 ms | Usually two separate single presses — likely normal spacing. |
These ranges are versioned in the methodology, based on published switch-bounce and human double-click timing data.
Repeated input is an observation, not a verdict. Work through these before assuming hardware failure, and use the mouse double-clicking guide for the full checklist.
Button remapping, macro software, single-click-open modes and a double-click speed set very low can all produce a second trigger.
A low battery, receiver position, USB port or wireless interference can change how input arrives at the browser.
A worn switch is one possibility, but so is behavior that is specific to one application. Compare across apps and computers first.
No. It is an observation that should be retested after changing one environment factor. Software mappings, connections and a specific app can also affect what you see.
Intervals of 50 ms or less are almost impossible to produce deliberately and are flagged as candidate repeats. Between 51 and 100 ms is ambiguous, so retest with a slower pace. Deliberate double-clicks are usually more than 100 ms apart. These ranges come from the versioned methodology.
Touch and pen input do not test a mouse switch. You can still browse this page; connect a mouse and click in the test area to begin.
Yes. Back and Forward buttons are supported, though browser support varies, and wireless or Bluetooth mice work like any other mouse the browser can see. A low battery can produce missed or repeated events.
Not necessarily. Games can have their own input handling, and fast intentional clicking can look similar. Run slow single clicks and let the result — not a single moment in a game — guide your next step.
No. Your presses and checklist choices stay in page memory and disappear when you refresh.
Use the mouse test to check buttons and scroll wheel, the Double Click Test when one mouse press seems to register twice, the double click speed test to measure intentional double-click timing, the CPS test to measure click speed and clicks per second, the right click CPS test for right-button-only speed, and the keyboard double click test for double typing or key chatter.