Controller Polling Rate Test

A controller polling rate test estimates how often new controller input updates are visible to the browser while you move a stick or press controls continuously.

Not necessarily. A browser can limit how often a webpage observes gamepad updates, so this page reports browser-visible update frequency rather than claiming a certified hardware or USB polling rate.

Connect the controller, press a button so the browser exposes it, choose a duration, start the test and move an analogue stick continuously until the timer finishes.

Many gamepad timestamps update only when the controller state changes. Continuous movement provides a steady stream of input updates for the browser to observe.

Average Hz is calculated from the mean interval between valid observed controller updates. A shorter average interval produces a higher frequency.

Median Hz is based on the middle observed update interval and is less affected by occasional long or short samples than a simple average.

It is calculated from the shortest valid interval seen during the test. It can be affected by timing noise, so average and median are usually more useful.

Some browsers expose or sample controller state in a way that is tied to the page's animation-frame loop, which can make the observed rate cluster near the display refresh rate.

Yes. Browser, operating-system, driver, connection and page-timing limits can all make the browser-visible rate lower than the controller's hardware polling specification.

Yes when the Xbox controller is exposed through the browser Gamepad API. Wired and Bluetooth results can differ.

Yes when the DualSense is recognised by the operating system and exposed to the browser. USB and Bluetooth can produce different browser-visible behaviour.

Potentially. The controller must be exposed through the Gamepad API. Mapping and timestamp behaviour vary between controllers, browsers and operating systems.

Test both if you want a comparison. Connection type can affect latency, update behaviour and browser support, although this page does not directly measure end-to-end input latency.

No. Polling or update frequency describes how often input states can be reported. End-to-end latency also includes controller processing, wireless or USB transport, operating-system, game, rendering and display delay.

That means the controller did not expose a changing Gamepad timestamp that the page could use, so the tool detected state changes during animation frames instead. This fallback is more strongly limited by browser frame timing.

Very long gaps usually mean you stopped moving the controller, while implausibly tiny intervals can be timing noise. The test filters those intervals so pauses do not dominate the result.

The live controller values and timing samples used by this tool are processed temporarily in your browser and are not uploaded as controller-input recordings.

Use the Controller Deadzone Test for stick thresholds, Stick Drift Test for unwanted centre movement, or the Xbox and PS5 controller pages for brand-specific button checks.