Monitor refresh-rate estimate
Keep this tab visible, stop heavy background activity if possible, then run a three-second measurement.
Estimate the refresh cadence available to this browser tab. The test samples requestAnimationFrame timestamps and reports estimated Hz, median frame interval, timing jitter and sample count.
Keep this tab visible, stop heavy background activity if possible, then run a three-second measurement.
requestAnimationFrame callbacks generally follow the display refresh cycle, so stable measurements often land near common rates such as 60, 120, 144, 165 or 240 Hz. Small deviations are normal. A large mismatch may indicate a different OS display mode, browser throttling or unstable frame delivery.
Use repeatable conditions. One browser result is a diagnostic clue, not a complete hardware verdict.
Background tabs are commonly throttled and will produce misleading results.
Press Measure refresh rate and avoid switching windows for a few seconds.
Check whether the estimate is close to the refresh rate selected in your operating system or GPU settings.
Variable refresh, power saving and load can change timing. Repeat after closing heavy applications if the result is unstable.
This is a browser timing estimate, not a hardware oscilloscope measurement. Variable refresh rate, compositor behavior, power saving, remote desktop, multi-monitor setups and system load can affect the callback cadence.
Frame timestamps are not perfectly uniform. Browser scheduling and display timing can produce small differences around the configured refresh rate.
Check the operating-system display refresh setting, the active monitor, cable/port capabilities, power-saving settings and whether the browser window is actually on the high-refresh display.
No. It estimates browser repaint cadence. Game FPS depends on the game engine, GPU, CPU, settings and frame pacing.
It should not be trusted there. Browsers commonly pause or throttle requestAnimationFrame in hidden tabs.