Monitor USB and Bluetooth controller connections, interruptions and browser-visible input updates. Compare sessions, inspect event timelines and export your results without installing software.
Plug in or pair your controller, press any button, and choose a test length. Keep this page active during your session.
Active sample intervals and device-presence markers
Move a stick or press and release buttons regularly during a test to create meaningful update samples.
Review device visibility, connection changes and meaningful input updates, then save a report for comparing wired and wireless setups.
Events will appear here when a session begins.
Connect a controller and begin monitoring. If you run a demo, the result will be labelled simulated.
| Date | Mode | Duration | Disconnects | Gaps | Median |
|---|---|---|---|---|---|
| No saved sessions yet. | |||||
Begin with the same controller and game conditions you normally use. Connect your Xbox, PS4, PS5 or compatible PC gamepad with a known working cable or Bluetooth pairing.
Keep the page visible throughout the test. Tab switching and background throttling can distort browser timing. Avoid treating an idle controller as a failed connection.
A disconnect means the selected controller stopped being exposed as connected through the Gamepad API. A longer input interval means the browser observed more time between changed gamepad states.
Neither result on its own identifies radio interference, packet loss, controller firmware, battery condition or USB electrical faults. Active-input intervals can also be affected by browser frame scheduling.
Tracks when a browser can see a selected controller, including genuine connect and disconnect events.
Records meaningful movement or button changes. Idle controllers can legitimately report no new input.
Measures gaps between observable input changes. These reflect browser sampling and usage patterns, not physical radio polling.
Shows how long the device remained exposed while the test was active, excluding periods when the browser tab was hidden.
Save repeated tests under comparable conditions to identify patterns without claiming lab-grade signal measurements.
Reports are generated in your browser. Export JSON or CSV to retain a personal record of the test results.
Press any controller button while the page is visible. Confirm USB data support, system pairing and browser Gamepad API access.
Compare results with a wired connection, check controller charge and make sure the device is paired correctly in system settings.
Keep the page in focus, create steady input and repeat the measurement. Browser timing gaps are not automatically lost packets.
Select the exact gamepad from the device menu. A different device may take over an index after reconnection.
Connect your controller, press a button so the browser can see it, start monitoring and move the sticks or press buttons regularly while the page remains visible.
It works with devices that your operating system and browser expose through the Gamepad API, including many Xbox, DualShock 4 and DualSense controllers.
No. Browsers do not expose raw Bluetooth radio packet loss through the Gamepad API. The tool records visible connection changes and browser-observed input timing.
When a controller is idle, gamepad state timestamps may stop changing. Idle periods are not classified as input gaps by this tool.
Not necessarily. Browser scheduling, uneven user movement and system load all affect the time between visible changes.
For meaningful results, keep the testing tab visible. Browsers throttle background animation and input polling; the page flags visibility interruptions.
Wired connections can remove some wireless variables, but actual performance depends on the controller, cable, ports, adapter and environment. Compare repeated sessions on your own setup.
Yes. The tester runs locally in your browser with no account required.
Yes. Download JSON or CSV records, copy a summary or store recent comparisons in local browser storage.
No. It does not measure the time between a physical button press and the corresponding in-game or on-screen response.
This independent web tool reports browser-observed controller activity. It cannot directly measure Bluetooth signal strength, USB bus errors, radio packet loss or hardware input latency.
Sign in to your account