Start by separating hardware from software.
Vibration depends on more than the motors inside a controller. The game or webpage must support a compatible haptic interface, the operating system and driver must expose it, and the active connection mode must carry the command.
Browser vibration support is narrower than native game support. If a gamepad rumbles in a supported game but not on this page, that can be a normal browser limitation rather than a fault.
Test in layers: browser feature detection, a known supported game, and official controller software or console behavior. This avoids replacing hardware because one software path is unavailable.
Work through the likely causes.
- 01
Hold the controller securely and try the short browser vibration pulse only after the page reports a haptic actuator.
- 02
Check the game's vibration setting, accessibility options, and active controller profile.
- 03
Charge the controller or install fresh batteries; some devices reduce vibration at low power.
- 04
Reconnect by USB and wireless separately because browser haptic support can differ by transport.
- 05
Close remappers or virtual-controller layers, then update firmware only through supported official tools.
- 06
Confirm behavior in a known compatible game or console before treating the motors as defective.
Check what the browser can see.
Open the full tester to inspect buttons, sticks, triggers, mapping, range, and neutral noise.
Repeat before you conclude.
A repeatable issue across connections, browsers, and native games is stronger evidence of a controller fault than a one-time browser reading. If the problem appears only in one game, review that game’s controller support, deadzone, remapping, and launcher settings.
What to keep in mind
Set the controller where it cannot fall and stop if it makes an unusual sound or becomes hot.
How the browser readings are defined
Our live tools use the standardized browser Gamepad interface and explain its limits in our methodology. Device mappings and proprietary features can still differ by operating system, browser, connection, firmware, and controller mode.
Questions about this issue
Why does the page say vibration is unsupported?
The browser did not expose a compatible haptic actuator for that device and connection. It does not prove the controller lacks working vibration motors.
Can the site test adaptive triggers or HD haptics?
No. Advanced platform-specific effects generally require native APIs, supported games, and proprietary hardware features outside the standard browser interface.
Why is vibration weak?
Battery level, game intensity, motor balance, profile settings, connection mode, and controller design can affect strength. This site does not calibrate motor output.