Mouse Polling Rate Test: Check Your Hz Live

Mouse Polling Rate Test: Check Your Hz Live

Your mouse reports movement at a polling rate measured in Hz. A 1000 Hz mouse sends 1,000 updates per second, one every 1 ms. A 4000 Hz or 8000 Hz mouse sends reports four or eight times more frequently, narrowing the gap between physical movement and cursor response.¹

This browser-based test uses getCoalescedEvents() to capture intermediate hardware reports that browsers would otherwise coalesce.² Move the mouse inside the tracking zone and read your current Hz, average, and max on the live chart. No download, no account, no data sent anywhere.

What affects your polling rate reading

Three factors determine what this test shows. First, the hardware polling rate your mouse is configured for, set via firmware or companion software. Second, USB controller scheduling: some ports share bandwidth across multiple devices, which introduces jitter. Third, OS power management: USB selective suspend can pause an idle USB device, which can delay reports before the browser receives them.³ Browsers may coalesce multiple pointer updates into one dispatched event, so a reading near 1000 Hz on a 4000 Hz or 8000 Hz mouse often points to browser coalescing or USB power-management delays rather than a hardware fault.²

Understanding which factor limits you changes the fix. If companion software shows 8000 Hz selected but the chart reads near 1000 Hz, browser coalescing or USB power management may be limiting what reaches the page. If both software and chart agree at a lower rate than expected, the polling rate was never changed from the shipped default. A wide-variance chart with peaks and dips rather than a flat ceiling points to USB hub contention; move to a direct rear motherboard port and check whether the reading stabilises.⁴

Choosing the right fix from the chart pattern

A flat ceiling points to a configured-rate or coalescing problem, while a jagged line points to USB contention. Use that distinction before changing software: first confirm the companion setting, then move to a direct port, then check power management. The chart pattern tells you which step is most likely to help. A flat line at 1000 Hz on an 8000 Hz mouse is almost always a coalescing or profile issue rather than a hardware fault, so rechecking the companion software setting and the USB power management policy resolves it before you ever open the mouse or replace a cable.

How to get an accurate reading

Accurate polling rate measurement requires consistent mouse movement. Erratic bursts produce variable intervals between events that lower the average artificially. Move at a steady pace inside the tracking zone and watch the chart stabilise. Plug directly into a rear motherboard USB-A port rather than a hub or front-panel header, which share bandwidth with other devices. Close other applications to reduce OS scheduler load, and disable USB selective suspend in Windows Device Manager if your reading seems lower than expected.

Waiting for the chart to settle matters more than people expect. Letting it run for at least 15 seconds before noting the average gives the sample window enough data to reflect your sustained rate rather than a burst interval. A 5-second test that captures a single acceleration phase shows a different average than a 20-second run at a steady pace; the average converges toward your true polling rate only as samples accumulate. Start moving at a consistent pace and read the value only after the chart line stops visibly shifting.

Reading the chart and interpreting results

The live chart plots the last 600 polling rate samples as a rolling line. A well-configured mouse at 1000 Hz produces a flat line near 1000; at 8000 Hz it produces a similar flat line near 8000. Variance appears as jaggedness; a jagged line on a 1000 Hz mouse usually means USB bandwidth contention. Red vertical lines mark polling dropouts, moments when the gap between two events exceeded 8 ms. Isolated red marks during fast movement are normal event coalescing by the browser. Persistent red marks indicate a real problem: contention, a failing cable, or power management throttling the USB port.⁴

Using variance to choose the next fix

Variance points to the next test. A flat chart at a lower rate usually means the configured polling rate did not reach the browser. A jagged chart near the expected rate usually means USB contention or power management is delaying reports. A few red marks only during fast movement usually means browser coalescing rather than a hardware fault. Tracking the direction of variance over a full 30-second sample distinguishes a consistent USB scheduling problem from random background noise; if the chart stabilizes after the first few seconds, the initial jitter was likely OS scheduling settling in rather than a persistent USB issue.

Separating normal dropouts from hardware problems

Dropouts at slow movement speed are real faults. Fast movement produces brief coalescing bursts in the browser event queue that appear as dropout lines but are not hardware issues. Move the mouse at a deliberate, walking-pace speed and observe whether red marks still appear. Dropouts during that controlled slow movement confirm a genuine issue with the USB port, power management settings, or cable condition; move to a direct rear motherboard USB-A port and retest before drawing conclusions about the mouse hardware.

Repeating the slow-movement check after each change creates a clean decision trail when you are chasing a stubborn dropout. If the red marks vanish after moving to a direct port, the hub was the culprit. If they remain, disable selective suspend and retest, then try a different cable. Walking the fixes one at a time in this order, alongside the click latency view on the main input lag and polling chart, turns guesswork into a short list you can finish in a few minutes.

When to use this

Use this test when your mouse feels laggy or inconsistent, before and after changing USB ports, after a firmware update, or when troubleshooting whether your hardware is delivering its rated polling rate.

Examples