Rules & quick reference
| Sample window | 10 seconds after first mouse movement |
|---|---|
| Live estimate | Unique timestamps in a rolling 500 ms window |
| Data source | Coalesced pointer samples when supported; otherwise pointermove |
| Limitation | Browser event delivery rate, not a USB hardware measurement |
Move continuously inside the panel
Move a mouse pointer into the panel and draw continuous circles. The first mouse movement starts a ten-second measurement. Keep movement inside the panel for the whole sample; the counter cannot use motion events delivered to another page element. The graph shows recent estimates, and the live number uses unique sample timestamps inside a rolling half-second window. No rate is inferred from a stationary mouse because no delivered movement samples are available.
How event grouping affects the estimate
A browser may combine several physical motion samples into one pointermove event. When getCoalescedEvents is supported and returns samples, this tester uses those timestamps instead of counting only the outer event. If the API is unavailable or returns an empty list, it falls back to the event timestamp. Identical timestamps are not counted twice. The API is not uniformly available across browsers, so the page reports whether coalesced samples were observed during your session.
What the final number represents
The reported mean averages live rate estimates from active windows during the run. It is a browser-delivered rate, not direct access to USB polling, device firmware settings or radio packets. Scheduling, timestamp precision, a capped frame rate and operating-system event handling can constrain it. A reading near a familiar rate such as 125, 500 or 1000 Hz does not certify that hardware setting. A lower reading is not sufficient evidence that a mouse is defective.
Use it as an observation tool
Keep the same browser, connection mode and motion pattern when comparing sessions. Continuous circles give more data than occasional short movements. If the browser exposes only frame-aligned events, switching a mouse setting may not visibly change the reported estimate. Use manufacturer software or a suitable native measurement tool when you need a hardware-level answer. The reaction and aim games answer different questions: they include how you respond to visual targets, whereas this panel observes event timestamps during motion.
Your result stays on this device
Completed game results are saved in this browser when local storage is available. Bests and recent history describe this device’s saved runs, not a public leaderboard. Changing browsers, clearing site data or using private browsing can remove them. Copy score writes only the visible result summary to your clipboard when you request it; sharing is your choice. Clear local game data removes scores, daily completion markers and the saved 2048 board for this origin. No game result is uploaded, and the games remain usable when persistent storage is unavailable. Use the rule table to check what the active mode measures before comparing another session. A changed duration, input method or grid difficulty can change the task even when the displayed score uses the same unit.
Frequently asked questions
Is this my exact USB polling rate?
No. It estimates browser-delivered motion samples; device and OS processing happen before those events.
Why does it show my display rate?
A browser may deliver or group motion events around animation frames. Coalesced events can help when available.
Does it work with touch?
The measurement accepts mouse pointer motion. Touch sampling follows a different input path.
Why does the rate fall when I stop?
There are fewer or no movement samples. Keep the mouse moving inside the panel throughout the sample.
Built by Mihai · Reviewed 2026-10-24 · Read the related technical guide · Testing policy