Mouse Double Click Test
Test a mouse for unintended double clicks with slow single-click screening or intentional pair timing. Choose a button, inspect browser click intervals, and compare local runs.
- Browser-observed
- No device permission
- Optional history in this browser
- No account or upload
Important
- Short browser-observed repeat intervals are screening evidence, not proof of switch bounce or hardware failure. Fast intentional input, remapping/software, connection behavior, and browser delivery can produce similar patterns.
Make deliberate single clicks, one physical press/release at a time, with a clear pause between intended clicks. Shorter windows flag only very close browser-observed repeats; 80 ms is a screening boundary, not a hardware specification.
Ready — press Start before clicking
The main screen looks for unusually close adjacent completed presses of the selected button. This is not a click-speed game or CPS score.
0 completed mouse presses
Unintended-repeat screening results
- Session
- Ready
- Selected button
- Primary / Left
- Completed mouse presses
- 0
- Valid adjacent intervals
- 0
- Possible repeat intervals
- 0
- Flagged interval ratio
- 0
- Minimum interval
- —
- Median interval
- —
- P95 interval
- —
- Latest interval
- —
- Incomplete presses excluded
- 0
- Non-mouse presses excluded
- 0
≤ 80 ms
Recent adjacent press intervals
—
Click interval = time between the browser-observed pointerdown timestamps of two completed presses for the same selected button. Pointer Events occur after the switch, mouse firmware, connection/reporting, operating system, and browser delivery; this page cannot inspect switch contact bounce, firmware debounce, USB/HID packets, or electrical state.
A short interval can reflect an unintended repeat, deliberate fast input, remapping or macros, connection/reporting behavior, or browser scheduling. Possible repeat ≠ switch fault proven; no possible repeats ≠ mouse health certified. The native dblclick event is not used because it cannot reveal intent.
Local history (aggregate only)
Stopped valid runs store only an aggregate summary in this browser. Raw click intervals, the pointer timeline, coordinates, and event sequences are not persisted or sent to analytics. Interrupted and empty runs are not saved.
No local history yet. Stop a meaningful run to save an aggregate summary.
Accepted empty or unknown pointer types are shown with an unknown-pointer caveat; touch and pen are always excluded. Back/Forward roles (3/4) can be intercepted or remapped by the browser, OS, or vendor software, so missing side-button evidence is not a hardware verdict.
How to use
- Choose Unintended repeat check or Intentional pair timing, then select the logical mouse button you want to test.
- For Unintended repeat check, choose a 40, 80, or 120 ms possible-repeat window. Make deliberate single press/release clicks with a clear pause between intended clicks.
- For Intentional pair timing, choose a 200, 300, or 500 ms pair window. Make deliberate two-click pairs and pause before the next pair.
- Press Start and keep the pointer inside the focused test surface. Only completed mouse press cycles for the selected button enter the main result.
- Stop to freeze the run. Repeat unusual results with the same button, mode, window, mouse, connection, browser, and similar protocol; compare aggregate local history rather than treating one short interval as a diagnosis.
What the result means
- A completed mouse press requires a browser-observed pointerdown followed by its matching pointerup for the selected logical button.
- Click interval is the time between the pointerdown timestamps of two completed presses for that button. Possible-repeat screening asks whether adjacent intervals fall within the selected DeviceMetrik window.
- Intentional pair timing uses non-overlapping pairs (1–2, 3–4, 5–6). Within pair window and outside pair window describe timing, not successful or failed hardware.
- Touch and pen presses are excluded from mouse analysis. Back/Forward buttons can be intercepted or remapped before a page event reaches the browser.
Limitations
- Possible-repeat windows are DeviceMetrik screening boundaries, not manufacturer specifications, switch debounce settings, universal failure thresholds, or proof of physical bounce.
- The pair timing window is a DeviceMetrik practice/comparison setting. This page does not read or reproduce the operating system's exact double-click preference.
- Browser Pointer Events occur after switch, firmware, connection/reporting, operating system, and browser delivery. This page cannot inspect switch contacts, firmware debounce, USB/HID packets, or electrical state.
- Possible repeat does not prove a switch fault, and no possible repeats do not certify mouse health. Trackpads may surface as mouse-like browser input, and pointerType does not identify the exact physical device.
- Current pointer analysis stays in the browser; raw timeline and intervals are current-session only, while Local history stores aggregate summaries. Raw click sequences and coordinates are not persisted or sent to analytics.
Troubleshooting
- Normal single clicks keep getting flagged
- Make clearly separated single press/release clicks. If you intentionally click quickly, increase the pause or choose a shorter screening window before interpreting the pattern.
- My intentional double-clicks fall outside the pair window
- Treat the window as a practice/comparison setting, not your OS double-click preference. Repeat consistent two-click pairs and compare the interval distribution.
- Right click opens a context menu
- Press Start and click inside the active test surface, where the running session suppresses the context menu.
- Back/Forward buttons leave the page or do not register
- Browser navigation, OS settings, or vendor software may intercept button 3/4. Test a standard button first and do not treat missing side-button evidence as hardware proof.
- The run was interrupted
- Focus loss or page hiding invalidates the run for Local history. Start a fresh session.
Related tools
FAQ
What does this mouse double-click test actually measure?
Browser-observed completed mouse press cycles and intervals for one selected logical button.
Does a very short interval prove switch bounce?
No. It is screening evidence only; fast intentional input, remapping, connection/reporting behavior, and browser scheduling can produce similar intervals.
Why are unintended-repeat and intentional-pair modes separate?
One asks whether extra very-close presses appear during deliberate single-click testing; the other measures deliberate two-click timing.
Does this use the browser's native dblclick event?
No. Native dblclick confirms that the browser recognized a rapid two-click activation but cannot reveal user intent. DeviceMetrik uses controlled completed-press interval analysis.
Is the pair window my operating-system double-click setting?
No. It is a DeviceMetrik run setting and the page does not read the exact OS configuration.
Which mouse test should I use?
Use this page for repeated-click interval analysis; use Mouse Test for broad button coverage, Scroll Wheel Test for wheel diagnostics, Mouse DPI Test for a browser DPI estimate, and Mouse Polling Rate Test for browser movement-event timing/rate.