Skip to content
Lizely

Double Click Test

Measure the browser-event interval between two clicks and compare the latest, best, and average result across up to fifty pairs.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Place the pointer over the large test area and click once to start a pair.
  2. 2.Click the same area again within 1,000 milliseconds to record the interval, then repeat for more samples.
  3. 3.Compare latest, best, and average browser-event timings under the same conditions, or reset to clear the session.

About Double Click Test

Double Click Test measures the elapsed browser-event time between two clicks on one large target. The first click starts a pair and the second completes it when it arrives within 1,000 milliseconds. The result shows the latest interval to one decimal place, the fastest recorded pair, the arithmetic average, and the number of completed pairs. Repeat the action to build a small session history, or reset all measurements and begin again.

The pairing rule is deliberately visible and simple. After the first click, the target asks for another click within one second. If more than 1,000 milliseconds pass, the late click is not recorded as a completed pair; it becomes the first click of a new pair and the page explains what happened. Pairs do not overlap, so the second click of one result is never reused as the first click of the next result. This keeps every displayed interval easy to reproduce and interpret.

Timing comes from the click event timestamp supplied by the browser. The tool subtracts the first timestamp from the second, requires a positive increasing result, and rounds the measurement to one decimal place for display and statistics. It keeps at most the latest fifty completed samples so repeated synthetic or accidental input cannot grow page memory without a bound. The average is calculated from the retained samples, while Best is their minimum and Latest is the final value.

The 1,000-millisecond window is a product rule, not an operating-system double-click setting or a scientific classification. The tool does not label a result fast, normal, slow, passing, or failing. Operating systems, applications, games, browsers, accessibility tools, and users can apply different thresholds and interaction models. A measured pair therefore does not prove that a desktop setting will recognize the same action as a double click.

This page also does not isolate hardware latency. The interval includes human movement, pointing-device firmware, wireless or wired transport, operating-system scheduling, browser event delivery, display timing, and whatever load the device is handling. Browser timestamps are useful for comparing attempts in the same environment, but they are not a calibrated measurement of switch debounce, USB polling rate, wireless delay, end-to-end click latency, or application response time.

For a useful comparison, place the pointer comfortably over the target and make several deliberate pairs. Avoid moving between clicks, and keep the same hand position when comparing attempts. If you are investigating unwanted duplicate clicks, compare what this page records with the behavior in the affected application and the operating-system mouse settings. Test another port or device only when it is safe to do so. A browser tool cannot diagnose a failing switch or recommend a repair.

The target is keyboard-focusable for page navigation, but the measurement itself responds to click events. Touchscreens and assistive input can generate click events too, so a result may represent a tap or synthesized activation rather than a physical mouse switch. Browser zoom does not change the timestamp subtraction. High system load, remote desktop software, automation, or background activity can change event delivery and should be noted when comparing sessions.

All samples remain in the current page. They are not uploaded, associated with an account, saved after refresh, or used to identify a device. Reset clears the in-memory state immediately. The reliable contract is narrow: pair two increasing browser click timestamps within the disclosed window, retain up to fifty positive intervals, and calculate transparent latest, minimum, and arithmetic-average statistics without making a hardware or health diagnosis.

Methodology & sources

Treat the first nonnegative finite browser click timestamp as the start of a non-overlapping pair. Require the next timestamp to increase. If its gap exceeds the product-defined 1,000 millisecond window, mark a timeout and use the late click as a new first timestamp. Otherwise round the positive gap to one decimal place, append it to a history bounded at fifty values, and clear the pending first click. Summaries expose the last sample, minimum, arithmetic mean rounded to one decimal place, and retained pair count. Tests assert exact pairing, timeout rollover, invalid timestamp rejection, statistics, and bounded history.

Frequently asked questions

What happens if the second click is more than one second late?
It is not saved as a pair. That click becomes the start of a new pair, and the page shows a timeout message.
Does this reveal my mouse polling rate or hardware latency?
No. It measures the interval between browser click events and cannot isolate firmware, transport, operating-system, display, or human timing.
Is 1,000 milliseconds an official double-click threshold?
No. It is a disclosed pairing rule for this tool. Operating systems and applications can use different settings and behavior.

Related tools

Device & Productivity guides

View all