Explore OGadget
Your everyday workbench

Refresh Rate Test

A dedicated workspace for refresh rate test.

Available tool · Local processing
Refresh Rate TestBrowser-local processing

Estimate the cadence of animation callbacks in this browser tab. Compare repeated measurements while the page stays visible.

Ready to collect 180 frame intervals

How Refresh Rate Test works

requestAnimationFrame supplies a timestamp for each callback. Estimated cadence = 1,000 ÷ median frame interval in milliseconds. The report also shows the 10th–90th percentile interval range. It measures browser scheduling, not the display’s advertised refresh rate.

Example and interpretation

A median interval near 16.67 ms corresponds to about 60 callbacks per second. That does not independently prove a 60 Hz monitor: power saving, browser caps, dropped frames and variable-refresh behavior can change the observed cadence.

Limits and common sources of error

This is not a calibrated hardware refresh-rate, FPS, input-lag, response-time or motion-blur test. Moving the window between displays may affect measurements. Hidden-tab measurements are cancelled to avoid misleading results.

Practical guide

Refresh Rate Test: how to use the result

This refresh rate test estimates the cadence of animation callbacks delivered by your browser. It is useful for observing how steadily a page is being scheduled on the current screen. The number should be read as a browser timing observation, rather than an independent confirmation of the display’s advertised refresh rate or the frame rate of a game.

How to use this workspace

  1. Keep the browser window on the display you want to observe and make the tab visible.
  2. Start a measurement while avoiding unrelated changes such as moving the window to another monitor.
  3. Read the estimated cadence together with the interval range. Repeat under similar conditions if the result varies.

A practical example

A median interval close to 16.67 milliseconds corresponds to roughly 60 animation callbacks per second: 1,000 divided by 16.67. This can occur in a browser session for several reasons. The calculation alone cannot establish that the connected panel is physically operating in a particular hardware mode.

How to interpret your result

The interval range adds context that a single rounded frequency hides. Wider variation suggests less consistent callback timing in that sample, but does not identify whether the cause was browser scheduling, power management, other work or display behavior.

Common mistakes and limits

Background tabs can be throttled, which is why a hidden-tab measurement is cancelled. Variable refresh behavior, power saving and browser caps can also affect the result. This is not an input-lag, pixel response-time, motion-blur or game benchmark.

Make the comparison repeatable

Test one condition at a time and note which device, browser and connection you used. If an unexpected result appears, repeat the same action before changing settings. A second browser or another known-working peripheral can help separate an application or permission problem from a device problem. Keep those comparisons descriptive: this page observes what reaches the browser and does not have access to a laboratory measurement of the hardware.

Frequently asked questions

Why is the reading lower than my monitor’s rated Hz?

The page measures callbacks available to the browser. A hardware specification does not guarantee that this tab will receive callbacks at the same rate in every condition.

Can I compare two screens?

You can repeat the same browser test on each screen, keeping other conditions similar. Treat the difference as a session-level observation, not a certified comparison of panel performance.

Continue with related tools