Move your mouse continuously inside the test area to compare browser-observed mouse event cadence. GearCheck Lab reports rolling sample rate, median timing, p95 interval and jitter so you can compare settings, ports or connection modes under repeatable conditions.
Live diagnostic
Mouse movement event cadence and basic buttons
WAITING FOR MOUSE INPUT
MOVE THE MOUSE CONTINUOUSLY · BASIC BUTTON CHECK ONLY
How to run a repeatable mouse polling test
Close busy tabs and keep this window visible.
Move the mouse in broad, smooth circles inside the stage for at least five seconds.
Record the median cadence, p95 interval and jitter after the values settle.
Reset and repeat three times without changing your movement style.
Change only one variable—polling setting, USB port, cable or wireless mode—then repeat in the same browser.
Compare the cluster of runs, not the highest instant number.
How the browser Hz estimate is calculated
The page prefers pointerrawupdate and otherwise uses pointermove, including getCoalescedEvents() samples where available. It derives Hz from the median recent sample interval. P95 highlights slower-tail gaps, while jitter shows how widely accepted intervals vary.
This is a browser event-stream comparison, not a direct USB HID or firmware polling readout. The PASS state confirms usable mouse samples—not that a mouse meets a rated polling specification.
Worked polling-rate interpretations
Three runs near 930–970 Hz with similar p95: the browser is receiving a consistently dense stream. The gap from a 1000 Hz setting is not proof of a hardware fault.
Median near 500 Hz after selecting 1000 Hz: repeat with faster continuous motion, the same browser, and a different USB port before attributing the result to the mouse.
Similar medians but much worse p95 on wireless: the slower tail changed. Check receiver placement, interference and power-saving behavior.
High peak followed by a lower stable median: use the settled median and repeated-run range; an instant peak is not the comparison result.
Troubleshoot low or inconsistent browser Hz
Keep the pointer moving; idle or tiny movements can reduce delivered events.
Repeat in a foreground tab with heavy applications closed.
Compare wired and wireless modes, and place a wireless receiver away from congested hubs.
Try another direct USB port before changing drivers or firmware.
Confirm the selected rate in the mouse vendor software, then retest.
If movement itself skips, use the Full Mouse Test; use switch-specific tools for clicks or holds.
Limits of a browser mouse polling test
A webpage cannot inspect raw USB reports, firmware queues, radio packets, switch actuation, display response or end-to-end input latency. Operating-system scheduling, browser event coalescing, pointer acceleration, CPU load, motion speed, connection mode and device drivers can all affect delivered Pointer Events.
Results are most useful for controlled before/after comparisons on one computer. They should not be used as laboratory certification, warranty evidence or a universal comparison across different browsers and systems.
Basic button check only
Press left, middle and right buttons in the stage. Each counter should increase only for the button pressed, and the highlight should clear on release or interruption.
A mouse configured for 1000 Hz can still produce a lower browser-observed estimate because a webpage does not read the USB HID report stream directly. Compare repeated samples under the same conditions instead of treating one number as firmware certification.
What do median, p95 and jitter mean?
Median is the middle accepted sample interval, p95 is a slower-tail interval, and jitter is the standard deviation of accepted gaps. Together they describe the browser event stream, not the mouse firmware specification.
Can this measure mouse click latency?
No. The browser has no independent timestamp for physical switch actuation or display response, so button counters on this page are only a basic input check.
Can this diagnose double-click faults?
Use the dedicated Double-Click and Chatter Test. This page keeps button counters only as a basic sanity check so polling-rate comparison is not mixed with switch-fault diagnosis.
Does pointer speed affect the result?
Yes. Very small or slow motion may produce fewer movement events. Use continuous, repeatable motion when comparing runs.
Does this test work with a trackpad or touch input?
The sampler accepts mouse Pointer Events only. Trackpads may be exposed as mouse input by the operating system, but touch and pen events are ignored and results still describe browser-delivered events rather than hardware reports.
GEARCHECK LAB