The short answer
Check the active refresh setting in the operating system for the correct display before blaming the monitor. Then confirm that the chosen resolution, GPU output, port, cable and any dock support the desired mode. Run Refresh Rate Test in a visible tab as a browser-cadence comparison, not a direct panel measurement.
A browser estimate near 60 Hz can occur even when a display supports a higher mode. Scheduling, power saving, multi-monitor handling and variable refresh all affect the page. A reported 59.94 Hz-like value is not automatically a broken 60 Hz configuration.
Practical checklist
- Select the correct monitor in OS display settings and inspect its active resolution and refresh options.
- Compare the monitor, GPU, cable, port and dock documentation at the actual resolution.
- Check supported power/performance modes without assuming every laptop exposes the same controls.
- Keep the browser visible and run the five-second refresh test after conditions settle.
- Repeat with the window on the intended monitor and avoid unrelated heavy tasks.
- Compare OS reports and browser sample context; seek supported manufacturer guidance for unresolved mode limitations.
Begin with the active operating-system mode
A monitor’s advertised maximum is not necessarily the mode currently selected. Open your operating system’s display settings, choose the actual display you want to inspect and look for the active resolution and refresh selection. Interfaces differ by system and version, so follow the OS help for the available advanced display options. A laptop’s internal panel and an attached monitor can have independent settings.
If a higher option is available, select it only if the OS and display support it, then confirm the image remains usable. Keep track of the original setting. If the option is absent, do not assume the panel is damaged: the current resolution, output path or driver may limit the list. Testpartout cannot read or change every active OS mode and should be used as a supporting browser observation rather than a substitute for those settings.
Resolution, cable, port and dock form one output path
A display mode requires support across the source, GPU output, connector, cable, intermediate dock or adapter and the monitor input. A cable that produces an image at one mode does not establish support for every resolution and refresh combination. Compare the actual product documentation at your intended resolution rather than relying only on a broad connector name or a marketing label.
A dock or adapter may introduce limits independent of the monitor, and a laptop’s different ports can have different capabilities. Use a supported known-compatible direct connection as a comparison if available. Avoid universal instructions such as assuming every HDMI or USB-C port supports a particular high-refresh mode. The browser cannot identify cable bandwidth, inspect adapter electronics or guarantee that a new cable will fix the symptom.
The browser measures animation cadence, not a panel controller
Refresh Rate Test uses consecutive requestAnimationFrame timestamps in a visible tab. It discards a 500 ms warm-up, collects roughly 4.5 seconds of intervals and estimates Hz from the median frame interval. The full run takes about five seconds. Samples and late or long frame counts help explain the evidence, and interval variation contributes to a consistency note.
This is browser scheduling through the operating system and compositor, not direct access to the panel controller. A 60 Hz-like result can reflect that path even when the active output supports more. A fastest single frame is not the primary value, and a contextual nearby common rate is not a guaranteed hardware setting. Read the median timing and sample quality together instead of treating the largest or smallest number as a certification.
Power saving and system load can constrain observations
Laptop battery or power-saving settings may affect rendering and, on some devices, available display modes. Check supported system or manufacturer performance settings and compare on safe appropriate power when relevant. Not every laptop exposes the same control, and not every low browser result is caused by power mode. Keep other conditions similar so a repeat actually tests the change you made.
Heavy applications, background tasks and browser scheduling can delay animation callbacks. Close only work you can safely close and repeat once the system is settled. Long intervals can indicate missed or delayed browser frames, not a failing monitor. Improving system conditions may make the estimate more consistent, but still does not turn a web page into a calibrated refresh or response-time instrument.
Multiple monitors and window placement
When several displays are connected, confirm which display the OS settings describe and place the browser window on the monitor you intend to test. A window spanning screens can complicate compositor behavior. Different monitors may have independent resolutions and refresh rates, and mirrored output may expose a different set of supported combinations from extended desktop mode.
Repeat with the page clearly on one display and the tab visible. Compare the OS’s per-display active mode, not a single global assumption. Browser or compositor behavior can follow a particular display cadence in ways that depend on the system. This guide does not promise that dragging a window always fixes timing or that every mixed-refresh setup behaves identically.
59.94 versus 60, and contextual common rates
A nominal 60 Hz mode may be reported near 59.94 Hz because some timing families use a fractional rate. That small difference is not by itself a malfunction. Browser measurement also has finite sample duration and scheduling variation, so a value like 59.9 should be understood with its interval evidence rather than forced into a perfect integer.
Higher common settings include 120, 144, 165 and 240 Hz, among others. Testpartout mentions a nearby common rate only as context when its estimate is within a small tolerance; it does not blindly snap every number to a marketed mode. The desired supported rate depends on the specific panel and output path. A 144 Hz advertisement does not guarantee that every input, resolution, power state and application will use 144 Hz.
Variable refresh and what this test cannot establish
Variable-refresh technology can change display timing with content and configuration. Browser animation callbacks may not expose every aspect of that behavior, and a short simple page cannot certify VRR range, synchronization quality or panel response time. Keep note of whether the relevant system settings changed between attempts. If a game behaves differently, compare its display mode and supported synchronization settings separately.
Do not equate refresh Hz with input-to-display latency or pixel transition speed. Refresh Rate Test does not measure motion blur, overshoot, HDR, color accuracy or display response time. Monitor Test offers visual patterns for larger uniformity and banding observations, while Screen Resolution Test labels browser dimensions and DPR. They complement timing evidence without combining it into a panel-quality score.
Decide the next check without blaming hardware prematurely
If OS settings show only 60 Hz at your chosen resolution, compare documentation for the entire output path and any supported alternative mode. If the OS reports a higher active mode but the browser stays near 60, inspect browser and compositor limitations before concluding the display is broken. A repeat in another supported browser is useful context, not a universal tie-breaker. Keep the same monitor, resolution and power conditions for that comparison.
For persistent missing modes or unstable images, follow the GPU, laptop or display maker’s supported driver and configuration guidance. Avoid undocumented firmware changes or claims that one browser result proves a cable or panel fault. Test timings and screen values remain local and are not sent to analytics. Save only a non-sensitive description of the OS mode, supported path and repeatable symptom if you need manufacturer support.
Frequently asked questions
Is 59.94 Hz different from a broken 60 Hz mode?
No. Fractional timing near 60 Hz can be normal, and browser estimates also vary slightly.
Does a 60 Hz browser result prove my 144 Hz monitor is faulty?
No. Compare the active OS mode, output path and browser scheduling limits.
Can a cable limit the available mode?
Yes, the supported combination depends on the whole output path, but this page cannot inspect or certify cable capabilities.
Does the browser test measure VRR or response time?
No. It estimates browser animation cadence and does not certify VRR behavior or pixel transition speed.
Keep the follow-up specific
Explore Full Device Check for a local diagnostic checklist and Video Call Check for meeting preparation. Read methodology for browser limits and privacy for actual data handling. If this guide disagrees with the current tool, contact Testpartout with a correction without private device identifiers or sensitive data.