1001Ferramentas
📊 Utilities

Browser FPS Meter

Measure browser frames per second via requestAnimationFrame. Shows instant, average and min FPS over the last 5s.

FPS instantâneo / médio / mínimo (5s)

0 / 0 / 0

Medição via requestAnimationFrame. Mantenha a aba focada para resultados precisos.

What this frame counter actually measures

Scrolling feels choppy and you cannot tell whether the page, the browser or the laptop is at fault. This page draws three live numbers: the frame rate of the last frame, the average over the past 5 seconds, and the worst single frame in that same window. It is good for comparing scenarios back to back: on battery versus plugged in, with and without that extension enabled, Chrome versus Firefox.

Under the hood it is a requestAnimationFrame loop. On every frame it measures the gap since the previous one and divides 1000 by it, keeping the values in a rolling 5-second window. The minimum is the worst individual frame in that window, so a single 100 ms hitch drops it to 10 and it only recovers once those 5 seconds roll off. The ceiling is your display: a 60 Hz panel gives you 60 and nothing more.

Measurement starts on its own when the page loads, with no start or reset button. It measures this page, which is essentially idle, so treat the number as the ceiling your browser can deliver rather than the frame rate of your own site or game. For that, use the Performance panel in DevTools on the real page. Browsers throttle requestAnimationFrame in background tabs, so keep this tab visible. Nothing is sent anywhere.

Frequently asked questions

Why is it stuck at 60 when my GPU can do far more?
The browser syncs frames to the display refresh rate. A 60 Hz monitor caps you at 60, while 120 or 144 Hz panels show higher numbers. Battery saver modes often cut it to 30.
Can I measure my own site with this?
No. It only measures this page. Open your site and use the DevTools Performance panel, or drop a similar requestAnimationFrame loop into your own code.
The minimum dropped to 4. Is something wrong?
One bad frame is enough: switching tabs, an antivirus scan, a build running in the background. Worry when the average stays low for several seconds in a row.

Related Tools