A Double Click Test measures the exact millisecond gap between two browser click events, and for this tool that gap must stay under 1,000 milliseconds to count as one pair. The page takes the timestamp the browser assigns to your first click, then subtracts the timestamp of the next click you make inside the one-second window, and rounds the positive result to one decimal place. Each completed pair is stored locally and used to compute your latest interval, your fastest interval, and the simple average across all the pairs you have made in that session. The window is not the official double-click setting of any operating system, and the number is not a hardware score or a label like "fast" or "slow." It is a transparent record of what your browser saw between two clicks, given your mouse, your device, and the moment you tried. Beginners can use it to get a feel for their own click rhythm, compare a few attempts under the same conditions, or sanity-check whether two clicks really did land close together.
What a Double Click Test Actually Measures
A Double Click Test is a small browser page that times the gap between two mouse clicks on a single target. When you click the target, the browser attaches a timestamp to that click event. The page stores the first timestamp, waits for the next click, and checks whether it arrived within the disclosed pairing window — for the Lizely Double Click Test, that window is 1,000 milliseconds, or one full second. If the second click is in time, the page subtracts the first timestamp from the second, requires a positive result, rounds the millisecond difference to one decimal place, and adds the interval to your session history.
The tool is not grading you, scoring your reflexes, or rating your mouse. It is measuring what your browser reported about two click events in a row, on a single large target, in a single session. Everything between you and that timestamp — your hand, the mouse switch, the cable or wireless hop, the operating system scheduler, the browser event pipeline, the display refresh — is bundled into the number. That makes the result a useful comparison tool for the same person on the same device, but a poor absolute measurement of any single piece of the chain, because nothing is isolated.
How to Use the Double Click Test Step by Step
The page is built to be opened and used right away. You do not need to install anything, sign in, or change any mouse setting. The steps below are the full operating procedure.
- Open the Double Click Test and place your pointer comfortably over the large test area in the center of the page.
- Click once. The page records this click as the start of a pair and visually prompts you to click again within one second.
- Click the same area a second time. If the gap between the two click timestamps is under 1,000 milliseconds, the interval is recorded as a completed pair.
- Read the updated Latest number. The page also keeps a running Best (fastest pair so far) and Average (mean of every retained pair, rounded to one decimal place).
- Repeat steps 2 through 4 to build a session. The page keeps at most the latest fifty completed pairs in memory so the statistics always reflect your most recent attempts.
- Click Reset at any time to clear the in-memory history and start a fresh session.
If your second click is more than 1,000 milliseconds late, the page does not silently record it as a slow pair. It shows a timeout message and treats that late click as the first click of a new pair. This non-overlapping rule means the second click of one result is never reused as the first click of the next one, so every displayed interval is easy to reproduce and interpret.
Reading Your Latest, Best, and Average Results
After your first completed pair, the page shows four numbers: Latest, Best, Average, and the number of completed pairs in the current session. The relationship between them is straightforward.
The following table explains each displayed value and where it comes from.
| Display | What it means | How it is calculated |
|---|---|---|
| Latest | The interval from your most recent completed pair. | The millisecond gap between the two most recent click timestamps that landed inside the pairing window. |
| Best | The fastest (smallest) interval you have recorded in this session. | The minimum of every positive interval stored in memory, rounded to one decimal place. |
| Average | The mean of every interval stored in memory. | The arithmetic mean of the retained samples, rounded to one decimal place. |
| Pair count | How many completed pairs the page is averaging over. | The number of positive, non-overlapping intervals stored in memory (capped at 50). |
To see how the statistics fit together, imagine recording three pairs at 245.0 ms, 310.5 ms, and 402.8 ms. The page keeps all three in memory. Best would show 245.0, Latest would show 402.8, and Average would be (245.0 + 310.5 + 402.8) ÷ 3 = 958.3 ÷ 3 ≈ 319.4 ms. Pair count would read 3. As you keep clicking, the oldest samples beyond the 50-pair cap are dropped, so the statistics always summarize your most recent work.
Why the One-Second Pairing Window Matters
The 1,000 millisecond window is a deliberate, visible rule for this tool — not an industry standard and not a reading of any operating system setting. The page openly states that if your second click is more than one second late, it is not saved as a pair, and the page explains what happened instead.
This matters for beginners for two reasons. First, it prevents the page from accepting "double clicks" that no real application or operating system would treat as such. A two-second pause between clicks is usually a deliberate second action, not a fast double, and the tool mirrors that distinction. Second, the rule is forgiving enough to make the test usable on a slow day and strict enough that a genuinely fast double click is unmistakable. Most people who intentionally try to double click land comfortably inside the window.
The page does not label any result as passing, failing, fast, normal, or slow. Different operating systems, different games, and different applications all use different thresholds and different interaction models. A measurement from this page describes one specific thing: the time between two click events as the browser saw them, with everything in the input chain bundled together.
Tips for Getting Reliable Measurements
If you want the numbers to mean something when you compare one session to another, the conditions need to be close. The page measures browser event timing, so anything that changes the gap between two clicks — hand position, mouse surface, device load, background software — will change the number.
A few habits help:
- Rest your hand in the same place for every pair and avoid lifting or sliding the mouse between the two clicks.
- Use the same target, the same browser window, and ideally the same zoom level. Browser zoom does not change the timestamp subtraction, but changing windows or fullscreen modes can shift what the browser is doing in the background.
- Make several deliberate pairs before drawing any conclusion. A single slow pair pulls the average up, and a single rushed pair pulls the minimum down.
- If you are investigating duplicate clicks in a specific program, treat the page as a baseline only and compare the recorded intervals with the behavior in the affected application and the operating system mouse settings.
- Run a comparison session under the same conditions if you suspect a hardware issue. For example, take a session on the old mouse and a session on the new mouse, in the same browser tab, with the same hand position, and compare averages and pair counts.
What the Test Cannot Tell You
Because the page works with browser click timestamps, the interval it shows includes much more than your hand movement. It bundles human reaction, pointing-device firmware, wireless or wired transport, operating-system scheduling, browser event delivery, display timing, and whatever load the device is handling at the moment. None of that is isolated.
The page is also not a calibration tool. It cannot measure USB polling rate, switch debounce, end-to-end click latency, or how an application responds after the click arrives. It does not reveal whether a result will be recognized as a double click by your operating system, a game, or an accessibility tool, because each of those uses its own threshold and behavior. A fast interval on this page does not prove that a desktop setting will recognize the same action as a double click, and a slow interval does not prove the opposite.
Touchscreens and assistive input can also generate click events. A pair on a touch device may represent a tap rather than a physical mouse switch, and assistive tooling may synthesize clicks that look identical to a real click to the browser. The numbers stay honest, but the interpretation depends on what actually produced the events. For a deeper look at how the browser side of this works, see how double clicking works in a browser.
Everything stays in the current page. The intervals are not uploaded, not tied to an account, not saved after refresh, and not used to identify your 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 report transparent latest, minimum, and arithmetic-average statistics without making a hardware or health diagnosis.