- Click your blocker’s icon in the toolbar (uBlock Origin, AdBlock, Ghostery, Brave Shields, etc.)
- Turn it off for
clickspeedtest.info— usually a power button or “pause on this site” - Reload the page
Hardware deep dive
Mouse Polling Rate Test
How often your mouse actually talks to your computer — and why chasing a bigger Hz number stops paying off sooner than marketing suggests.
Click below, or press Space
Ready — select a duration above
Clicks per second
0.0
Clicks per minute
0
What polling rate actually is
Polling rate is how often your mouse reports its current state — position and button status — to your computer, measured in Hertz (times per second). It has nothing to do with how fast the mouse’s internal sensor can detect movement or a click; it’s purely about how often that information gets sent over the USB connection. A 125Hz mouse reports once every 8 milliseconds. A 1000Hz mouse reports every 1 millisecond. An 8000Hz mouse reports every 0.125 milliseconds. Between those reports, nothing new is communicated — if a click happens right after a report goes out, it waits for the next scheduled report to be seen by the computer at all, regardless of how fast your finger actually moved.
That waiting period is the entire reason polling rate matters for anything you do with a mouse, click speed included: it sets a hard ceiling on how quickly an event on the mouse can possibly become an event your computer knows about, independent of the mouse’s actual sensor speed or your own reaction time. It’s a communication-layer constraint, not a sensing-layer one — worth keeping that distinction in mind whenever polling rate gets discussed alongside sensor specs like DPI, since the two measure genuinely different things about a mouse.
The math, worked through properly
| Polling rate | Report interval | Max theoretical reports/sec | Worst-case added latency |
|---|---|---|---|
| 125 Hz | 8 ms | 125 | up to 8ms |
| 250 Hz | 4 ms | 250 | up to 4ms |
| 500 Hz | 2 ms | 500 | up to 2ms |
| 1000 Hz | 1 ms | 1000 | up to 1ms |
| 4000 Hz | 0.25 ms | 4000 | up to 0.25ms |
| 8000 Hz | 0.125 ms | 8000 | up to 0.125ms |
“Worst-case added latency” is the important column, and it’s worth understanding precisely: if a click happens the instant after a report was just sent, it has to wait almost the full interval before the next report carries it to your computer. If it happens right before a scheduled report, the wait is nearly zero. On average across many clicks, the added latency from polling alone is roughly half the interval — so 1000Hz averages around 0.5ms of polling-related delay per click, 125Hz averages around 4ms. Neither number is something a human can consciously perceive on its own, which is the first hint toward where this genuinely stops mattering for anything you’d notice in practice.
Why doubling the number doesn’t double what you feel
Human reaction time — the time between your brain deciding to click and your finger actually pressing the button — sits in the range of 150–250 milliseconds for most people even when primed and ready for a specific stimulus. A polling-rate jump from 1000Hz to 8000Hz changes worst-case added latency from roughly 1ms to roughly 0.125ms — a difference of well under one millisecond, disappearing into a reaction-time budget that’s two to three hundred times larger. This is why polling rate improvements show genuinely diminishing returns past 1000Hz for the vast majority of practical purposes, click-speed testing very much included: the jump from 125Hz to 500Hz is meaningfully perceptible for competitive purposes; the jump from 1000Hz to 8000Hz is, for almost everyone, not something you could pick out in a blind test.
Where the higher numbers do matter: extremely fast, precise flick-aiming in shooter games can benefit marginally from very high polling rates, because cursor position updates (not just click timing) get reported more frequently too. For pure click-speed and click-timing purposes specifically, the practical ceiling of meaningful improvement sits much closer to 1000Hz.
Where the “bigger number” marketing push came from
Polling rate sat quietly at 125Hz or 500Hz for most consumer mice for well over a decade, largely unremarked on outside enthusiast forums. That changed once 1000Hz became achievable and marketable as a distinct, easy-to-advertise number — from there, the same logic that drives megapixel counts and processor clock speeds elsewhere in consumer electronics kicked in: bigger numbers sell, even past the point of practical benefit. The jump to 4000Hz and then 8000Hz mice happened less because a clear technical need emerged and more because manufacturers had headroom to push a number that’s simple to put on a box, easy to compare against a competitor’s spec sheet, and genuinely does have a real technical meaning — even when that meaning stops translating into anything perceptible well before the number stops climbing.
This isn’t unique to mice, and it’s worth recognizing the pattern because it recurs constantly in gaming hardware marketing: a genuinely meaningful technical improvement (125Hz to 1000Hz) gets followed by increasingly marginal iterations (1000Hz to 8000Hz) marketed with the same confidence and prominence as the original meaningful jump, because the marketing incentive to keep climbing a number doesn’t disappear just because the practical benefit has.
What to actually prioritize when buying based on this spec
If polling rate is a factor in a mouse purchase decision, the practical guidance is straightforward: confirm 1000Hz support and stop optimizing on this specific number. Beyond that point, the switch type, shape, weight, and sensor quality of a mouse will affect your actual clicking and tracking experience far more than whether it supports 4000Hz or 8000Hz. A mouse that markets an extremely high polling rate as its headline feature, without equal attention to switch quality or ergonomics, is often optimizing for a spec sheet number rather than the experience that number is supposed to represent.
Worth checking specifically: whether a given mouse’s high polling rate mode requires a specific USB port, dongle, or software configuration to actually engage, since some mice ship defaulting to a lower rate with the higher one requiring an extra step most buyers never take — meaning the headline spec on the box may not reflect the out-of-box experience at all unless it’s deliberately configured.
How to check your actual current polling rate
Most gaming mice ship at 1000Hz by default, but not always, and it’s worth confirming rather than assuming. A few reliable approaches:
Manufacturer software. Most gaming mouse brands include a settings utility that displays and lets you change the polling rate directly — this is the most reliable source since it’s reading the mouse’s actual configured value, not inferring it.
Dedicated polling rate test tools. Several independent tools exist specifically to measure real-world polling behavior by timing how frequently your mouse actually reports movement, which can reveal a gap between what your mouse claims to be set to and what it’s actually delivering — a genuine discrepancy that shows up more often than you’d expect, especially over USB hubs or extension cables, and one that manufacturer software alone won’t always catch.
Windows Device Manager (rough check only). This won’t give you an exact Hz figure, but confirms your mouse is connected via a USB port capable of supporting higher polling rates in the first place — a mouse plugged into an old USB 1.1-only port physically cannot exceed 125Hz regardless of what it’s configured for, which is a genuinely easy thing to overlook when troubleshooting an unexpectedly low reading.
Why your actual polling rate might be lower than you think
Several real-world factors silently cap polling rate below what a mouse is nominally capable of:
| Factor | Effect |
|---|---|
| USB port generation | Older USB 1.1 ports cap out around 125Hz regardless of mouse capability |
| USB hubs, especially unpowered ones | Can introduce polling instability or reduce effective rate below the configured value |
| Wireless connection type | 2.4GHz dongles vary significantly by manufacturer; Bluetooth typically caps well below wired maximums |
| CPU load / background processes | Extremely high polling rates (4000Hz+) genuinely increase CPU interrupt load, and a heavily loaded system can miss reports |
| Outdated or missing drivers | Generic drivers sometimes default to 125Hz even on mice capable of far more |
That CPU load point is worth taking seriously at the very high end specifically: an 8000Hz mouse is generating an interrupt request eight thousand times per second, every second it’s connected, whether or not you’re actively using it. On older or already-busy systems, this can occasionally cause more problems than it solves, which is a genuinely counterintuitive outcome for a spec universally marketed as a pure upgrade.
Wireless polling rate realities
Wireless mice using a dedicated 2.4GHz USB receiver can, on modern hardware, match wired polling rates closely enough that the difference is negligible for click-speed purposes — this is a genuine improvement over older wireless technology, where wireless meant a real, noticeable step down. Bluetooth is a different story: Bluetooth’s own protocol design generally can’t sustain the same report frequency as a dedicated 2.4GHz receiver, and mice connected via Bluetooth typically report meaningfully slower and less consistently, even on mice that perform excellently over their dedicated wireless dongle. If click-speed performance matters to you and your mouse offers both connection types, the dedicated receiver is worth using over Bluetooth even though both are technically “wireless” — the underlying radio protocol and how it schedules communication differs enough between the two that “wireless” alone doesn’t tell you much about actual polling performance.
How to change your polling rate
On most modern gaming mice, this is a straightforward software setting rather than anything requiring technical intervention:
Manufacturer utility software. The standard path — install the mouse’s companion app, find the polling rate or “report rate” setting, select your target value. Changes usually apply immediately without needing a restart, though it’s worth reconnecting the mouse once afterward just to confirm the new setting actually took effect rather than assuming it did.
Generic or older mice without dedicated software. Some non-gaming mice can still have their polling rate adjusted through third-party USB configuration utilities, though this is less reliable and carries more risk of misconfiguration than using official manufacturer tools when they’re available.
What you can’t do: no software adjustment can push a mouse’s polling rate above what its hardware physically supports. A mouse built for 1000Hz maximum will not report faster than that no matter what setting you select — software controls stay within hardware limits, they don’t exceed them.
Does this actually matter for click-speed testing specifically?
Honestly, less than most of the surrounding discourse suggests, once you’re above roughly 500Hz. The jump from a budget 125Hz mouse to a standard 1000Hz gaming mouse is a real, measurable difference in how consistently your clicks get registered at high CPS — that’s worth caring about. The further jump from 1000Hz to 4000Hz or 8000Hz is, for the specific purpose of clicking speed and timing, chasing a number well past the point where it changes anything you or this site’s tools can actually detect.
If you’re deciding what to prioritize in a mouse for click-speed purposes specifically, switch actuation force and debounce time (covered on the Click Per Second Test page) are both more consequential than polling rate past the 1000Hz mark — worth reading before spending extra money purely chasing a bigger polling-rate number on a spec sheet.
FAQ
What polling rate should I use for click speed testing?
1000Hz is the practical sweet spot for almost everyone. Going higher (4000Hz, 8000Hz) produces changes too small for a human to perceive in click timing, while potentially adding unnecessary CPU load on older systems.
How do I know my actual polling rate, not just what it’s set to?
Manufacturer software shows the configured value. Dedicated polling rate testing tools measure what your system is actually receiving in practice, which can differ from the configured value due to USB hubs, cables, or driver issues.
Does higher polling rate mean higher CPS?
Not directly. Polling rate affects how quickly a click you’ve already made gets reported to your computer, not how fast you can physically click. Below around 500Hz it can genuinely bottleneck fast clicking; above 1000Hz it stops being a meaningful factor.
Is Bluetooth mouse polling rate really that much worse?
Generally yes, compared to a dedicated 2.4GHz wireless receiver on the same mouse. If your mouse supports both, use the dedicated receiver for click-speed purposes rather than Bluetooth.
Can I increase my mouse’s polling rate above its rated maximum?
No — software settings select among rates the hardware physically supports, they can’t exceed the sensor and controller’s actual capability regardless of what any utility claims to offer.
More click tests
- Click Speed Test — the main CPS test, with every duration from 1 to 60 seconds
- 10 Second Click Test — the standard benchmark distance, with an endurance breakdown
- Click Per Second Test — the hardware science behind your score
- Jitter Click Test — technique-specific benchmarks and how-to
- Mouse Click Test — diagnose a failing switch or double-click fault
- Drag Clicking — the hardware technique that pushes past muscle speed entirely
- Clicker Speed Test — sustained-rate testing for clicker and idle games
- Double Click Test — check your double-click pace against your OS setting
- Butterfly Clicking — the two-finger technique with the most learnable ceiling