logo

Mouse Double-Click Check

Measure time gaps between clicks and spot suspiciously short intervals that may indicate unintended double clicks.

Clicks

0

Intervals

0

Suspected

0

dblclick events

0

Click Area

Suspect under80 ms

Intervals below this threshold are counted as "suspected" (heuristic).

Click repeatedly in this area. The tool records the gap between consecutive left clicks, up to 500 ms.

No interval yet.

No clicks yet.

Click here

Interval Histogram

No intervals yet

Start clicking to generate the histogram.

Single click triggers double click?

Compare light taps versus firm clicks. If light taps misfire more often, switch wear is likely. Before replacing hardware, also verify your OS double-click speed setting.

If a mouse switch is failing, a single click may register as two clicks within a very short time. This page helps visualize click intervals so you can spot abnormal clusters.
• Counts clicks and records consecutive click intervals. • Histogram to reveal abnormal clusters. • Adjustable "suspect under" threshold. • Tracks native dblclick events. • JSON export for sharing with support.
1) Click repeatedly in the click area. 2) Watch the histogram and the "suspected" count. 3) Adjust the threshold based on your expected click speed. 4) Export JSON to share results.
• Source: click, pointer, and mouse events inside the area. • Interval: time between consecutive left-click activations. • Limit: only intervals up to 500 ms are stored, focusing on unintended rapid doubles. • Results depend on OS click settings and browser event coalescing.
• Diagnose "one click becomes two" in games or file managers. • Compare different debounce settings in mouse software. • Verify behavior after replacing switches or cleaning the mouse. • Provide evidence for RMA or support conversations.
Q: What threshold should I use? A: Start around 60-100 ms. If you click very fast, increase it to avoid false positives. Q: Why do I see intervals but no dblclick events? A: dblclick is a higher-level gesture and depends on OS and browser settings. Q: Is "suspected" always a hardware issue? A: Not always. Software macros, OS settings, accessibility features, or touchpad tap-to-click can also affect clicking. Q: How do I reproduce the issue reliably? A: Click at a normal pace on a single surface. If you can trigger "suspected" events without intentionally double-clicking, it is a stronger signal. Q: Will OS double-click speed affect the results? A: It affects dblclick events, but the raw interval list is independent and always shows the measured gaps. Q: What should I share for support or RMA? A: Export JSON and include your OS, browser, and mouse model or firmware if possible.