Refresh Rate Test

Estimate browser refresh rate and compare motion across frame rates.

CSS screen
—
Viewport
—
DPR
—

FPS & refresh rate comparison

Monitor ghosting test

Follow the moving bars. Look for faint trails or bright outlines.

Observation tips

Change one monitor setting at a time and repeat at the same speed. A response-time measurement requires separate equipment.

Visual patterns

Frame Skipping Test — Visual Pattern

Visual pattern only — manual observation.

Observation tips

One square lights up per browser callback. If you photograph the grid, aim to capture several consecutive squares in less than one 25-step cycle. Exposure, camera rolling shutter, panel scanning, and browser scheduling can all change what you see.

The pattern sequence was checked in software. Camera-based diagnosis and exposure times are unverified.

Screen Tearing Test — Visual Pattern

Visual pattern only — manual observation.

Observation tips

Watch for a horizontal break in the vertical line. Browser and system compositor settings affect the pattern. A continuous line here leaves game or application tearing unverified.

How to check your refresh rate

  1. Move the window to the display you want to test and keep the tab in front.
  2. Wait for at least about three seconds and 120 frame intervals. Wait longer on slower displays.
  3. Compare the browser estimate with your system setting. If they differ, check the setting, close busy tabs, and retest.

How to read the numbers

Estimated Hz is 1,000 divided by the median callback interval in milliseconds. Window FPS divides the number of intervals by their full duration, including long intervals. P95 time is the 95th percentile frame interval. The chart plots the highest interval in each group, so brief stalls remain visible.

We use the most recent 4.5 seconds, keeping at least the latest 120 intervals when available. Steady means the central 80% span at most 12% of the median interval and the two cadence estimates differ by at most 8% of the median-based estimate. An optional nearby display preset is a hint. Long intervals count times above your selected multiple of the median.

Timing comes from requestAnimationFrame. Callback cadence, game FPS and the panel’s physical scan rate can differ. CSS dimensions and DPR can change with browser zoom and display scaling.

Verification coverage
Version and date
rAF v1.0 / patterns v1.0 · 2026-11-16
Software verification
Chrome 155 and Edge 157 on Windows. Synthetic 24, 60, 144 and 240 Hz timestamp sequences and browser interaction checks.
Unverified hardware and methods
Physical refresh accuracy, other high-refresh or multi-display setups, and camera-based frame-skipping diagnosis.

Common questions

Why does my 144 Hz monitor show a lower number?

Check the selected refresh rate in your system. Browser scheduling, power settings, rendering load, or variable refresh can affect the sample. Retest in the foreground after changing one condition.

Can I compare 60 Hz and 144 Hz on a 60 Hz display?

You can request both tracks. The browser can only update them when it gets a callback, so the faster track cannot demonstrate 144 distinct updates per second on a 60 Hz setup.

Does a long interval prove a skipped display frame?

A long interval means the time between two browser callbacks exceeded the selected threshold. The cause can be browser load or scheduling. Use the visual pattern for a separate observation.