Jank

Also called stutter or dropped frames

Visible stutter in an animation or scroll, caused when the browser misses frames because it cannot finish its work in time.

What is Jank?

Jank is the hitch you notice when motion freezes for a moment and then skips ahead. Each frame has a deadline, about 16.7ms on a 60Hz screen. When the browser misses it, the old frame stays on screen, and the next one jumps to catch up.

Common causes are long JavaScript tasks on the main thread, animating properties that trigger layout such as width, top, or left, expensive paints like large blurs and shadows, and decoding big images in the middle of an animation.

To find it, record the interaction in the Performance panel of Chrome DevTools: dropped frames show up in the Frames track, and long tasks get a red marker. Fix it by animating transform and opacity, breaking long tasks into smaller pieces, and moving heavy work out of the moment the animation runs.

Steady motion feels better than motion that alternates between fast and frozen, so a consistent frame rate matters as much as a high one.

Often confused with

Frame rate (FPS)
Frame rate is how many frames arrive each second on average. Jank is the uneven gaps, when some frames arrive late or not at all.
All terms

Frame rate (FPS)

The number of frames a screen draws each second; around 60 fps, motion looks smooth, and at lower rates it starts to look choppy.

Layout thrashing

A slowdown caused by code that alternates style changes with size reads, forcing the browser to recalculate layout many times in one frame.

GPU acceleration

A browser technique where the graphics chip moves, fades, or scales an element on its own layer instead of redrawing the page every frame.

Perceived performance

How fast an app feels to people, which skeleton screens, instant feedback, and progressive loading can improve even when the real wait stays the same.