Test Your Rig · Device Lab

Device Lab

Every USB input device streams "HID reports" — tiny packets carrying its movement and buttons. This lab opens your mouse, gamepad, wheel or other device with your permission and shows what the hardware itself sends: its identity, its interfaces, the raw bytes, and the true report rate measured packet by packet — not the number on the box.

WebHID isn't available in this browser.
It's supported in Chrome and Edge on desktop. Firefox, Safari and mobile browsers don't expose it — the classic mouse tester and gamepad tester work everywhere.
Your browser will list the HID devices it allows. Standard keyboards are blocked by Chrome on purpose (so no site can read keystrokes at this level) — mice, gamepads, wheels, and vendor devices work. Nothing is written to the device.

Vendor / product ID
Measured report rate
move / press to generate reports
Interval · median
between reports
Interval · jitter
mean |Δ| between gaps
Reports seen
0
Move the mouse in fast circles (or wiggle sticks / hold buttons) — idle devices send nothing, so the rate is only measurable while the device is talking.

Live report stream

waiting for reports…

HID collections

Usage pageUsageInOutFeature

Why measure at the report level?

Our regular mouse tester counts the events a web page receives — after the OS and browser have merged and throttled them. The Device Lab sits one layer lower: it counts the packets the device itself emits. That's how you verify a "1000 Hz" mouse really polls at 1000 Hz (or that the 8000 Hz mode is actually enabled), catch a wireless mouse silently dropping to 125 Hz to save battery, and see stick data flowing from a controller byte by byte.

Interval jitter matters as much as the rate: a healthy wired mouse shows gaps of almost exactly 1 ms with microseconds of wobble. Wide, irregular gaps at the report level point at the device, its dongle, or the USB port — not your PC.

Frequently asked questions

How is this different from the mouse tester?

The mouse tester sees OS-processed events; this counts the raw reports the hardware sends. An 8000 Hz mouse shows 8000 here even when pages receive fewer events.

Why doesn't my keyboard appear in the picker?

Chrome blocks standard keyboards from WebHID so no site can read keystrokes at the hardware level. That protection is deliberate.

Is reading my device safe?

The page only listens to reports the device already sends and writes nothing to it. Permission is per device and revocable in site settings.

More free tests