Input timing diagnostics

Polling Rate Test

Move a stick or press buttons and this polling rate test will sample browser update intervals, average Hz, and event stability.

Polling Rate Timeline

Input timestamp intervals are sampled locally while you move a stick or press buttons.

No Controller Detected

Connect via USB or Bluetooth, then press any controller button to activate detection.

Average polling rate

Waiting

Waiting

Average interval

Waiting

Measured from browser-exposed gamepad timestamps.

Samples captured

0

Move the controller for a fuller timeline.

Embed This Tool

Use this iframe code to place this exact diagnostic widget on another page.

Polling rate widget

Embed the polling timeline for browser-observed update intervals.

https://gamepadtesteronline.org/embed/polling-rate-test/

<iframe src="https://gamepadtesteronline.org/embed/polling-rate-test/" title="Polling rate widget" width="100%" height="520" loading="lazy"></iframe>

What Browser Polling Rate Can And Cannot Prove

A polling rate test estimates how often the browser sees updated controller state. The page samples Gamepad API timestamps while you move a stick or press buttons, then converts average intervals into hertz. This controller polling rate test is useful for comparing wired and wireless modes, spotting unstable updates, and identifying obvious low-rate behavior.

Browser polling is not the same as a USB analyzer. The operating system, driver, browser scheduler, display refresh, power saving mode, and controller firmware can all affect the intervals visible to JavaScript. The gamepad polling test therefore reports practical browser-observed values rather than claiming laboratory precision.

A high polling rate can feel responsive, but it is only one part of input quality. A controller can update quickly while still suffering from stick drift, bad mapping, or application latency. After this polling rate test, use the latency test for event timing clues and the mapping page if the wrong control is being sampled.

How To Capture Stable Samples

Start the polling rate test with the controller connected and the page focused. Move a stick in a steady circle or press a button repeatedly for several seconds. The bar timeline grows as samples arrive. If the chart stays empty, the browser may not be receiving changing timestamps, or the controller may need a button press to activate detection.

Compare like with like. Run the controller polling rate test over USB, reset the timeline, then run Bluetooth with the same browser and power settings. A wired controller often shows steadier intervals, while Bluetooth may show more variation. If the average changes dramatically between modes, the connection path may explain the feel difference.

Close heavy tabs or overlays when comparing results. JavaScript execution can be delayed by browser workload, which changes what a gamepad polling test can observe. That limitation is part of the measurement, so use repeated runs and consistent conditions before drawing conclusions.

Interpreting Average Hz And Stability

Average hertz gives a quick summary, but stability matters too. A controller that averages a good number while producing large gaps may still feel inconsistent. Watch the bar heights: a steady row suggests regular updates, while uneven spikes suggest jitter, scheduling delays, or connection noise.

Do not assume that more hertz always solves a gameplay problem. If the polling rate test looks healthy but input feels delayed, run the latency test and check the game's frame rate, display mode, and controller order. If the polling rate is low only in one browser, try another current browser before changing hardware.

For competitive play, use the polling rate test as a comparison tool. It can show that one cable, adapter, Bluetooth stack, or mode behaves better than another in your environment. It should not be the only metric used to judge a controller.

Diagnostic Glossary

Polling rate

The observed frequency of controller state updates, usually described in hertz.

Interval

The time between two observed input updates.

Jitter

Variation in update intervals that can make input feel inconsistent.

Questions Users Ask

Short answers for common diagnostic decisions on this page.

Why is my polling rate lower than advertised?

The browser sees a processed input path, not raw USB packets. Drivers, Bluetooth, and JavaScript scheduling can lower the observed value.

Do I need to move the controller?

Yes. Many browsers update timestamps only when input changes, so movement or repeated presses help collect samples.

Is this a latency test?

No. Polling rate measures update frequency. Latency involves the delay from physical action to observed result.

Useful Next Checks

Compare input latency

Look at event timing clues and optional HID capability.

Inspect button mapping

Confirm indexes, labels, analog values, and unusual layouts.

Read troubleshooting paths

Fix detection, Bluetooth, permission, browser, and mobile issues.

Open all tools

Choose the right diagnostic page for the controller symptom you see.