01
Check a lower-than-expected FPS result
Check display mode, power settings and the browser. On a phone, check mobile refresh conditions.
FRAME RATE TEST / IN YOUR BROWSER
Start with a ten-second sample.
See your FPS and the gaps between frames.
Keep this tab visible. Start with a baseline, then compare another run.
Each run starts with a one-second warm-up. Compare the same drawing task with different amounts of added load.
Browser frame rate
Animation callbacks per second.
Ready. Start a test to collect your first sample.
YOUR MEASUREMENT
Method: animation callbacks sampled in a visible browser tab, using the duration and drawing load selected above.
Use the rate currently selected in your system’s display settings. Leave this empty if you are unsure.
A completed, steady browser sample within 5% of your selected rate is described as close. Longer intervals and added drawing load take priority in the advice. The FPS measurement and exported intervals stay unchanged.
An interval spike is longer than 1.5× this run’s median. Use the chart to see when those longer gaps occurred.
Compare runs with the same duration, load and display settings. How it works ↗
USE YOUR RESULT
MORE WAYS TO UNDERSTAND YOUR DISPLAY
Enter a resolution and physical diagonal. Compare two displays by PPI and dimensions.
See the browser’s screen size, page dimensions and pixel ratio, with each reading clearly labelled.
Trace with a finger, recheck gaps, compare simultaneous touches and try a 20-second hands-off check.
MAKE THE READING USEFUL
Want to see the effect of added work? Repeat the same duration with animation load enabled. Keep the browser, display settings and other conditions as similar as you can. The result shows how the same browser animation behaves as its drawing workload increases.
Browser FPS describes the animation callbacks observed by this page. Browsers commonly schedule these callbacks near the display’s refresh cadence, but the browser, power mode and system workload can alter the result. The browser animation API documentation explains this timing boundary.
If the result is near 60 FPS on a display advertised as 144 Hz, check the selected display mode and repeat the test. Compare the browser result with the system’s active refresh setting using the setup guide.
Compare FPS, Hz and pixel response to choose the right measurement for your question.
Download the completed result before changing your setup. Compare tests of the same duration and load, and note any change you made between them. A brief interruption can affect a short sample, so repeat a surprising result.
Read the measurement method for the exact calculations, warm-up and interruption rules. See how local results and shared settings are handled.