What this test checks
Look for unintended duplicate mouse clicks by comparing event timing while you make deliberate single clicks.
InputAnalyzer processes test events locally and does not upload your raw inputs or result values.
How to run the test
Use deliberate single clicks
Place the pointer in the test target and click once at a time without intentionally double-clicking.
Keep a steady pace
Make at least 20 separate clicks with a comfortable pause between each one.
Repeat suspicious results
If a close pair is flagged, change finger pressure and reconnect the mouse before another run.
How to read the result
Observed signals, not artificial certainty.
Separated clicks
Each physical press produces one click event with intervals consistent with the pace you used.
Unexpected close pair
Repeated pairs far faster than your deliberate pace can be consistent with switch bounce, but need confirmation.
What this test cannot prove
What the browser cannot see
- A fast pair may be intentional or caused by technique; timing alone cannot diagnose a worn switch.
- Operating-system double-click settings and browser scheduling affect event grouping and timestamps.
- Results are browser-based estimates, not a physical hardware diagnosis.
Useful next tests
Frequently asked questions
Short answers before you test again
Does one flagged pair mean my mouse is faulty?
No. Repeat the test with slow, deliberate presses. A pattern across several runs is more meaningful than one pair.
Why test intervals instead of only the dblclick event?
The browser's `dblclick` event follows system timing rules. Raw intervals provide useful context without claiming a physical diagnosis.