Frames Per Second (FPS) and Frame Drops
You'll learn how to use the DevTools FPS meter to spot animation jank and measure visual smoothness in your web apps.
What Is FPS in Web Performance?
Frames Per Second (FPS) measures how many complete screen redraws your browser performs every second. The ideal target is 60 FPS — meaning the browser renders a new frame every 16.67 milliseconds (1000ms ÷ 60 = 16.67ms). At this rate, animations and scrolling feel buttery smooth to users.
When your app can't maintain 60 FPS, you experience frame drops — missed rendering opportunities that create visible stuttering or "jank." This happens when JavaScript execution, layout calculations, or painting takes longer than 16.67ms, forcing the browser to skip frames.
Spotting Problems with the FPS Meter
Think of the FPS meter like a heart rate monitor for your interface. Consistent green bars near 60 FPS indicate healthy, smooth rendering. Sudden dips or red bars signal dropped frames — moments where animations freeze or scrolling stutters.
In the Performance panel, the FPS meter appears as a graph above your timeline recording. Watch for:
- Consistent green bars at 60 FPS: Smooth experience
- Yellow/red bars or gaps: Frame drops and jank
- Patterns during interactions: Scrolling, hovering, or animations triggering drops
Frame drops often correlate with long tasks you identified earlier. If you see a JavaScript task taking 50ms, expect several dropped frames during that period — the browser simply can't render while executing that code.
Why This Matters
Visual smoothness directly impacts perceived performance. A site loading in 2 seconds with constant jank feels slower than one loading in 3 seconds but rendering smoothly throughout.
Key Takeaway: The FPS meter reveals when and why your interface stutters, helping you pinpoint which interactions need optimization to achieve the smooth 60 FPS experience users expect.