Polling
Connect a controller and press a button if the browser has not exposed it yet.
Gamepad Polling Rate Test: Controller Update Rate, Timestamp Changes, Input Sampling, And API Refresh Speed
Estimate controller update rate from Gamepad API timestamp changes.
What this test checks
- Controller API detection
- Button, stick, trigger, or haptic behavior
- Live polling and input state
- Read Updates Per Second
How to read the result
Polling depends on the browser Gamepad API, so connect the controller and press a button first. Repeated drift, low polling, or missing button states usually deserve a second pass with the related controller diagnostics.
Start With A Connected Controller
The browser needs an active gamepad before polling can be measured. Pressing a controller button often initializes the Gamepad API connection.
Move A Stick Or Press Buttons During Sampling
Activity helps produce timestamp updates that the tool can count. This gives a practical estimate of controller update behavior inside the browser.
Read Updates Per Second
The tool estimates updates by observing gamepad timestamp changes over time. Browser and device behavior affect the result; this is not a direct USB polling measurement.
Compare USB And Bluetooth Modes
Users can repeat the polling rate test over USB and Bluetooth to compare latency-sensitive controller setups. Different connection modes may update at different rates.
Related I/O Checkup Tools
What does Polling measure?
Estimate controller update rate from Gamepad API timestamp changes.
Do I need to install anything for Polling?
No. Polling runs directly in a modern browser. Some checks may ask for permission when they need camera, microphone, gamepad, pointer lock, touch, or audio output access.
Are results uploaded?
The test runs in your browser and uses local input events or browser hardware APIs for the visible diagnostics.
Why should I run related tests too?
Related tools help separate hardware issues from browser timing, display behavior, input device settings, or permission problems, which makes the final diagnosis more useful.
Detailed Testing Guide
Controller symptom
This controller page checks one part of the Gamepad API signal instead of assuming one button press proves the whole pad is healthy.
Start with a baseline run before changing device settings. Record any repeated symptom so the next comparison is useful.
API evidence
Watch button state, stick axes, trigger values, vibration response, polling updates, and whether the controller stays visible.
Watch Controller API detection, Button, stick, trigger, or haptic behavior, Live polling and input state, Read Updates Per Second. These observations come from the browser; they do not reveal hidden firmware or factory calibration data.
Controller test method
Press a button to expose the pad, then test one control group at a time.
Keep the test conditions stable. Changing browser, cable, port, lighting, surface, volume, grip, or selected device all at once makes the result harder to trust.
Result reading
Browser support, Bluetooth latency, driver mapping, and firmware can all change what the page receives.
A repeated pattern matters more than a single spike. When something looks wrong, confirm it with another pass and compare a related tool before deciding the device itself is defective.
Limits and next checks
Use button, stick drift, trigger, vibration, and polling tests together for a complete controller pass.
For a closer comparison, try Gamepad Button Test, Stick Drift Test, Trigger Test, Polling Rate Test. Keep the same device and connection while you investigate the next symptom.