Last updated
Run a mouse polling rate test
First use the mouse button test if movement works and only one click is missing. Here you are checking the cadence of movement updates. Put the pointer inside the test area and move it in broad circles for a few seconds. Build up to a comfortable, steady pace. Keep moving until the average settles and the peak has a value. Move the pointer outside the area to keep the last reading on screen.
For a before-and-after comparison, set the rate in the vendor app, confirm the active profile, and reset the test between passes. Keep the browser, connection mode, and movement pattern as similar as you can. The polling rate saved for USB may differ from the one saved for wireless. Some devices apply a new profile only after you switch to it or reconnect the mouse. When testing the receiver, verify the mouse is actually using it and has not switched to Bluetooth.
Read average, peak, and stability
Average is calculated from the recent gaps between usable movement samples. For example, a hundred samples spaced about two milliseconds apart produce a reading around 500 Hz. The calculation divides one second by the mean gap. Averaging the inverse of each gap separately would let a few very short gaps skew the result upward.
Peak uses the fastest block spanning at least 100 milliseconds of accepted gaps. It can show a short stretch where the rate improved. Peak can remain blank until the test has accumulated a full block. Stability measures how many gaps sit within 25 percent of the mean gap, giving you a way to compare a smooth sequence with one that alternates between very short and very long gaps.
Read the three numbers together. A smooth trace around 125 Hz and a high stability score indicate a consistent visible cadence. A trace whose average lands near the advertised rate but regularly jumps between two plateaus is worth another pass. Move the pointer continuously, too. Small, slow motions can produce fewer distinct movements even when the mouse is ready to report much more frequently.
What the browser can measure
A mouse can send an update even when its position has barely changed. The browser receives input after the device, connection, operating system, and browser input pipeline have processed it. The site listens for mouse pointermove events and uses their timestamps. When a dispatched event contains coalesced movement samples, the tool reads their timestamps instead of counting the dispatch as one sample. Otherwise it uses the timestamp of the event itself. The method cannot see reports that were dropped or merged upstream. W3C Pointer Events specification
The display uses requestAnimationFrame to paint the chart and updates no more than about ten times a second. No frame timestamps go into the rate calculation. Browser event delivery can still line up with animation frames, especially when the underlying samples are unavailable. A trace near 60 Hz or 120 Hz can reflect that delivery pattern. Browser versions and privacy settings vary, so compare within the same setup. Firefox can expose a different timestamp resolution, and Safari versions that lack the coalesced API can give a more limited view.
Pauses longer than 100 ms and identical timestamps are excluded. During motion the calculations use about two seconds of recent samples. When you stop, the last reading stays visible so you can write it down. A long pause between runs resets the interval baseline. It does not add a zero-Hz sample, since the tool cannot tell whether a stationary device sent reports during that pause.
Rate and interval reference
These are nominal intervals if reports are evenly spaced. They are arithmetic conversions, useful for spotting approximate steps between modes. The numbers do not promise that a web browser can observe every report.
| Nominal rate | Time between reports |
|---|---|
| 125 Hz | 8 ms |
| 250 Hz | 4 ms |
| 500 Hz | 2 ms |
| 1,000 Hz | 1 ms |
| 2,000 Hz | 0.5 ms |
| 4,000 Hz | 0.25 ms |
| 8,000 Hz | 0.125 ms |
Above 1,000 Hz, the expected gaps get very small. A little rounding or batching can combine multiple real reports into one visible timestamp. If a mouse has 4,000 Hz and 8,000 Hz settings, the browser might display almost the same number for both. Use a native utility that reads device report timing when you need to distinguish those modes or verify a hardware claim.
Troubleshoot a low or uneven reading
The result is stuck far below the advertised number. Check the rate in the active profile rather than the maximum printed on the box. A Bluetooth mode can have a different rate from a dedicated USB receiver. Try a direct port and confirm the correct connection before comparing the numbers. Use the same browser and the same display when you swap ports to reduce other changes.
The average falls when you move slowly. Run a broad continuous pass, then repeat with faster movement. Sparse position changes can make the browser supply fewer distinct timestamps. Very low DPI at crawl speed may make this effect easier to see. If you changed the sensitivity profile between trials, the DPI tester can help verify that you selected the movement setting you intended.
The trace changes when you open another app. Close a video, screen recorder, or heavy background task and run the same motion again. Try a fresh browser tab with the test visible. Other work can delay the browser or cause delivery in batches. A comparison on a second desktop browser is useful, especially when the first result hugs the display’s refresh rate.
Input feels uneven even though the reading looks steady. Try the same mouse and connection in the application where you notice it. Frame pacing, application rendering, and wireless interruptions can affect what you see and feel. This page captures input timestamps during a movement pass. It cannot tell when a frame finally reaches the monitor. A native report log and the application’s frame-time display answer different parts of the problem.
Write down the model, active rate, DPI, connection type, operating system, browser version, and what you did with the mouse. Take two or three readings at each setting. If the browser consistently shows an increase when you change from 125 Hz to 500 Hz, that supports the conclusion that the profile changed. A single high peak provides less evidence than an average and trace you can reproduce.
USB, wireless, and power-saving modes
A rate you can reproduce on one connection is more useful than a single high peak on another. If the mouse offers a USB cable, a 2.4 GHz receiver, and Bluetooth, test each mode separately and reset the page between them. When you can, plug the receiver into a rear port on the computer and keep it away from USB 3 devices and metal enclosures that can add interference. A flaky front-panel header or an unpowered hub can also thin out the updates the computer receives, even when the mouse profile still shows a high rate.
Many wireless mice lower their report rate when the battery is low or when a long-life profile is active. Charge the mouse, turn off any endurance mode in the vendor app, and confirm the same profile is still selected after a reconnect. If the average rises after those steps, the earlier reading was probably limited by power or profile state rather than by this page.
If two desktop browsers agree within a few percent, treat that as the cadence this computer can show. If they disagree by a wide margin, record both browsers with the same motion and prefer the higher average only after you can repeat it. This page remains a check of what the browser observed, not a substitute for a native report log when you need to certify a high-rate marketing claim.
Frequently asked questions
Does mouse Hz mean the same thing as monitor Hz?
Mouse Hz refers to the cadence of input reports or observed movement updates. Monitor Hz describes display refreshes. A browser may deliver movement callbacks around display frames, so the two numbers can appear related during a test.
Why does my 1,000 Hz mouse show less than 1,000 Hz?
Check the active profile, test while moving continuously, and try the intended USB or receiver connection. Browser batching and sparse motion can also reduce the number of visible samples even when the mouse is set correctly.
Can this test separate 4,000 Hz from 8,000 Hz?
Use the browser reading for rough comparisons. It may merge samples or round timestamps enough that those modes overlap. Use a native report-timing tool when you need to distinguish high rates reliably.
What counts as a stable reading?
The stability score is the percentage of accepted gaps within 25% of the mean gap. Compare that percentage with average Hz and the live trace. A steady browser cadence can still be lower than the hardware setting.
What does Peak mean here?
Peak is the fastest observed rate over a full block of at least 100 ms of accepted movement gaps in the recent window. A single unusually short timestamp gap does not set it.
Can I measure click latency with this page?
The tool measures the timing of browser movement samples. Measuring click latency requires aligning a physical action with a device or application response using a separate timing reference.