Move continuously inside the measurement area. The first movement establishes a timestamp; later pointer intervals form the estimate. A click without movement does not create a polling sample.
Part of the Mouse test. Run the full mouse test first for a complete device check.
The rate stays blank The value jumps between bands The result is lower than a device setting
Mouse Polling Rate Test and Browser Hz Checker
Estimate the browser-observed mouse event rate with a live interval histogram and an explicit uncertainty range.
No permission neededNothing uploaded
Run this test
- Keep the tab visible and focused; move the mouse smoothly inside the sample area for several seconds to start sampling.
- Read browser-observed Hz ± uncertainty and the measured interval count, then press Finish and read result.
- Press Reset counters to repeat the same path and connection; after a focus interruption, press Restart measurement.
Move the mouse continuously inside the sample area to begin.
Also known as: mouse polling rate test, polling rate tester, polling rate checker, mouse polling rate checker, mouse polling rate tester, polling rate test, polling rate mouse, mouse hz test, mouse report rate test. Free, online, and no download required.
01
What the mouse polling rate test checks
| Check | How it is measured | Fails when |
|---|---|---|
| Event interval | Consecutive pointer timestamps produce a bounded interval sample. | Intervals cannot form a stable central estimate. |
| Observed rate | The median interval is converted to events per second. | Too few valid movement intervals arrive. |
| Uncertainty | Median absolute deviation is converted to a plus-or-minus rate range. | The spread is too large for a useful estimate. |
If something failed
Use a longer smooth path, keep the tab foreground and avoid repeatedly reaching the screen edge. Compare the uncertainty and interval count, not only the rounded Hz.
The page receives pointer events after operating-system and browser processing. Repeat under the same connection, then compare one changed setting. A lower browser value does not prove the device missed its configured USB report rate.
02
How to read the result
Polling rate checker results from 125 to 8000 Hz
Mouse polling rate test begins with a smooth movement sample. A polling rate checker in a browser estimates pointer-event frequency. Move for several seconds and read the event count with the displayed Hz and uncertainty. One rounded value is not enough.
Results near familiar 125, 250, 500 or 1000 Hz bands can support a controlled comparison. A browser does not read the device's USB reports directly, so the estimate is not a certificate for those configured rates or for 4000 and 8000 Hz modes. The phrase 8000 hz describes a device setting, not a promise this page can verify.
Is the number jumping? Keep the pointer moving inside the area, leave the tab visible and repeat the same path. Reaching an edge, slowing down or changing direction alters the event stream you give the page.
Why the polling rate tester reads lower than mouse software
The polling rate tester uses pointerrawupdate by default when supported, otherwise pointermove. It expands getCoalescedEvents() samples when available and calculates intervals from each sample's own timeStamp. Without coalesced samples, it uses the event timeStamp.
Mouse software may display a configured report rate, while this mouse hz test calculates the median interval between events delivered to the page. Those are different data sources and should not be expected to match exactly.
Compare repeated ranges using the same movement path, connection and browser. A wide uncertainty band or low interval count means the sample is unstable. Repeat the motion before changing hardware or assuming the advertised setting is wrong.
How to change mouse polling rate
This page cannot change mouse polling rate. Use the device maker's supported settings or system controls for the exact model, then repeat this browser observation under the same movement.
Does wired and wireless differ? Keep the browser, path and duration fixed while changing only the connection. A difference can identify a condition to investigate, but it does not reveal the internal radio or firmware cause.
The related mouse polling rate guide explains the arithmetic between intervals and Hz, plus event coalescing and foreground-state limits. For click-to-paint response use the mouse latency test. For several controls use the mouse test; for missing presses and releases use the mouse button test. These results measure different tasks.
How the mouse polling rate test and browser hz checker works
Only mouse movement from the first accepted pointerId enters this run. Equal or reversed timestamps are discarded without moving the time baseline. The latest 512 intervals form the sample; the median and median absolute deviation provide the rate and uncertainty.
React updates the aggregate at animation-frame pace, but the interval buffer is filled by pointer events. The chart is therefore a summary of received event timing, not a count of screen refreshes.
Sampling mode shows the source actually used: raw + coalesced, pointermove + coalesced, or pointermove. Raw events without coalesced samples are labelled raw. These are browser input samples after system processing, not direct hardware or USB capture.
What the result can establish
A stable repeated range can show how this page receives movement under one setup. Record the connection, browser foreground state, movement and uncertainty alongside the result.
If a setting change moves the repeated range, that supports a relationship under these conditions. It does not prove the exact cause or establish performance in a game.
A low or changing estimate is a reason to repeat the same smooth movement and compare the interval count and uncertainty. The page cannot tell whether the difference came from the mouse, connection, operating system or browser.
Measurement limits
Browser event frequency is not USB report rate. The page cannot inspect the receiver, cable, firmware queue or every raw device report.
Hiding the tab or moving focus away from the browser window interrupts the active run and clears its movement samples. Returning to the page does not resume the old run; click Restart measurement and collect a fresh sample.
Very short intervals approach browser timer and scheduling limits. Treat high-rate estimates cautiously and use model-specific tools when you need device-level verification.
03
Mouse Polling Rate Test and Browser Hz Checker questions
Why does this mouse hz test read lower than my mouse software?
Mouse software may show a configured device report rate. This mouse hz test estimates pointer events received after system and browser processing, including possible coalescing, so the values can differ.
What error range should a polling rate checker report?
Read the Hz together with its uncertainty and interval count. A narrower repeated band is easier to compare; there is no universal error limit that certifies every device.
Can this mouse report rate test resolve 4000 or 8000 Hz mice?
A browser mouse report rate test cannot reliably certify 4000 or 8000 Hz hardware reporting. Timer resolution, event processing and coalescing can dominate such short intervals.
Is 1000 Hz polling enough for gaming?
This page does not decide whether 1000 Hz is enough for gaming. It reports a browser event estimate. Compare the actual game, system load and supported device setting separately.
Does a wireless mouse have a lower polling rate?
A wireless connection can produce a different browser event pattern, but the result does not reveal why. Compare wired and wireless under the same movement, power and foreground conditions.
How do I change my mouse polling rate?
Use the device maker's supported configuration for the exact model. This page cannot change mouse polling rate; it can only repeat a browser-observed comparison afterward.
How should I repeat the mouse polling rate test fairly?
Keep the same browser, visible tab, connection and smooth movement. Run for several seconds, record Hz, uncertainty and count, then repeat before changing one condition.
What can the mouse polling rate test not prove?
The mouse polling rate test cannot read USB reports, certify a configured rate or measure game performance. It estimates movement-event timing delivered to this page.