Phone refresh-rate test: understand your result

What the number means

Phone Test estimates timing between animation callbacks in your browser. It is a browser observation expressed in hertz, not a direct measurement of the display controller. Animation callback frequency generally follows screen refresh timing, but the browser and device control when those callbacks run.

Run a useful comparison

Keep the test visible in the foreground. Start a measurement and let it finish without switching apps or opening another tab. Record the result together with your browser, display setting and power mode. Repeat under the same conditions before comparing a second setting.

If you change a setting, change only one thing at a time. For example, compare a standard display mode with a high refresh mode while keeping the browser and power settings the same. Use the reported observations rather than assuming the highest marketing specification is always active.

Why the reading can be lower

Background tabs can have animation callbacks paused. Other work on the device, power settings and adaptive display behaviour can also affect what you observe. A phone advertised with a high maximum refresh rate is not a promise that every website will produce that rate throughout a session.

What to do with an unstable result

Return to the visible test, let competing activity finish and measure again. If readings remain inconsistent, save the range and the test conditions. Do not round an uncertain result into a claim that the display is defective. Compare with the phone’s supported display settings and manufacturer diagnostics if you need hardware confirmation.

Frame rate is not touch response

This test does not measure touch sampling rate, input latency or game performance. Use the touchscreen and multitouch checks for contact tracking; those tests answer a different question.

Technical references

• MDN: Browser animation timing