Browser mouse-event sampler

Ready

Results

Estimated event rate— Hz
Average event rate— Hz
Peak event rate— Hz
Median event interval— ms
Mouse events— events
Active time— seconds
Start, then move your mouse continuously inside this area
Recent browser-delivered mouse event intervals

This is the rate of events delivered to the browser, not a direct read from mouse firmware.

Ready

Browser input event estimate

Mouse Polling Rate Test

Move your mouse continuously inside the active area to estimate how often motion events reach this browser. The result is a browser-observed event rate, not a direct USB or firmware polling readout.

What Is a Mouse Polling Rate Test?

A mouse polling rate test usually asks how frequently a pointing device reports movement. Hardware settings are commonly described in hertz, such as 125, 500, or 1000 Hz. A web page cannot query the mouse controller directly, so this tool measures timestamps on pointer events delivered to the browser and reports an estimated browser-observed mouse event rate.

The distinction is important because the operating system, driver, browser, event coalescing, display cadence, main-thread load, and the way you move can all change delivered events. The value may resemble the configured hardware polling rate under favorable conditions, but it is not proof of firmware configuration or USB bus behavior.

Mouse Polling Rate vs Mouse Event Rate

Hardware polling rate describes communication between device and host at a lower layer. Browser mouse event rate describes how frequently the page receives exposed input updates. The browser may combine several physical reports into one event or provide coalesced sub-events where supported. This test reads those coalesced timestamps when available and keeps the latest 5,000 observations in bounded memory.

Estimated rate is the reciprocal of the median valid interval. Average Hz averages individual reciprocal intervals, while peak Hz shows the fastest observed pair. Peak is sensitive to timestamp quantization and should not be treated as the primary result. Median interval and event count give essential context for the estimate.

How to Get Started

A touch-only device cannot perform a meaningful mouse Hz test; use a connected mouse. Press Start Mouse Test, focus the patterned area, and move in steady circles or long side-to-side sweeps for several seconds. Movement must continue because a stationary mouse sends few or no motion events. Keep the pointer inside the region.

  1. Start the sampler and move continuously with enough distance to avoid repeatedly hitting the area edge.
  2. Continue for five to ten seconds, then read estimated rate, median interval, average, and event count.
  3. Reset and repeat at the same movement style before comparing a driver or mouse setting.

What 125 Hz, 250 Hz, 500 Hz, and 1000 Hz Mean

Theoretical intervals are 8 ms at 125 Hz, 4 ms at 250 Hz, 2 ms at 500 Hz, and 1 ms at 1000 Hz. These are report opportunities, not guarantees that every application processes a unique update at exactly that spacing. Some modern mice support rates above 1000 Hz, which add CPU and USB work and may be harder for a browser page to observe faithfully.

A displayed estimate between standards is normal. Timestamp precision, coalescing, movement speed, and scheduling introduce a distribution rather than one exact interval. Look for a stable median across repeats. Do not round a noisy 760 Hz browser observation to a claim that the mouse hardware is “actually 1000 Hz” without checking its configured software and a lower-level measurement tool.

Why Polling Rate Matters for Gaming

More frequent reports can reduce the maximum wait for a new device update and provide finer temporal sampling of movement. The practical effect is one part of a longer path that includes sensor scanning, USB transfer, operating-system input, game processing, frame production, display refresh, pixel response, and the viewer. Higher polling alone does not guarantee better aim or lower complete system latency.

At very high rates, processing overhead and application support matter. A stable lower setting may behave better than an unstable high one on some systems. Use native game telemetry and vendor documentation for game-specific compatibility. The browser test is most useful as a quick delivered-event comparison under the same desktop conditions.

Why Browser Results May Differ

Browsers can dispatch pointer events aligned with animation, combine movement, expose coalesced events differently, or reduce timer precision. Main-thread congestion delays JavaScript handlers even when hardware reports continue below. Operating-system pointer settings and drivers may alter the path. Slow or tiny hand motion can also produce fewer distinct events than steady movement.

To improve repeatability, use a current desktop browser, close heavy tabs, keep the page foregrounded, move consistently, and collect hundreds of events. Try another browser if the estimate is unexpectedly low. A difference between browsers can reflect delivery policy rather than a changed mouse. Touch and trackpad events should not be interpreted as conventional gaming-mouse polling.

When the Test Helps—and Its Limits

The mouse rate checker can compare two configured rates, confirm that the browser receives frequent movement, reveal severe event-delivery interruptions, or teach the relationship between hertz and milliseconds. It is also useful before a reaction test to make sure pointer input behaves normally in the page. Use the same port, movement pattern, power state, and browser for comparisons.

The tool cannot interrogate firmware, identify the mouse model, validate sensor accuracy, measure click debounce, or isolate USB latency. Average and peak values are influenced by event delivery and timestamp precision. No result proves a mouse is defective. For authoritative hardware polling analysis, use trusted native software designed to read the relevant lower-level input path.