What Is a Refresh Rate Test?
A refresh rate test estimates how many times per second the active display pipeline can present a new browser animation frame. Refresh rate is expressed in hertz, or Hz. A 60Hz display can refresh up to 60 times per second, while a 144Hz monitor can refresh up to 144 times per second. This online monitor Hz test measures the cadence of requestAnimationFrame callbacks while the page is visible and converts the typical frame interval into an estimated refresh frequency.
The browser does not provide a universal, certified hardware refresh-rate property. For that reason, the number shown here is an estimate of the browser's active animation cadence, not a factory specification read directly from the monitor. When the system, browser and display are operating normally, the estimate often settles close to the configured refresh rate.
Refresh Rate vs FPS: What Is the Difference?
Refresh rate describes how often a display can update an image. Frames per second, or FPS, describes how many unique frames an application produces. A 144Hz monitor may refresh 144 times each second, but a game rendering only 60 FPS still produces 60 unique frames per second. Conversely, a game can render more frames than the display refreshes, which may increase responsiveness but can also produce tearing when synchronization is disabled.
This page uses FPS labels for the deliberately capped comparison lanes and Hz for the estimated display cadence. The native lane updates on every available animation callback, while the 30 FPS and 60 FPS lanes deliberately hold positions between updates.
60Hz vs 120Hz vs 144Hz vs 240Hz
At 60Hz, each refresh lasts about 16.67 milliseconds. At 120Hz, that interval is about 8.33 milliseconds. At 144Hz it is approximately 6.94 milliseconds, and at 240Hz it falls to about 4.17 milliseconds. Shorter intervals allow moving objects to advance in smaller steps and can reduce the time between an input and a visible update. Perceived improvement also depends on content frame rate, pixel response, motion speed, synchronization and the viewer.
How to Get the Most Accurate Monitor Hz Result
- Keep the test in the foreground and do not switch tabs while measurement is running.
- Close games, video encoders, heavy downloads and other applications that may create CPU or GPU spikes.
- Connect the browser window to the exact monitor you want to test before starting.
- Use fullscreen mode and a 20- or 30-second run when the reading is unstable.
- Check operating-system display settings and confirm that the desired refresh rate is selected.
- Connect laptops to power and disable aggressive battery-saving modes when testing high-refresh displays.
- Repeat the test in another modern browser if a device appears capped at a lower value.
Why the Test May Show 60Hz on a 120Hz or 144Hz Screen
The display may actually be configured to 60Hz, the browser may limit animation cadence on that platform, the page may be embedded or backgrounded, hardware acceleration may be unavailable, a battery-saving feature may reduce animation frequency, or the cable and display mode may not support the intended refresh rate. Some systems also behave differently with multiple monitors that use different refresh rates.
What the UFO Motion Test Can and Cannot Show
The moving spacecraft and comparison lanes are useful for subjective smoothness checks. Follow the object with your eyes and observe whether its edges remain clear, smear, leave colored trails or jump unevenly. However, a browser animation alone cannot precisely measure monitor pixel response time, input lag, overshoot, persistence, PWM flicker or true frame skipping. Those measurements require controlled test patterns, a high-speed camera, a photodiode or other specialized equipment.
Variable Refresh Rate and Multi-Monitor Limitations
Variable refresh rate technologies can change the display cadence dynamically. Browsers, operating systems and graphics drivers may also choose different scheduling behavior when a window crosses displays or when several monitors use different modes. Move the window fully onto one display, wait briefly and run the test again. Treat a fluctuating result as an indication to repeat under cleaner conditions rather than as proof of a hardware fault.
Privacy and Browser Processing
Refresh-rate calculation, motion rendering, frame-time analysis and device-information display occur locally on your device. No image of your screen is captured. No files or personal content are uploaded. The page stores only your non-personal test preferences locally, such as motion speed and selected pattern. When a timed test finishes, an anonymous aggregate counter is incremented; ratings update an aggregate rating total.