Refresh Rate Test Guide: Check How Smooth Your Screen Really Is

A screen does not show a continuous moving picture. It shows a rapid sequence of still images, and the speed of that sequence is the refresh rate, measured in hertz. A 60 hertz screen shows 60 images per second, a 120 hertz screen shows 120, and a 144 hertz screen shows 144. The Refresh Rate Test measures the rate your screen and browser actually deliver, which is not always the number printed on the box. A screen advertised at 120 hertz can run at 60 hertz because of a setting, a cable, a power-saving mode, or a browser limitation, and the only way to know is to test it.

Refresh rate matters most for motion. Scrolling a long page, moving a window, playing a game, or watching a fast video all look smoother at higher rates, because the gap between images is smaller and the eye has less chance to notice the steps. The difference between 30 and 60 hertz is obvious to almost everyone. The difference between 60 and 120 hertz is noticeable when scrolling or moving a cursor, though some people notice it more than others. Beyond 120 hertz the gains become harder to perceive for everyday tasks, which is why a test result should be read alongside what you actually do with the device rather than treated as a score to maximize.

There is also a difference between the screen's capability and the rate the browser can use. A gaming monitor may be capable of 144 hertz, but a browser may be limited by the operating system, the graphics settings, or a battery-saving mode on a laptop. A test that runs in the browser measures the practical result: what you actually experience while browsing, which is the number that matters for everyday use. If the test reports 60 hertz on a 120 hertz screen, something between the screen and the browser is holding it back, and the test gives you a reason to look for it.

How a refresh rate test works

The test uses the browser's own animation timing to count how often the screen redraws. The browser asks to be notified before each new frame, and the test measures the time between those notifications over a period of several seconds. From those intervals it calculates the rate: if frames arrive about every 16.7 milliseconds, the rate is 60 hertz; if they arrive every 8.3 milliseconds, it is 120 hertz. The test also watches for irregularity, because a screen that averages 60 hertz but drops frames in bursts will look worse than a steady 60 hertz screen, even though the average is the same.

For the result to be meaningful, the test needs a fair run. Close or pause anything that competes for the device's attention, such as a video playing in another tab, a large download, or a game running in the background, because those can steal processing time and make the test report a lower or jumpier rate than the screen itself delivers. Keep the test tab visible and in the foreground, since browsers slow down animation in background tabs, and let the test run for its full duration rather than judging the first second. A single short run is a snapshot; two or three runs under the same conditions give a result you can trust.

It is also worth testing under the conditions you actually use. A laptop on battery power often runs its screen at a lower rate to save energy, and a laptop plugged in may run faster, so testing both states tells you whether power saving is the cause of a lower number. An external monitor connected through an older cable or adapter may be limited by that connection, so testing the built-in screen and the external screen separately can isolate the bottleneck. The test measures your setup as a whole, and changing one part of the setup at a time is how you find which part is responsible.

Worked example

Consider a student who buys a monitor advertised at 144 hertz and connects it to a laptop. Running the test, the screen reports 60 hertz, not 144. The student checks the display settings and finds the monitor is set to 60 hertz by default, because the operating system picked the safest setting when the monitor was first connected. Changing the display setting to 144 hertz and re-running the test shows 144 hertz on the monitor, while the laptop's built-in screen still reports 60 hertz, which is its own maximum. The test has confirmed both that the new monitor works as advertised once configured, and that the laptop screen was never going to match it.

A second run tells a different story. The same student runs the test on battery power and sees the monitor drop to 60 hertz with occasional stutters, even though the setting still says 144 hertz. Plugging in the charger restores a steady 144 hertz. The cause is a power-saving feature that lowers the refresh rate on battery, and the student now knows that the lower rate on battery is a deliberate trade-off, not a fault. The practical decision is simple: plug in for games and fast scrolling, accept the lower rate on battery, and stop worrying that the monitor is broken.

The worked example shows the test's real value. It does not just produce a number; it produces a comparison between what the hardware claims, what the settings allow, and what the browser actually delivers. Each gap between those numbers points at a specific cause: a setting, a cable, a power mode, or a browser limit. Closing those gaps one at a time is how a screen ends up running at the rate it was bought for.

Mistakes to avoid

The first mistake is running the test with a video or game active in another tab and treating the depressed result as the screen's true rate. The second is running the test in a background tab, where the browser deliberately slows animation, and concluding the screen is faulty. The third is comparing a single short run across devices without repeating it, because one run can be skewed by a momentary load spike. The fourth is assuming the advertised rate is the delivered rate without checking the display settings, which is the most common cause of a disappointing result. The fifth is chasing the highest possible number for tasks that do not benefit from it, such as reading static text, where a steady 60 hertz is perfectly comfortable and battery life matters more.

Putting it into practice

Start by closing competing apps and running the test on each screen you use, noting the result for each. If a result is lower than the screen's advertised rate, check the display settings first, then the cable or adapter, then the power mode. Re-test after each change so you know which change made the difference. For everyday browsing, a steady result at the screen's advertised rate is the goal; for battery-powered use, decide consciously whether smoothness or battery life matters more, and set the power mode accordingly rather than leaving it to chance.

For related checks, the Screen Resolution test reports the size and pixel density of your display, the Mouse Test checks the buttons and scroll behaviour of your pointing device, and the companion guide on device health checks covers a full routine for keeping a device running well. A refresh rate test takes less than a minute, and it answers a question that specifications alone cannot: how smooth is this screen, right now, in the browser you actually use?

Key points

• Refresh rate is how many images per second a screen shows, and higher rates make motion look smoother
• A browser test measures the rate actually delivered, which can be lower than the advertised rate because of settings, cables, or power modes
• Close competing apps, keep the test tab in the foreground, and repeat the test before trusting a result
• Check display settings first when a result is low, then the connection, then the power mode
• A steady rate at the screen's advertised figure is the goal; chasing higher numbers for static reading wastes battery

In short: test each screen under real conditions, fix the setting or connection behind any gap, and judge the result by how smooth your everyday tasks feel.