A phone advertised with a 120 Hz display can still produce a browser result near 60 FPS. The specification describes a supported display capability. This page counts animation callbacks during a sample. Compare the current power and display settings to understand the difference.

First, make the browser comparison repeatable

  1. Open the browser FPS test in a visible tab, with drawing load off.
  2. Use the same sample duration and orientation. Leave the test in the foreground until it finishes.
  3. Record the phone model, system version, browser and power-saving setting.
  4. Repeat once, then change one relevant setting and test again.

A static page, a scrolling app and this animation need not use identical scheduling. Keep the phone’s selected mode separate from the rate observed by a particular app. FPS and Hz are related measurements with different meanings.

iPhone and iPad: check Low Power Mode

On models with ProMotion, Apple documents a display refresh limit of 60 Hz in Low Power Mode. See the current iPhone power-mode guide or iPad Low Power Mode guide. In Settings, check Battery; the exact controls vary by model and system version.

If Low Power Mode is enabled, compare a run with it temporarily disabled, then restore your preferred setting. Check that your model has ProMotion, and record the browser rate with each power setting.

Android: use your model’s display guidance

Android refresh-rate menus and power policies vary by model. Look in the manufacturer’s documentation for the model’s supported display modes, adaptive behavior and battery-saving restrictions.

For example, Google’s Pixel display guide describes Smooth Display increasing refresh for some content on listed models, and says Battery Saver disables Smooth Display. Follow the instructions for your own model. Avoid forcing undocumented developer options just to obtain a higher test number.

If the browser still reads around 60

Compare another current browser under the same conditions, if available. Record whether the reading changes between browsers, and keep the selected power and display modes with each result.

Keep the completed results alongside the selected display mode and the manufacturer’s supported behavior. When asking for help, state which app shows the discrepancy and whether it changes with power saving. The measurement method explains the animation callbacks, sample duration and interruption handling behind the result.

Platform sources checked 26 October 2026. Menus and supported behavior can change with software updates.