Select the input type
Choose Mouse for pointer movement or Controller for Gamepad API timestamps.
Measure the movement update rate your browser can observe from a mouse or controller. Compare event delivery, timing consistency and short dips with live charts and repeatable timed sessions.
Choose your device and collection method. Results describe browser-observed events or controller state updates, not direct USB or wireless hardware reports.
Choose Start Test and move your mouse continuously.
Half-second rate windows; input must be moving. Gaps may reflect user movement, browser coalescing or scheduling.
Run a test to see a measurement-specific interpretation.
A 1000Hz hardware device can produce far fewer JavaScript callbacks. A mouseevent is not guaranteed to represent one device poll.
| Nominal rate | Interval |
|---|---|
| 125 Hz | 8 ms |
| 250 Hz | 4 ms |
| 500 Hz | 2 ms |
| 1000 Hz | 1 ms |
| 4000 Hz | 0.25 ms |
| 8000 Hz | 0.125 ms |
These are mathematical reference intervals, not targets confirmed by the page.
Repeat measurements using the same motion and settings. Compare observed rates, timing variability and the collection method.
| Run | Device / method | Avg Hz | Peak Hz | Median gap | Samples | Status |
|---|---|---|---|---|---|---|
| No tests completed. | ||||||
Session data stays in this tab unless you export it.
Choose Mouse for pointer movement or Controller for Gamepad API timestamps.
Use continuous brisk mouse movement, or rotate an analog stick throughout controller sampling.
Don't change tabs, minimize the browser or stop movement during the session.
Review average, peak, median gap, jitter and consistency before interpreting a result.
Place your mouse on a large, consistent surface and move it continuously across the test pad. Choose Automatic for the broadest supported event path, or compare pointermove and mousemove results.
For high-rate mice, browser callback frequency can be substantially lower than physical device polling.
Press a controller button to make it visible to the browser, choose Controller mode and rotate a stick continuously during the test. The tool records changes to Gamepad API timestamps, not the actual USB or wireless transmission schedule.
Controller sampling may be limited by animation-frame cadence, firmware behaviour and browser mapping.
The tool counts browser-visible mouse movement events. Browsers may align pointermove with display frames or combine multiple input updates.
pointerrawupdate may expose more frequent movement data on supported HTTPS browsers. It is not universally available or identical to raw USB traffic.
Where exposed, merged pointer events can contain additional samples. These are reported separately from JavaScript callback counts.
Controller mode observes distinct Gamepad API timestamps on animation frames. It cannot read every hardware report between browser frames.
The interquartile range of observed time gaps describes spread, not guaranteed firmware or radio jitter.
Nominal 125/250/500/1000/4000/8000 Hz values specify report intervals. An online test cannot certify the actual device setting.
A browser may combine movement into fewer dispatched events. Try raw pointer events if supported.
Slow or stationary movement produces too few samples. Re-run with steady motion over the testing area.
Gamepad state is observed inside requestAnimationFrame. A displayed 60โ144 Hz is not proof the controller runs at that native report rate.
Busy browser tabs, operating-system scheduling and inactive pages can delay callbacks and skew measurements.
USB, Bluetooth and dedicated wireless connections can differ. Compare modes only with consistent conditions.
Check the exact mouse or controller software and firmware for an advertised report-rate setting.
It is the rate at which a device reports state to its host, usually stated in hertz. For example, a nominal 1000Hz rate corresponds to a 1ms report interval.
No. It can measure mouse movement callbacks and available coalesced samples but cannot read USB or Bluetooth report traffic directly.
The browser may dispatch mouse movement in line with animation frames, or it may have coalesced updates. A low browser result alone does not prove a mouse fault.
It can show rates exposed by the browser, but it does not certify 4000Hz or 8000Hz hardware polling. High-rate movement samples may not reach JavaScript individually.
It is a browser Pointer Events interface intended to expose input updates with less delay than ordinary pointermove. Support depends on the browser and secure context.
It counts available movement samples embedded in pointer events. The reported sample rate can differ from the callback rate; neither is a raw USB measurement.
Yes, if the browser exposes the controller through the Gamepad API. Controller mode observes timestamp changes while you move a stick.
A static cursor or stick may produce no new movement events or timestamps, so the page has too little data for a useful observation.
More frequent hardware reports can reduce report-interval delay, but overall response time also depends on drivers, the game, rendering and display. An online result is not end-to-end latency.
The page layout is responsive. You need a physical supported mouse or controller for meaningful polling measurements; finger touches are not interpreted as mouse polling.
Polling Rate Test by Gamepad Tester ยท Browser-observed measurements ยท No account required
Sign in to your account