Check whether your phone browser can trigger the vibration motor. Try short taps, long vibration, pulse patterns, and emergency-style bursts without installing an app.
Open this page on your phone and tap each pattern button. Hold the device in your hand or place it on a hard surface so you can feel or hear the vibration clearly. A healthy haptic motor should respond immediately to supported patterns.
If the browser reports vibration support but you feel nothing, check system haptic settings, battery saver, silent mode, and whether another app can vibrate the phone. Some browsers require a direct tap before vibration is allowed.
The Web Vibration API is not available on every device. Many desktop browsers, iOS browsers, and privacy-focused mobile browsers block it. That does not always mean the phone motor is broken; it may simply mean the browser does not expose the feature.
For used phone checks, compare browser results with system haptics such as keyboard vibration, incoming call vibration, and alarm vibration. Consistent failure across system features is a stronger sign of hardware trouble.
Safari on iOS does not support the web Vibration API, so no website can trigger an iPhone's haptics. This test works on Android Chrome and most Android browsers. On iPhone, check vibration in Settings → Sounds & Haptics instead.
On a supported Android device, if none of the patterns produce any vibration and the phone also stays silent for calls and alerts, the haptic motor is likely faulty. Test a few patterns before concluding it's a hardware problem.
Check that vibration intensity isn't turned down in your system settings, and that the phone isn't in a battery-saver mode that reduces haptics. A consistently weak motor across full intensity can indicate wear.
It works on Android browsers that support the Vibration API, which is most of them. A few manufacturers limit web-triggered vibration; in that case, native vibration for calls and notifications is the fallback way to check the motor.