Mouse Click Test
Compare deliberate clicks, close intervals, and browser double-click events.
Choose a button and intended count. Make deliberate press-and-release clicks in the test area, then compare detected clicks with your own count. Pause briefly between clicks; no speed score is used.
Both press and release must be inside this area.
0detected · intended 10
- Close intervals to review
- 0
- Browser double-click events
- 0
- Last interval
- Not available yet
Intervals below 50 ms are marked for review, including rounded zero values. Intentional fast clicks, event timing precision, and OS settings can cause these too. They do not prove a defective switch. Double-click events are a separate browser summary and never add to the click count.
Recent click intervals (last 20)
No completed clicks yet.
On a touchscreen, use an attached physical mouse. Touch or keyboard activation is not counted as a mouse switch check.
How to use this test
- Choose the physical mouse button and an intended count, then reset before a new comparison.
- Make deliberate press-and-release clicks with both parts inside the test area; keep your own count.
- Compare detected clicks, close intervals, and the separate double-click summary. Recheck a mismatch without treating one session as a switch diagnosis.
What the result means
Make a controlled number of deliberate clicks with the selected button, keeping both press and release inside the area. Compare the completed event-pair count with your own intended count. A second completed click less than 50 ms after the previous release is marked as a close interval to review. Native double-click events are reported separately; they never increment the completed-click count again.
Know the limitations
The 50 ms threshold is a conservative review cue, not a validated switch-debounce limit or fault detector. Intentional fast clicks, timestamp rounding, OS double-click settings, and device/browser behavior can affect results. The browser cannot know how many physical clicks you attempted, so missing events require your own comparison. One session cannot establish a defective switch; there is no CPS score or hardware latency claim.
If counts or intervals look unexpected
An outside release is deliberately excluded. Changing the selected button resets observations. Fast intentional clicks or timestamp rounding may produce close intervals, and OS settings affect double-click summaries. The page cannot know how many physical clicks were attempted. Confirm the general button mapping if the selected button does not respond.
Common questions
Does a close interval mean the switch is defective?
No. It only describes closely spaced browser events. Intentional double clicks, timing precision, and settings can produce the same observation. Repeat deliberate clicks and compare your own count before consulting the manufacturer about a persistent concern.
Why is the double-click count different from completed clicks?
The browser can emit a double-click summary after two primary clicks according to its own settings. We keep that summary separate so those two completed clicks are not counted a third time. Other buttons may not emit that summary.