How to compare sensor responsiveness in web apps

A web app may react slowly when you tilt your phone, rotate it, or move it between light and shade. That delay can come from the sensor, the browser, or the way the app displays readings. Comparing apps under the same conditions can help you narrow it down.

Use the Sensors Test as a baseline, then repeat the same movement in the web apps you want to compare. The test can show motion, gyroscope, compass, light, location, and vibration data, when your device and browser make those sensors available.

Compare the same movement in each app

1. Open the Sensors Test on the device you want to check. Keep the page visible in the foreground. If the browser asks for permission, allow access to the sensor or location you are testing.
2. Choose one movement that is easy to repeat. For motion, place the phone flat, tilt it slowly to one side, then return it to the starting position. For a compass, rotate the phone through the same turn each time, away from metal objects and magnets.
3. Watch the relevant reading while you move. Note whether it begins changing promptly, settles after you stop, or pauses or jumps. Repeat the movement five times so one unusually fast or slow response does not decide the result.
4. Open the first web app you want to compare in the same browser. Give it the permissions it requests, then repeat the movement from the same starting position and at roughly the same speed.
5. Repeat the same test in the next app. Keep the phone in the foreground, use the same browser, and alternate between apps if possible. This reduces the effect of differences in your movement or the device getting warmer over time.

You do not need a stopwatch to make a useful comparison. Look for a consistent difference across several trials, such as one app showing a change while the phone is still moving and another updating after it stops. A browser display is not a laboratory timing instrument, so treat small differences as clues, not exact latency measurements.

What the result means

Both apps react at about the same time

The device and browser are delivering readings in a similar way to both apps. If both respond quickly enough for your task, there may be nothing to fix. If they both feel slow, check the device, browser, and movement conditions below.

The Sensors Test reacts, but one web app lags

The sensor is producing readings, but that app may process, smooth, or display them less often. A moving graph or animated object can also appear delayed even when the underlying readings arrive. The app's code and visual design can affect what you see.

Both apps pause or update in jumps

The browser or operating system may be limiting sensor updates, or the device may be applying smoothing to reduce noise. A page that is hidden or in the background may also receive fewer updates. Repeat the test with each page open and visible before blaming the hardware.

One app shows no readings

Check whether the app requested permission and whether the browser supports the sensor feature it uses. A phone may not have every sensor, and browsers do not expose every sensor in the same way. No reading in one app does not by itself prove that a sensor is broken.

The compass changes unpredictably

Compass readings can shift near magnets, speakers, metal furniture, or other sources of interference. Move to a different spot and repeat the same turn. Do not compare a compass test in one location with another test beside a metal object.

How to make the comparison fair

1. Use the same device and browser. If you change both at once, you cannot tell which caused the difference. Test one device first, then repeat on another if needed.
2. Keep the page in front. Browsers may slow updates for background tabs or screens that are off. Keep the display awake and do not switch apps during a trial.
3. Repeat a simple movement. Start from the same position and move at a similar speed. For light readings, keep the phone still and change the light source rather than moving the phone toward it.
4. Check permissions. On Android, review the browser's app permissions in Settings › Apps › [your browser] › Permissions, and check the browser's site settings for sensor access if available. On iPhone, check Settings › Privacy & Security › Motion & Fitness if the browser appears there. Location access is separate from motion sensor access.
5. Check location access when testing location. On Windows 11, open Settings › Privacy & security › Location. On macOS, open System Settings › Privacy & Security › Location Services. On phones, check location permission for the browser and the site. A location reading can take longer because it may depend on GPS, Wi-Fi, or cellular information.
6. Reload the page and retry. A page may not start receiving readings after a permission change until you reload it. If the problem remains, close other sensor-heavy pages, update the browser, and restart the device.

When the sensor may be faulty

Suspect a device problem only if the same sensor gives missing or erratic readings in multiple apps, with permissions enabled, after a restart and in a suitable location. For a compass, first move away from magnetic interference. For motion, keep the device still, then make a slow, deliberate tilt. If the same fault persists across apps and browser sessions, contact the device maker or a repair shop. A browser test can reveal symptoms, but it cannot confirm which component needs repair.

Why two apps can show different readings

Apps may request sensor data at different rates, smooth sudden changes, or update their graphics on different schedules. Those choices can make one app look faster even if both receive similar sensor information. A web page also cannot always control how the operating system filters or schedules sensor readings.

The Sensors Test runs in your browser on the device being checked, so use it as a comparison point rather than as a precise hardware timing measurement.