Polling Rate Test
Move the mouse fast inside the box and read the real report rate in Hz -- from the raw pointer reports, not the screen's frame rate.
No permissions. Chrome, Edge, or Firefox for the true rate.
Reports / sec (now)
0
Peak
0 Hz
Looks like
–
Browsers normally deliver one pointer event per screen frame, which is why most "polling rate" pages just show your refresh rate. This one reads the raw coalesced reports underneath, so a 1000 Hz mouse reads ~1000 when you keep it moving continuously. The peak only reaches the true rate while the mouse is in constant motion; pauses drop it.
Frequently Asked Questions
Why do other polling rate tests show 60 or 144 Hz for a 1000 Hz mouse?
Because browsers bundle mouse reports into one event per screen frame, so a page that counts events is really counting frames. This test reads the coalesced reports inside each event, which is the actual stream from the mouse. In Chrome, Edge, and Firefox it reaches the true rate; Safari doesn't expose them, so it falls back to per-frame counting.
The peak is below the rate my mouse is set to.
The mouse only reports while it's moving, so any pause during the second lowers the count. Keep it in continuous fast circles for a few seconds and use the peak. If it still tops out at exactly 500 or 125, the mouse or its software is set to that rate, or it's a wireless mouse in a power-saving mode.
Does polling rate actually matter?
Going from 125 Hz to 1000 Hz cuts the worst-case report delay from 8 ms to 1 ms, which is noticeable in fast aiming. Beyond 1000 Hz the gains are small and some games and CPUs handle 4000-8000 Hz badly, so higher isn't automatically better.