Polling Rate Test — what your pad really reports

The figure on the box is the controller's hardware ceiling. What reaches your browser depends on every link between the pad and the system: cable, hub, dongle, Bluetooth radio and the controller's own firmware report mode.

Some controllers default to a lower report rate over certain protocols even when the hardware can manage more. Sony's DualSense for example clamps to around 250Hz over Bluetooth even though the same hardware can hit 1000Hz on USB.

Bluetooth itself can carry rates up to about 1000Hz under ideal conditions but in practice most controller firmware caps Bluetooth output well below USB. The DualSense settles near 250Hz, Xbox pads near 125Hz, Switch Pro near 120Hz.

Some high-end controllers using a proprietary 2.4GHz dongle instead of standard Bluetooth bypass this and report at full rate. The dongle is doing the heavy lifting there, not the Bluetooth stack.

The browser only counts a new poll when the controller's state changes. A stick at rest produces no state changes so the timestamp the browser exposes stops updating even though the controller is reporting at full rate.

Moving the stick continuously generates a fresh state on every poll, which is what gives the test something to count. Pressing buttons works too but a rotating stick is the easiest way to keep the changes flowing.

Going from 125Hz to 250Hz is noticeable in fast genres like fighting games and twitch shooters. The jump from 500Hz to 1000Hz is much harder to feel and sits below the threshold most players can distinguish in blind tests.

For casual single-player gaming the difference between 250Hz and 1000Hz is mostly academic. For competitive play it can matter at the margins, especially when paired with a high refresh-rate monitor.

The browser runs in the same event loop as everything else on the page. A garbage collection pass, a background tab waking up or even the cursor doing something elsewhere can briefly delay the gamepad poll. One or two missed polls over a thirty-second run is normal.

What you want to avoid is a steady stream of drops or large clusters of them. That pattern points at hardware or interference rather than browser scheduling.

Chrome and Edge tend to report gamepad timestamps most consistently. Firefox can be less granular with timestamps so the test relies more on axis-change detection there, which works but can undercount slightly on stationary moments.

Safari's gamepad support has improved but is still the least predictable for high-rate polling. For the cleanest result run the test in Chrome or Edge on a desktop, with the controller wired in.

Probably not. Going from a flaky 80Hz wireless link to a stable 250Hz wired one is a noticeable upgrade. Going from 250Hz to 1000Hz is much harder to feel outside of competitive play.

Stability matters more than peak rate. A steady 250Hz beats a 1000Hz reading that drops to 200 every few seconds. The grade from the stability run is the number to trust over the headline figure.

Yes, often. A cable with damaged shielding or weak conductors can drop packets or force the controller's USB interface to retry transmissions, both of which reduce the effective rate that reaches the browser.

If a wired controller is reporting much lower than expected, swapping the cable is the cheapest fix to try. A known-good cable from another device is the fastest way to rule it out.