Display FPS Test

For general web browsing and video playback, 60 FPS is the standard target matching standard 60Hz monitors. For competitive gaming, esports, and fast scrolling on modern panels, 120 FPS, 144 FPS, or 240 FPS provides substantially greater visual clarity, lower motion blur, and faster visual feedback.

A browser test measures rendering and frame dispatch timings available to the JavaScript runtime via requestAnimationFrame. While browser FPS will closely mirror physical refresh rate when VSync is engaged and no throttling is active, browser security sandboxes prevent direct hardware-level register reads of the monitor's display controller.

Common causes include: browser hardware acceleration being disabled in settings, high background CPU/GPU loads, operating system battery-saving modes, multi-monitor frequency mismatches (e.g. running 60Hz and 144Hz monitors simultaneously on Windows), or browser tab throttling when running non-focused tabs.

Browsers run on an asynchronous event loop that alternates between JavaScript execution, layout calculation, garbage collection, and GPU composite submission. Brief microsecond delays in any of these sub-systems can cause minor frame-to-frame timing jitter.

Frame time is the duration in milliseconds required to render and display a single frame (1000 / FPS). For example, 60 FPS equals ~16.67 ms per frame, while 144 FPS requires just ~6.94 ms per frame. Lower and more consistent frame times result in smoother perceived motion.

1% low represents the average frame rate of the slowest 1% of all measured frames during the test session. It is the most reliable metric for detecting micro-stutters that may not be apparent in simple average FPS calculations.

Yes! If you have a 144Hz monitor connected, set your Windows/macOS display settings to 144Hz, ensure hardware acceleration is enabled in your browser, and select 144 Hz or Auto on this test.

Yes. Modern Chromium and WebKit browsers can run requestAnimationFrame at 240Hz and higher on capable displays, provided the GPU driver supports high-refresh composite pacing in windowed apps.

Yes. By default, web browsers synchronize requestAnimationFrame to the primary display's VSync interval to eliminate screen tearing. If VSync is locked at 60Hz in your GPU control panel, browser rendering will be capped at 60 FPS even on higher refresh displays.

Yes, clicking the Fullscreen button activates true browser fullscreen mode. This allows the OS window manager to bypass desktop composition layers (DWM/Compositor) and dedicate maximum GPU pipeline priority to the active viewport, minimizing frame drops.