Controller Rumble Test
Fire a short vibration pulse at your gamepad and feel whether the motors still work. Everything runs in your browser — nothing is uploaded.
Connect a controller and press any button
Plug in (or pair) an Xbox, PlayStation, Switch Pro, or generic USB/Bluetooth gamepad, then press any button so your browser can see it. Some browsers only reveal a controller after the first input.
Rumble / vibration test
How the rumble test works
Press Test rumble and the page asks your controller for a dual-rumble effect: both the heavy and the light motor at 90% strength for 450 ms. Hold the pad loosely in your palm rather than gripping it — a tight grip damps the vibration and can make a working motor feel dead. Run it two or three times. If one side of the controller buzzes and the other stays still, one motor (or its solder joint) has failed, which is a common outcome after a drop.
If the button is disabled with a note saying rumble isn't supported, that is a browser or connection limitation more often than a broken controller. Haptics reach the browser through the Gamepad API's vibration actuator, and support is uneven: Chrome and Edge implement it on desktop, Firefox and Safari are patchier, and the same controller frequently rumbles over USB while refusing to over Bluetooth. Before concluding the motors are dead, try a cable, and try a Chromium-based browser.
One quirk worth knowing: some browsers only allow haptics after you have interacted with the page, and a few stop the effect if the tab loses focus. If nothing happens on the first press, click somewhere on the page and press again with the tab in the foreground.
Next: run the button test, or check both sticks with the stick drift test.
