Check whether your mouse is registering one click twice. Use this free double click test in your browser to find possible switch bounce or accidental duplicate click events in a few seconds.
Use one physical mouse click per round. The test watches the input received by this page and flags very close duplicate signals without uploading your click data.
Start a session, then click the test area once whenever the prompt is ready. Do not intentionally double click.
Ready for a 10-round mouse double click test.
The most useful session is controlled and repeatable. This test is not a speed challenge: it asks for one click, records what the browser receives, and explains what the result can and cannot tell you.
Keep the default ten rounds for a quick check, or choose more rounds when the double click problem appears only occasionally. Use the same setting when comparing two sessions.
Press Start test and wait for the first prompt. The page begins listening only after you start, so navigation and setup clicks are not part of the reading.
Use the physical left mouse button once, then wait for the next round. An intentional fast double click can look exactly like an accidental duplicate event to a browser.
Check completed rounds, total click events, suspected duplicates and the shortest flagged interval. Repeat the test if the symptom is inconsistent.
When a mouse switch starts to wear, one physical press can sometimes produce more than one input signal. That behavior is commonly described as a mouse double click problem. A browser cannot inspect the electrical contacts inside the switch, but it can show whether this page receives rapid duplicate mouse input while you are deliberately making single clicks.
During a session, the tool records valid physical mouse presses inside the test area and measures the time between neighboring signals with a monotonic browser timer. A signal inside the selected threshold is counted as a suspected duplicate instead of being treated as a new completed round. This keeps the result focused on accidental double clicks rather than rewarding fast clicking.
A warning is evidence that the browser saw a close pair of mouse events; it is not a laboratory measurement or a repair certificate. The same result can come from an intentional double click, a crowded setup, an unusual driver behavior, or a threshold that is not appropriate for the comparison you are making.
A clear result is also limited. Switch bounce can be intermittent, so one quiet ten-round session does not prove that a mouse will behave perfectly in every application. Use the result as a fast troubleshooting clue, then compare the same mouse on another computer or compare it with a mouse that is known to work.
The result combines a plain-language state with the underlying session counts. Look for a pattern across repeat tests instead of treating one number as a verdict about the entire mouse.
The current session did not contain a rapid duplicate event inside the selected threshold. If the mouse still double clicks in another app, run the test again and compare the behavior on another computer.
The page received one or more close duplicate signals while you were asked to click once. Restart with careful single clicks. If the warning repeats, investigate the mouse, operating-system settings, drivers and the affected application.
The session was interrupted, too few rounds were valid, or the input was not a physical mouse. Restart with the page in focus and complete the requested rounds before interpreting the metrics.
Testing is most useful when the conditions are simple and repeatable. Use the button that causes the problem, keep the mouse on a stable surface, and make the same single-click motion each round. If you are comparing settings or computers, keep the round count and threshold unchanged for the first comparison so the outputs describe the same experiment.
If the issue happens only sometimes, a second or third session can be more informative than changing every setting at once. Record the threshold beside your result. You may compare 300 ms, 500 ms and 700 ms to understand sensitivity, but keep the default 500 ms session as the easiest baseline to explain to support or a repair shop.
Use the physical mouse and the exact button that shows the symptom.
Click once, then keep your hand still until the next prompt appears.
Repeat the session if the mouse problem is intermittent.
Compare the mouse with another computer or a known-good mouse when possible.
Do not treat an intentional fast double click as proof of switch failure.
If only one application is affected, check that application before replacing hardware.
The measurement in this MVP is performed in the browser. The page uses the test area, local timing and visible result fields; it does not need your mouse events sent to a conversion API or stored as a user account record. That makes the tool quick to try and avoids asking you to upload a file or install a diagnostic program.
The website can still load ordinary hosting, analytics or advertising services, and those services have their own data practices. Read the Privacy Policy for the site-wide explanation. The local test promise applies to the click measurement itself and must remain aligned with the code as the tool evolves.
These answers cover the questions people usually have when a mouse starts turning single clicks into double clicks.
No. A CPS test measures how many clicks you can intentionally produce in a time window. This double click test asks for one click per round and looks for a rapid duplicate signal, so it answers a different question.
Start the accidental double click test, click the test area once for each prompt, and review the suspected duplicate count. Repeat the session if the result changes from one run to the next.
It is the default time window used to flag neighboring mouse events that arrive very close together. It is a practical browser-test setting, not a universal hardware standard or an operating-system certification.
You can open the page, but a touchscreen does not test a physical mouse. For a meaningful mouse double click test, connect the mouse you want to diagnose and use a desktop or laptop browser.
The detector can see the timing of input events but cannot know your intention. An intentional fast double click can therefore be flagged. Restart and make exactly one physical click per round.
No. It means that this session did not show a rapid duplicate event within the chosen threshold. Intermittent switch problems may need more rounds, another application or another computer to reproduce.
The MVP focuses on the left button because it is the most common problem area and keeps the first result easy to interpret. A future version can add right and middle button modes with separate context-menu handling.
