Actual Refresh Rate vs. Advertised Hz: What to Check
Understand why a monitor can advertise 144 Hz yet present about 60 Hz, and use a browser timing test to verify the active setup.
The number on a monitor box describes what the panel can support under the right conditions. It does not prove that your current cable, port, resolution, operating-system setting, and browser are presenting that mode. The useful question is: what refresh behavior is active on the screen in front of you right now?
Separate Hz, FPS, and frame time
Refresh rate is the display cadence, measured in hertz. Frame rate is how many frames the browser or game produces per second. Frame time is the interval between frames. They are related, but they are not interchangeable.
The simple relationship is frame time = 1000 / rate milliseconds. At 60 Hz, that is 1000 / 60 = 16.666... ms, or about 16.67 ms. At 144 Hz, it is 1000 / 144 = 6.944... ms, or about 6.94 ms. At 240 Hz, it is about 4.17 ms. These examples describe timing, not a guarantee that a particular browser will sustain every frame.
Test the active presentation
Open Refresh Rate Test after selecting the desired mode in your operating system. Let the live reading settle for several seconds. The page observes animation-frame timing and displays a practical estimate, frame-time history, and motion lanes. It does not change the display setting or inspect the monitor’s internal electronics.
If you selected 144 Hz and the reading stays close to 60 Hz, first check the setup rather than the panel. Confirm the operating system mode, resolution, cable specification, input port, browser hardware acceleration, and laptop power profile. A high-refresh display may start in a 60 Hz default mode after connection or wake.
Why the number can move
Animation-frame timing can be affected by browser work, background tabs, power saving, a hidden document, or system load. A short spike does not prove the display changed modes. Look at the settled reading and the pattern of frame times, not one unusually high or low sample.
Variable refresh rate adds another layer. When VRR is active, the display can adapt its cadence to changing frame output. A browser test may therefore show a practical range instead of a perfectly fixed number, especially when the workload is light or changes during the observation.
Verify the connection before returning the monitor
Use the resolution and refresh combination you actually plan to use. Some ports support a high refresh rate only at a lower resolution; some cables or adapters become the limit. If an external display is connected through a dock, test the direct port as a comparison.
On a laptop, compare plugged-in performance mode with battery saver. On a desktop, check that the display is connected to the graphics output you intend to use. Restart the browser after changing hardware acceleration so the test begins with a clean presentation path.
Read the result responsibly
A browser timing estimate is valuable for finding a mismatch between your selected mode and your visible experience. It is not a certification instrument. It cannot tell you the panel’s response time, overdrive behavior, input latency, or whether a manufacturer rounded its advertised specification.
Use the number alongside motion: scrolling, dragging a window, or watching the test lanes. Smoothness depends on frame pacing as well as the average rate. If the setup is configured for 144 Hz, the browser settles near that range, and motion is consistent, the active path is behaving as expected. If not, trace the connection and power settings one at a time.
Keep a short verification log
When you are troubleshooting a mismatch, write down the selected resolution, refresh mode, input port, cable or dock, browser, and power state. Change one item at a time and run the test again. This prevents a cable swap and a settings change from looking like one fix when you do not know which part mattered.
It also helps to compare a second browser or a direct connection only after the original result is recorded. If both browsers report the same settled range, the operating-system mode or physical connection is more likely to be the limit. If they disagree, check hardware acceleration and background load before drawing a conclusion. The log turns a vague “it feels slow” complaint into a sequence that another person can reproduce.