Troubleshooting
Not measurable here
Some figures need every report a pad sends, or parts of it the browser doesn't pass on. Where the source reading the pad can't give them, PadBench says so rather than show a wrong number.
Polling rate and chatter
The browser's Gamepad API hands the page one reading per screen refresh, so the pad's own reports can't be counted, and most bounces of a switch fall between readings. The Polling rate tile and the Timing tab then say Not measurable here, and the Buttons tile Chatter not measurable here.
Read more in Polling rate and timing
Motion, touchpad and battery
The Gamepad API passes on no motion, touchpad or battery, so the Motion tile says Not readable here, and the Controller tab Not read through this source. A Sony pad on Bluetooth sends them only once it's switched to its full report. An Xbox pad has no motion sensors at all, and the tile says so instead.
Read more in Sony pads on Bluetooth
Buttons the browser leaves out
Some buttons never reach the page through the Gamepad API, such as a DualSense's Mute. The Controller tab names them, and says whether WebHID reads them.
Where they can be measured
WebHID, in Chrome and Edge on a computer, reads every report. Where it can open the pad, the tile offers Use WebHID: on a DualSense, a DualShock 4, a Switch Pro Controller, and on Windows an Xbox pad. Other pads can be added through WebHID with the + after the controller tabs. Safari, Firefox and phones have no WebHID, and the Windows app reads every HID pad report by report itself.