Style Recalculation: When CSS Slows the Browser Down
Why style calculation costs time at runtime, how Selector Stats and Long Animation Frames make its share visible, and which changes actually shrink the scope.
This is page 4 of the posts from our blog. The newer posts are on the pages before.
Each post explains one topic. Below the title there is a short text about it. Click on a post. Then you can read the whole text.
The posts are on more than one page. Below the list you can choose another page.
Why style calculation costs time at runtime, how Selector Stats and Long Animation Frames make its share visible, and which changes actually shrink the scope.
A checkout cannot be cached away: why the five steps before an order need their own speed budgets, and where in your shop you should be measuring them.
Why the developer machine is the wrong yardstick, which reference device matches the 75th percentile and how both turn into a performance budget that holds.
Why anti-flicker layers push out Largest Contentful Paint, how to measure their share of the first paint and which setups carry a test without hiding the page.
How load time becomes a verifiable acceptance criterion: target value, method, data source and proof date per metric – and what German contract law makes of it.
Farewell events often fail to deliver the final measurement on mobile. How fetchLater() fixes that, which quota applies and what the fallback looks like.
How much CSS a page really needs, how to measure the unused share reliably and in which order to remove ballast without breaking the rendering.
TTFB only gives you the sum. The Server-Timing header breaks server time down in the browser into database, cache, application logic and template work.
The interface starts fast and turns sluggish after twenty minutes: how front-end memory leaks arise, how to measure them over time and how to get rid of them.