Mouse Polling Rate Test
Estimate browser-observed mouse event frequency while you move continuously inside the test area.
How to use this test
Move the mouse continuously inside the field using smooth circles or long sweeps. Wait for the graph and sample count to settle before reading the average and median Hz values.
How the measurement works
Pointer event timestamps are collected in a rolling window, obvious pauses are filtered out, and the remaining intervals are converted into browser-observed polling frequency.
How to interpret results
Median Hz is the best quick estimate, average Hz shows the rolling sample, peak Hz can reveal bursts and stability indicates how tightly the samples cluster.
Troubleshooting tips
Use a focused foreground tab, avoid tiny movements that trigger acceleration pauses and retest with raw-input or browser settings changed only one at a time.
Related tests
You can also browse every utility from the complete tool index.
Common polling rate questions
Is 500 Hz or 1000 Hz mouse polling better?
1000 Hz can report pointer updates more frequently than 500 Hz, but the practical benefit depends on the game, display refresh rate, CPU load and input pipeline. A stable 500 Hz can feel better than an unstable higher setting.
Read full answer →Why does my 1000 Hz mouse show less than 1000 Hz?
Browser event coalescing, USB scheduling, tiny pointer movements, power saving and system load can reduce the observed event rate. Use large continuous movements and compare several runs before treating the result as a hardware problem.
Read full answer →Can a browser accurately test 4000 Hz or 8000 Hz mice?
A browser can estimate very high event cadence, but it is not a direct USB hardware analyzer. At 4000–8000 Hz, event coalescing and scheduling make browser-observed results more sensitive to system and browser behavior.
Read full answer →Why can a 1000 Hz mouse show less than 1000 Hz?
Browser event coalescing, USB scheduling, operating-system load, drivers and pointer movement quality can lower the browser-observed rate even when the device is configured for 1000 Hz.
Read full answer →