Current latency
— ms
Average —
Min
—
Max
—
Click here to measure latency
Mouse click latency test
Measure browser render latency — the time from your click to the pad flashing on screen. Read current ms, min, max, average, and a scrollable per-click log.
Online mouse latency test — browser render latency log
Browser render latency is the delay from your click to visual feedback on screen. On a 60 Hz monitor one frame is ~16.7 ms — results cluster around VSync boundaries. This instrument logs every sample so you can compare browsers, system load, and connections with data, not guesswork.
Browser render latency
Time from pointer down to the next requestAnimationFrame paint. This is what the pad measures — typically 0–16 ms on a 60 Hz display.
System scheduling
Windows and macOS batch work — background CPU load can add brief spikes even on fast mice.
Display path
A 60 Hz monitor adds up to ~16.7 ms before you see the result — not measured here but part of real gameplay lag.
Wireless RF
Bluetooth and crowded 2.4 GHz environments raise averages. Retest with the dongle on an extension cable away from the PC chassis.
When to use this test
Wired vs wireless
Log 20–50 clicks on each connection and compare average ms — spikes hint at RF or USB issues.
Before/after driver tweaks
Retest after changing polling rate or debounce in your mouse app to see if averages shift.
Bluetooth sanity check
Bluetooth mice often show higher averages and occasional spikes — this test surfaces that pattern quickly.
How to run the latency test
Click steadily, collect 30+ samples, then read average and max — not just one click.
-
Close heavy background apps
Streaming, downloads, and browser extensions can inflate spikes. Retest on a quiet system for baseline numbers.
Use the same browser profile you game with if comparing tweaks.
-
Click the pad repeatedly
One click = one log row. Wait for the pad flash to reset before the next click — rapid spam is ignored until the cycle completes.
30–50 samples smooth out VSync alignment variance.
-
Compare connections
Reset between wired, dongle, and Bluetooth runs. Note average and worst max, not single lucky clicks.
Log screenshots when sharing results — timestamps help spot patterns.
Reduce input latency
-
Set mouse polling to maximum (1000 Hz+) in vendor software.
-
Use wired or low-latency 2.4 GHz wireless for competitive play.
-
Disable V-Sync in games; prefer G-Sync/FreeSync within refresh range.
-
Use fullscreen or borderless fullscreen to avoid extra compositor delay.
Mouse click latency test FAQs
What does this mouse latency test measure?
Each click measures browser render latency — the time from pointer down to the next screen paint when the pad flashes. This uses requestAnimationFrame to align with your monitor refresh. It does not measure USB polling delay, switch debounce, or full end-to-end display lag (pixel response time).
What latency is considered good?
Under 8 ms average is excellent — your click landed just before a VSync and painted almost instantly. Under 16 ms is good (within one 60 Hz frame). Sustained averages above 16 ms mean the browser missed a frame or your system is under load.
Why do individual clicks vary?
Monitor refresh alignment is the biggest factor — clicking right after a VSync can add up to ~16 ms before the next paint. OS scheduling, background tabs, and wireless jitter add smaller variance. Focus on average over 30+ clicks.
Is this the same as internet latency?
No. Network latency measures packet round-trip time. This test is local input latency from your mouse through the browser event queue.
Does polling rate affect click latency?
Higher polling (1000 Hz) reduces the average wait for the next position report, which can shave milliseconds from perceived responsiveness. Pair 1000 Hz with a high refresh monitor for the full benefit.
Can I test keyboard latency here?
This pad measures mouse clicks only. Keyboard latency tests need key-down timing — use our keyboard test for key response, or dedicated keyboard latency tools for HID timing.
