"> Click Delay & Input Lag Test — Measure Latency

Click Delay Input Lag Test

Measure the delay between clicking your mouse button and the event registering in the browser.

Time between physical click and the corresponding browser mouse event in milliseconds. Click Start Test and click the button as quickly as possible when prompted.

♢ Runs in your browserNo installationResults can be affected by browser and system conditions
◴

What does this test measure?

Time between physical click and the corresponding browser mouse event in milliseconds.

☆

Why is this test important?

Measure the delay between clicking your mouse button and the event registering in the browser.

▻

How do you run the test?

Click Start Test and click the button as quickly as possible when prompted.

▥

How should results be interpreted?

Under 10 ms is excellent; above 30 ms is noticeable in fast-paced gaming.

☑

Normal and problematic results

Under 10 ms is excellent; above 30 ms is noticeable in fast-paced gaming.

△

Technical limitations

Results include browser processing overhead which cannot be separated from hardware lag.

↘

Why can the score decrease?

Unstable measurements, denied permissions, unsupported browser APIs, background load, power saving, or an incomplete test can affect the result. When a score changes, the result screen explains the reason.

⌕

What should you do if a problem is found?

Update mouse firmware, reduce USB polling latency, or try a wired connection.

Example Result Explanation

✓ GoodA stable, repeatable result in the expected range. A clear and consistent experience is expected.
△ AttentionSome indicators should be checked again. Reduce background activity and repeat the test under the same conditions.
× ProblemA repeated clear failure or instability means the relevant setting, connection, or device needs closer review.

Frequently Asked Questions

Does this test provide a definitive hardware diagnosis?

No. The test measures signals the browser can safely access and clearly explains its technical limits.

Why can results change between runs?

Background applications, power mode, network conditions, permissions, and operating-system timing can affect results.

How should I repeat the test if I see a problem?

Repeat it on the same device and browser while changing only one condition, so the source of the difference is easier to identify.