Why use this tool?
- Measure repeated click-to-browser frame response without drivers or downloads.
- Reveal typical click delay, slow outliers, and run-to-run variation.
- Compare wired, wireless, and Bluetooth mice under controlled browser conditions.
Mouse Latency Test
See every mouse click and plot button event-to-frame latency on a live line graph, with median, average, fastest, slowest, P95, and consistency results.
Timing samples stay in this browser tab
This is a browser event-to-next-frame estimate, not a laboratory measurement of total hardware input lag. Use it for controlled comparisons on the same computer, display, and browser.
Click-to-frame test
Collect at least 20 samples for a useful comparison. Up to 100 recent samples are retained.
Recent mouse clicks
Newest firstMouse clicks will appear here.
Waiting for samples
Use the test area above to begin.
Latency results
All figures describe DOM input-event to next animation-frame timing in this page.
- Samples
- 0
- Latest
- —
- Median
- —
- Average
- —
- Fastest
- —
- Slowest
- —
- P95
- —
- Consistency
- —
Maximum 100 recent samples
Button: —
Best typical-response comparison
Mean of all retained samples
Lowest observed sample
Highest observed sample
95% of samples are this fast or faster
Standard deviation; lower is steadier
Latency over recent inputs
Each point is one measured mouse click.
The latency line graph will appear after your first input.
Complete tool guide
Mouse Latency Test guide
Use this online mouse latency test to estimate how long the current browser takes to carry a mouse-button press into the next painted frame, with median, average, 95th-percentile, range, and consistency results.
Your input is processed in the current browser tab and is not sent to the application server.
Common use cases
- Comparing mouse connections or USB ports on the same computer
- Checking browser responsiveness before a timing-sensitive game
- Diagnosing latency spikes caused by load, extensions, or power saving
How to use it
- 1
Click the large mouse target repeatedly at a steady pace.
- 2
Collect at least 20 samples without dragging or holding the button.
- 3
Review median response, P95 outliers, and consistency.
- 4
Reset, change one condition, and repeat with the same display and browser.
Controls and results explained
Mouse latency target
A pointer-down inside the target starts a sample immediately; it does not wait for the later click event. Left, middle, right, back, and forward buttons can all produce samples when the browser exposes them.
Latest sample
The newest pointer-event-to-next-frame estimate. Individual values depend on when the press lands within the display refresh cycle, so use a group of samples.
Median and average
Median represents the typical result with less influence from spikes. Average includes all samples and helps show the overall cost of intermittent delays.
Fastest and slowest
The observed endpoints show the spread of this run. They include browser scheduling and should not be treated as the mouse manufacturer’s hardware specification.
P95 latency
P95 describes the slower edge of normal behavior: roughly 95% of samples are at or below it. A high P95 with a low median indicates occasional stutter.
Consistency
Standard deviation summarizes how tightly the click samples cluster. Lower is steadier and usually feels more predictable in timing-sensitive interactions.
Recent click history
Each recorded mouse button appears with its measured delay, letting you match left, middle, right, back, or forward presses to individual graph points.
Latency line graph
The line plots clicks from oldest to newest with a point for each sample and a dashed median reference. A flat line indicates steadier browser response; peaks are slow frames.
Reset samples
Clears the run before comparing another USB port, polling-rate setting, wireless receiver position, browser, or system power profile.
What is measured
The estimate compares the browser pointerdown timestamp with the next requestAnimationFrame callback, approximating event-to-next-paint delay in this page.
What is not measured
It cannot isolate switch debounce, sensor polling, USB or radio transport, operating-system processing, display scanout, or pixel response. External equipment is needed for full click-to-photon latency.
Polling and refresh rates
Higher mouse polling can reduce when an event becomes available, while a higher-refresh display shortens the wait for the next frame. Browser scheduling can still dominate a sample.
Practical tips for better results
- Use 20–30 or more clicks and compare the median and P95 with equal sample counts.
- Keep the receiver close, use a charged battery, and avoid a congested wireless connection.
- Close busy tabs and disable power saving before comparing devices.
- Do not compare results collected on different display refresh rates as if they were equivalent.
Frequently asked questions
Does this measure true mouse click latency?
No. It estimates pointer-event-to-next-frame delay inside the browser. Measuring complete physical click-to-photon latency requires a controlled external sensor or high-speed camera setup.
Can this verify a 1000 Hz polling rate?
No. This test records button events and browser frames, not raw USB reports. Use a dedicated raw-input polling test when polling-rate certification is the goal.
Why is P95 much higher than the median?
The system likely produced occasional slow frames. Close background work and extensions, keep the tab focused, and repeat to see whether those spikes persist.
Is any click information uploaded?
No. Temporary timing samples and the latest button label stay in this browser tab and disappear when you reset, refresh, or leave.
Keep working
Related device & browser tests
Continue with another focused tool from the same collection.
Keyboard TestTest every keyboard key on a visual layout, find dead or repeating keys, and inspect keydown, keyup, code, and modifier events.Keyboard Latency TestSee each key press and graph key-event-to-frame latency with median, average, fastest, slowest, P95, and consistency results.Mouse TestTest five mouse buttons, wheel directions, cursor movement, report rate, and double-click timing, including possible switch bounce.Touchscreen TestDraw across a touchscreen to find dead zones or ghost touches and check multi-touch contacts, pressure, contact size, and pointer type.