Why this polling rate test exists
Mouse software often shows a configured polling rate, but a setting and the events delivered to an active browser are not exactly the same measurement. Polling Rate Test exists to give users a quick, transparent way to observe that event stream during real movement without installing another program.
The homepage keeps the test close to the top. Choose a duration, move inside the marked area, review the estimated Hz and stability, then repeat the same workflow after changing a device setting, USB port, wireless mode, driver, or browser.
What the homepage does
The current tool listens for supported Pointer Events and uses the browser's high-resolution performance clock to estimate event frequency. It reports an estimated rate, average, peak, valid sample count, and a stability score. The page also provides a short reference table for common settings such as 125 Hz, 500 Hz, 1,000 Hz, and 8,000 Hz.
The optional Focus Mode uses the browser Fullscreen API only when the user explicitly selects it. Fullscreen is not required for a polling rate test, and a browser that refuses the request does not block the normal page workflow.
Who can use Polling Rate Test
Gamers can compare a mouse's polling settings before troubleshooting input feel or CPU load. Hardware reviewers and support teams can record a repeatable browser estimate alongside the device model, connection type, driver version, and test conditions. Everyday users can use it as a first check when a mouse feels inconsistent or a high-rate mode appears not to be active.
The result is a diagnostic signal, not a promise about a game's input latency, a monitor's refresh behavior, or the exact report rate inside a USB or wireless protocol. A browser can only measure the events that reach its active tab.
A privacy-conscious measurement flow
The ordinary test runs in the browser with client-side JavaScript. It does not need an account, a download, a mouse-data upload, or a server-side calculation request. Raw movement coordinates are not required for the final summary and are not intentionally stored after the current test.
This is a product boundary, not a promise about every browser extension, network provider, analytics tool, or advertising service. The separate Privacy Policy explains technical data, cookies, web beacons, IP addresses, Google products, advertising, and support communications.
What we care about
- A working polling rate test that is visible without a registration wall.
- A clear distinction between browser-estimated events and a hardware setting.
- Results that show more context than one unexplained number.
- Field-level feedback for missing, unsupported, insufficient, and failed states.
- A responsive interface with keyboard access, visible focus, and comfortable touch targets.
- Straightforward explanations that help users repeat and compare a test fairly.
How to use a result responsibly
Keep the duration, browser, movement pattern, connection, and background workload consistent when comparing two runs. Record a range rather than one perfect number, especially at high settings where browser scheduling and event batching may be more visible.
If a result is unexpectedly low, check the USB port or hub, receiver placement, battery, firmware, driver, browser load, and device utility before deciding that the mouse is defective. For a hardware-level confirmation, use a dedicated vendor utility or measurement method designed to inspect the device protocol.
A focused product with room to grow
The first release is an English homepage for mouse polling rate testing. Separate keyboard, controller, click, DPI, or input-lag tools may be added later as independent experiences with their own input signals and limitations. They are intentionally not presented as unfinished destinations on this page.
The goal is simple: make a common hardware check quick to start, honest about uncertainty, and easy to repeat. Feedback about an unclear label, browser issue, or unusual device behavior helps improve the tool without hiding its measurement boundaries.
Contact
Questions, corrections, and product suggestions can be sent to support@pollingratetest.wiki. Helpful reports include the browser, pointer type, connection method, test duration, expected setting, and the result that appeared on screen.