FREE BROWSER TOOLS

Double-click test

Look for unintended extra clicks with a controlled, slow-click check. The tool shows the interval between left-button presses; it does not automatically diagnose a faulty switch.

Double-click testLOCAL TO THIS TAB
Click here ↖Slow, deliberate input gives the clearest comparison.
—Left presses
—Short intervals
—Minimum interval (ms)

Ready. Follow the steps to begin.

Intervals between left presses

ACTUAL EVENTS

No observations yet.

One physical press, more than one recorded click?

Make 20 deliberate single presses about a second apart. Compare your physical count with received presses before interpreting short intervals. A speed record answers a different question.

KEEP A USEFUL BASELINE

Give this observation some context.

Save an explicit snapshot, then change one condition and repeat. Up to 20 reports stay in this browser only.

Compare saved reports →

Nothing is saved automatically. Download JSON also works without local storage.

How to use this test

  1. Reset the counters. Click the target once, then wait about a second before clicking again.
  2. Repeat 20 deliberate single clicks. Compare the number of physical presses with the recorded count.
  3. Inspect “Short intervals” and the minimum interval. The default 150 ms threshold is a viewing aid, not an industry fault limit.
  4. Repeat with another port or connection. Use a different mouse as a control and download the report if you need to compare sessions.

Read the observations

A short interval means that two left-button pointer-down events reached this page close together. Intentional rapid clicking also creates short intervals, so this is meaningful only when you are deliberately making separated single presses. Adjusting the threshold reclassifies the existing intervals without changing the observations. A missing first interval is normal: one click has no previous click to compare with. The JSON report includes the intervals in milliseconds.

What this test cannot tell you

There is no universal millisecond boundary that proves switch chatter in a browser. OS timing, accessibility settings, remapping software and device firmware can affect events. This tool records presses, not your intent or the switch voltage. Do not change mouse firmware debounce settings based solely on this number.

Need a closer comparison? Mouse double-clicking: build a controlled comparison.

Questions about the test

What threshold should I use?

Start with 150 ms and keep physical presses roughly one second apart. Treat the threshold as a filter, and compare the raw count with your deliberate presses.

Is a short interval always a fault?

No. It can be an intentional double-click. Only a controlled comparison can help distinguish unexpected extra events.

Technical references

Method version 2.0 · Page updated 2026-10-20