How to interpret the result
A median near 60, 90, 120, 144, or another configured mode is expected. Spikes can come from browser scheduling, power saving, background work, variable refresh, or display handoff.
Estimate the browser’s animation cadence and inspect frame-time stability with requestAnimationFrame.
Waiting for a test.
A median near 60, 90, 120, 144, or another configured mode is expected. Spikes can come from browser scheduling, power saving, background work, variable refresh, or display handoff.
This is a timing estimate, not an oscilloscope or high-speed-camera measurement. It cannot prove panel response time, scan-out behavior, overdrive, or exact VRR range.
Inspect viewport size, screen resolution, pixel ratio, orientation, color depth, and fullscreen behavior.
Open testInspect grayscale and RGB ramps for abrupt steps, clipping, tint, posterization, and dithering patterns.
Open testCreate a local WebGL context, inspect limits and extensions, and run a brief animation workload.
Open test