Motion test patterns
Pursuit, scrolling text and a 24–60 fps content clock against your measured refresh — blur, tearing, dropped frames, cadence judder.
Refresh rate is measured from frame timing, not assumed. Speeds are in pixels per frame (and screen widths per second) so results transfer between panels. The frame-rate test quantises motion to a content clock and reports the resulting cadence (3:2 at 60 Hz, 5:5 at 120 Hz, uneven at 50). A dropped-frame counter tells you when the browser, not the display, is the bottleneck. Fullscreen starts the test.
Refresh rate is measured from frame timing, not assumed. A dropped frame is any interval longer than 1.5× the expected frame time; a non-zero count means the browser, not the display, is the bottleneck.
Need this math wired into a real system? We do that for a living.
Start a conversation →