Frequently Asked Questions

Polling rate is how often a mouse reports its position to the computer, measured in Hz. A 1000 Hz mouse reports 1000 times per second. Higher rates can reduce input lag, but the benefit tapers off above 1000 Hz for most people. The browser observes a rate that is often lower than the hardware spec because events are delivered on display frames and after OS processing.

A website can only count the pointer events the browser delivers to the page. It cannot read the hardware, firmware, or USB controller. The result is a browser-observed rate, not a hardware measurement. The how-we-measure page explains the method and its limits.

Browsers align pointer events to display frames by default. Even with coalesced events, the browser receives input after the OS processes it. A 1000 Hz mouse commonly reads somewhat below 1000 in a browser — the gap grows above 1000 Hz. This is normal. The browser guide explains the per-browser ceilings and why this happens.

Drops in the stability graph usually mean the browser delivered fewer samples in that second. Common causes: wireless interference, low battery, receiver too far or blocked, heavy background CPU load, or mouse power-saving features. Try a wired connection, a fresh battery, or moving the receiver closer.

A wired mouse removes the wireless link as a variable, so it typically shows lower variation. A modern 2.4 GHz wireless mouse with a good battery and clear line of sight can be nearly as steady. Bluetooth mice often show higher variation because of the protocol's lower report rate and duty cycling.

Yes, slightly. More reports per second mean more CPU interrupts and more wireless transmissions. On a modern system the CPU cost is negligible. On a wireless mouse, a higher report rate reduces battery life — often noticeably above 1000 Hz.

Not directly. Polling rate is input frequency; FPS is frame output. A very high polling rate on an older system could add a tiny amount of CPU load, but it does not change the GPU render pipeline. The main benefit of high polling is reduced input-to-display latency, not higher FPS.

No. DPI (dots per inch) is how far the cursor moves per inch of physical mouse movement. Polling rate is how often the position is reported. They are independent settings. You can have high DPI with low polling rate or vice versa.

Most gaming mice let you change the rate in vendor software (for example G HUB, Synapse, GG, or the manufacturer's utility). Some mice have a hardware button that cycles through rates. Check the manual for your model. The browser guide has a section on common vendor tools.

Not from a web browser. Keyboard events arrive after OS processing, and the WebHID API blocks web access to keyboard input reports for security reasons. Any website claiming to measure keyboard Hz online is fabricating numbers. Read our dedicated guide on what browser keyboard tests can and cannot show.

Analytics are strictly limited to aggregate page views and test starts. No mouse movements, clicks, timings, or hardware serials are sent. No cookies are set in the default configuration. The privacy policy has the full legal statement.

LocalStorage is used strictly on your client device for UI preferences (theme mode and language selection) and to store summary metrics of your last 10 benchmark runs under the key mk-run-history so you can compare configurations. All localStorage access is wrapped in try/catch so private browsing never breaks.