Skip to the tool

Refresh Rate Test

Estimate the active browser refresh rate from animation timing and watch for an unstable cadence without installing software.

Refresh Rate Test

Estimate the active browser refresh rate from animation timing and watch for an unstable cadence without installing software.

Why this test is useful

A browser refresh estimate should settle near a stable value. Variable refresh rate, power saving and scheduler jitter can cause small changes between samples. For certified resolution, refresh rate or panel specifications, compare the browser result with the operating system and the manufacturer documentation.

Before you start

A reliable way to run the test

  1. A browser refresh estimate should settle near a stable value. Variable refresh rate, power saving and scheduler jitter can cause small changes between samples.
  2. Keep this tab in the foreground while measuring animation timing. Background tabs are deliberately throttled by modern browsers.
  3. If the computer is under heavy load, close demanding apps before judging timing or motion so browser scheduling is less likely to distort the result.
  4. When comparing monitor modes, change one setting at a time and use the same test speed, brightness and viewing position.

How to read the result

A browser refresh estimate should settle near a stable value. Variable refresh rate, power saving and scheduler jitter can cause small changes between samples. A browser can estimate refresh cadence but cannot prove that every frame reached the panel without loss or measure scanout behavior precisely. For certified resolution, refresh rate or panel specifications, compare the browser result with the operating system and the manufacturer documentation.

What to do next

What this test cannot prove

Browser timing and display information are practical estimates, not laboratory instruments or certified specifications. A browser can estimate refresh cadence but cannot prove that every frame reached the panel without loss or measure scanout behavior precisely. Do not make a hardware decision from one pattern alone. Repeat the observation with a second pattern or related test.