One click becomes two?
A guided check of the input events that reach this browser.
Choose a threshold before starting. Make at least 5 deliberate, separate left-button clicks inside the pad. Avoid intentional double-clicking in this guided check.
A canceled or interrupted run does not establish a hardware problem.
What reached the browser
No input observed yet.
0 presses · 0 adjacent intervals below 80 ms. A larger threshold flags more intervals.
Cannot judge yet
No completed run yet. Untested inputs are not failures.
Observations describe this browser session. They do not certify hardware health. Read the method and next steps →
If a single click registers as two
You press the left button once and the browser receives two presses a few milliseconds apart. This guided check counts adjacent primary-press intervals shorter than the threshold you pick (40, 80 or 120 ms) so you can see whether short intervals repeat under the same settings.
A hardware cause and an ordinary cause look the same
Two very different things produce the same short-interval pattern: a worn or bouncing switch (often called chatter), and deliberately fast or double clicking. The check cannot tell them apart on its own — that is why it asks you to click deliberately and separately, and why one flagged run reads as “observed once,” not a fault verdict.
How to read your result
- Not observed: no short intervals in your completed runs at this threshold — untested clicks stay unknown.
- Needs another check: short intervals appeared in one run; repeat before drawing any conclusion.
- Observed in more than one run: the pattern repeated at the same threshold in this session — the strongest signal this check offers.
- Cannot judge: the run was interrupted or had fewer than five deliberate presses.
What your shareable report shows
Your exported report records the threshold you used, how many of your press intervals were short, the sample size, your browser and operating system, and whether it reproduced across runs — the same details a manufacturer’s support team or a forum thread usually asks for.
If it reproduces, what to do next
- Repeat the check at a second threshold, then in a different browser, and if you can, on another computer or USB port. A pattern that survives all of those is more convincing than a single run.
- Check whether your mouse has a firmware update or a debounce/click-delay setting in its own software.
- Review the manufacturer’s warranty or return window and attach your exported report. A browser observation supports a support request; it does not replace the manufacturer’s own diagnosis.
These steps are general guidance, not a diagnosis. A browser check documents what happened in this session — the manufacturer confirms a physical fault. Read: when a single click becomes two → See the full method → See the open data →
Use a result as a starting point
If an unexpected event repeats, try a fresh browser session and another port or device where practical. Compare the same steps. A result can depend on the browser, operating system, input settings and physical device.
Does this measure hardware latency or polling rate?
No. Browser event delivery is affected by scheduling and input processing. These tools do not certify hardware latency, USB polling rate, DPI accuracy or switch lifespan.
Where do my results go?
The last 30 runs stay in this browser’s local storage. Use the history button to copy a readable report, export JSON or remove them. Raw keyboard and pointer event streams are not sent to a server by this app.