Measure Your Input Lag
Click and measure the time between your input and the visual response. Run multiple rounds to get a reliable average — all processed locally in your browser.
This test measures the software-level delay from a PointerEvent click to the next rendered frame, using performance.now() timestamps to calculate click-to-render latency in milliseconds.
Typical browser input lag ranges from 15–50ms; hardware-level factors (monitor response, USB polling) add additional delay not captured by software timing.
What Do Your Results Mean?
| Result | Range | Meaning |
|---|---|---|
| Good | Under 20ms average | Excellent software-level latency. Combined with a 144Hz+ monitor and 1000Hz polling mouse, total end-to-end lag should be imperceptible for competitive gaming. |
| Warning | 20–50ms average | Acceptable for most use cases. Higher values may come from browser compositor delays, background processes, or V-Sync adding up to one frame of latency. |
| Bad | Over 50ms average | Noticeable lag that impacts gaming performance. Causes include heavy CPU load, compositor latency, power-saving mode throttling GPU, or frame drops from background processes. |
Common Issues and How to Fix Them
Input lag measurements are inconsistent (high variance)
Close other browser tabs and background applications. Garbage collection pauses and compositor scheduling can cause spikes. Run the test in a fullscreen browser window for the most stable results.
Measured lag is much higher than expected
Disable V-Sync in browser settings (chrome://flags → disable V-Sync) to remove frame-sync delay. Also check that your OS is not in power-saving mode, which throttles CPU and GPU frequencies.