Neutral sample
Stick drift and deadzone
Set the controller on a steady surface and do not touch either stick during the sample.
Ready for an 8-second sample.
Connection timing diagnostics
Browser-Observed Controller Update Rate
Estimate how often your browser receives new controller states. Compare connection modes without confusing update rate with input latency.
- ✓ Runs in your browser
- ✓ No sign-in
- ✓ Local results
Local-only test
Connect with USB, Bluetooth, or a supported wireless adapter. Then press any controller button so your browser can expose it. Your readings are processed on this device.
Detected device
No controller detected
Gamepad API ready · waiting for input
L1
R1
L
R
Update rate— Hzbrowser-observed
Buttons—reported
Axes—reported
Mapping—browser label
Live input
Sticks and triggers
Left trigger 0%
Observed range: not sampled
Right trigger 0%
Observed range: not sampled
Full movement
Range and circularity
Rotate each stick slowly around the outer edge, then sweep the center in several directions.
Move the sticks to begin range tracking.
Input coverage
Buttons and D-pad
Press and release every available control. Analog buttons show their reported value.
No button activity yet.
Raw browser data
Axes and mapping
Use these values to spot unusual layouts. A blank standard mapping does not automatically mean the controller is defective.
View raw browser data
Connect a controller to view raw data.
Optional capability
Vibration check
Browser haptics are not available for every controller, connection method, operating system, or browser.
Connect a controller to check browser support.
Did you feel the pulse?
Private test record
Keep your result
Reports are stored in this browser. Sharing is optional and puts only the selected result in the link.
Diagnostic readings describe what this browser receives, not electrical measurements from the controller. Confirm important findings in the game or device where you plan to use the controller.
Use the test as evidence, not a pass/fail sticker.
This test estimates how often the browser observes a new gamepad state or timestamp while you move a control. It can help compare wired and wireless modes or identify an obviously inconsistent connection.
Move an analog stick continuously during the sample and keep the browser tab visible. The tool summarizes observed updates and timing variation instead of claiming an exact hardware polling rate.
Update rate is not the same as end-to-end input latency. Display refresh, browser scheduling, operating-system drivers, USB or wireless transport, game logic, and the controller itself all affect the complete response path.
Signals to watch
- Browser-observed updates per second
- Interval consistency and variation summary
- Pause-aware measurement for background tabs
- Repeatable wired-versus-wireless comparison workflow
Run a repeatable check.
- 01
Connect the controller and press any button so the browser can detect it.
- 02
Use the focused test panel slowly and deliberately. Watch the live values during presses, holds, movement, and release.
- 03
Repeat any suspicious result after reconnecting, then confirm it in the game or device where the controller will be used.
What a useful result looks like.
Look for repeatable behavior rather than a single momentary value. Stable, symmetric movement and clean press-and-release behavior are generally more useful signs than chasing a perfect zero.
If a result changes substantially between USB and wireless modes, browsers, or computers, the connection, driver, browser, or remapping software may be part of the problem.
Important browser-test limits
Keep this tab visible and move a control throughout the sample.
Questions about browser-observed controller update rate
Is this my controller's USB polling rate?
Not necessarily. It is an estimate based on states visible to browser JavaScript. The USB bus, driver, browser, and display loop can each limit or reshape what the page observes.
Does a higher update rate mean lower input lag?
Not by itself. More frequent updates can reduce one part of the timing budget, but this tool does not measure the full button-to-pixel delay.
Why does the result change between runs?
Browser workload, power saving, wireless conditions, tab visibility, system load, and how consistently you move the control can affect the sample. Run several tests under the same conditions.