A SMALL CHECK FOR AN ANNOYING PROBLEM

One press. Or two?

Check whether separate mouse presses arrive unexpectedly close together. A clear timing record, without calling your mouse healthy or broken.

Runs in your browserNo app or device permission

Mouse double-click timing checkReady when you are

Which button are you checking?

Primary button (usually left)Secondary button (usually right)

Choose before your first press. Button mappings may be reversed in your settings.

Press here, slowlyPrimary button (usually left)Release all buttons between presses

Received presses0 / 20 suggested

Gaps below threshold0 of 0 intervals

Shortest observed gap—need two presses

Highlight gaps below 80 ms

20 ms150 ms

A chosen heuristic, not a hardware standard. Adjust before finishing.

Aim for at least 20 separate presses of the selected button. Release all buttons between presses; don’t hold another button. Only mouse-reported presses count, not touch, pen or keyboard. The first accepted press starts recording. Up to 500 received presses per session. In Secondary mode, the menu is suppressed only on the pad while it can record. Firefox may still show its menu if you hold Shift while right-clicking.

Gaps between received presses

In order, left to right

Your timing will appear here.

At or above thresholdBelow 80 msBars cap at 500 ms. Table keeps full values.

Session observations

Primary button · Finish to summarize

Press the pad with a mouse to begin, or view the clearly labeled timing example.

OBSERVATION, NOT A VERDICT

A short gap is a clue. It isn’t a diagnosis.

If you intend to press once, but the browser receives two presses close together, the extra event is worth investigating. This tool highlights gaps under your chosen threshold. It cannot tell whether a switch, driver, software setting or an intentional quick press caused them.

Choose one button, then go slowly

Choose Primary (usually left) or Secondary (usually right) before the first press. Release all buttons each time. The choice locks when sampling starts; Reset clears the history and keeps your choice. Aim for at least 20 received presses, then finish. Twenty is a practical sample target, not proof that a mouse works or fails.

Read the timing, not a score

80 ms is our starting heuristic, not a validated hardware standard. You can adjust it from 20 to 150 ms before finishing. Intervals strictly below the threshold are highlighted; one exactly on it is not. Quick intentional clicks can also be highlighted.

Keep a useful record

A local report contains the selected logical button, received-press count, interval history, threshold and limitations. Copy it or save a text file if useful. A session with no highlighted gaps means none were observed in that sample—not that intermittent problems are ruled out.

What the browser can—and can’t—see

We sample the selected logical button’s pointerdown events only when the browser reports pointerType="mouse". Touch, pen and keyboard activation do not become samples. Trackpads can report as a mouse, so the page cannot identify your physical device. Primary and secondary describe button functions; your settings may reverse their physical positions. Don’t hold another mouse button while testing: pointerdown reports the first button in a button chord, not every later press. MDN explains the event distinction and button mapping.

In Secondary mode, the context menu is suppressed only inside the pad while it can record. Menus elsewhere, in the fictional example and after finishing stay available. Firefox may still open its menu for Shift + right-click; MDN describes this browser exception.

The gaps use the browser event’s timestamp, not a hardware clock. Browser precision settings can round them—even two received presses can have the same timestamp. Background load, operating-system behavior and input software may affect what reaches the page. Read about event timing and reduced precision.

This does not inspect switch contacts, raw USB reports, mouse polling rate or operating-system double-click settings. No extension, native app or device permission is required.

Seeing an extra press you didn’t intend?

Repeat a slow session, then compare with another computer or a different USB port when practical. For a Logitech mouse, its button troubleshooting guide includes steps for a single press producing a double click. Follow your own device manufacturer’s guidance before deciding to replace or repair it.

Timing stays here.

Sampling and analysis run in this browser. We do not upload timestamps, intervals, coordinates or reports, and do not put a session in a link, cookie or browser storage. Refreshing clears it. Copying or downloading the report is your choice.

Optional Google Analytics and Statsig receive controlled tool-action categories and coarse size/duration buckets—not the timing history, coordinates or report contents. For eligible US visits, measurement may be enabled after the first-party country-policy check unless you decline. Elsewhere, including when location is unknown, it stays off unless you allow it. Global Privacy Control and Do Not Track keep it off; Analytics preferences remain available. Providers may receive connection/device information and a browser identifier when measurement is on. Normal hosting requests still happen. Read the full privacy notice.