Refresh rate test

This Hz test measures how often your screen updates while the page is moving. It records frame times for a few seconds and uses the middle frame interval to estimate the refresh rate in Hz. The result describes what the page observed during that run.

A screen’s refresh rate and the number shown by a game or video are related ideas, but this test measures the screen’s frame timing in the browser. It does not measure every app or every moment. The page may show a different result if the browser limits how often it can update the display.

The test also reports timing jitter and missed frames. These readings help you see whether frame timing stayed even during the test. They do not, by themselves, identify which part of the device or connection caused an uneven result.

Measured Hz is the refresh rate estimated from the frame intervals. A higher number means the page observed more screen updates in the same amount of time. Read it as a measurement from this browser run, not as a promise that every program will show the same rate.

Jitter describes changes in the time between observed frames. A steadier timing pattern means the intervals were more alike during the run. If jitter is noticeable, the display or browser did not deliver evenly spaced frames for this measurement, but that alone does not show why.

Missed frames are frames the test expected but did not observe in its timing sequence. The page also shows a frame-skip pattern intended for a camera photo. A repeated gap in that pattern can help make skipped updates visible, though the photo is a separate view from the timing estimate.

The display links table uses the resolution reported for your display to show which cable and port combinations can carry that resolution at different rates. Check that information alongside the measured Hz. Browser rate limits can affect the result, and the page shows caveats from its data when they apply.

A lower measured rate than you expected can mean the browser capped the page’s update rate. It can also reflect the timing seen during that particular run. This reading alone cannot tell you whether the screen, cable, port, or browser is responsible.

Uneven timing or missed frames means the page did not see a steady sequence of updates. Compare the measured Hz with the display links table for your resolution, and read any browser caveat shown on the page. The table can help you check whether the connection has a listed rate limit for that resolution.

If the result still seems wrong, use the page’s change refresh rate fix guide. It covers what to check next. A guide cannot guarantee that a change will improve the result, because the test does not identify the cause on its own.

The connection table is specific to the resolution shown for your display. It lists cable and port limits by rate, so use the row or entry that matches your resolution before comparing it with measured Hz. A connection limit can help explain why a display may not run at a rate you expected.

The table is reference information, while measured Hz, jitter, and missed frames come from the live browser test. Those parts answer different questions: the table describes listed connection capacity, and the live readings describe frame timing observed by this page. A browser cap caveat can also affect what the test reports.

Use all the readings together rather than treating one number as a pass or fail. If your expected rate and the measured rate differ, check the connection information and the caveat before using the fix guide.