New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
A 200KB image sneaks into a pull request. Nobody notices until production Core Web Vitals tank.
What you'll have at the end
A pull-request check that runs Lighthouse against your real production build and fails the merge the moment load speed, image weight, or another Core Web Vitals number crosses the ceiling you set, the way it does the instant an oversized hero photo sneaks in.
You need
A pull-request pipeline that already runs on every incoming change, even if today it only runs your test suite, plus a command that turns your source into the exact files production serves.
Not covered
Diagnosing why one specific page misses a Core Web Vitals number in the first place, or setting up a pull-request pipeline where none exists yet.
Leans on
Get your LCP image downloading before anything else
when the load-speed ceiling keeps failing and the real cause is the image's loading order rather than its weight, fix that specific mechanism there instead of loosening this recipe's number.
Catch the React re-render hiding behind a slow INP
when the responsiveness ceiling keeps failing, the actual re-render culprit gets diagnosed there, not inside this recipe's build gate.
Checked 25 Aug 2026
Part of the Core Web Vitals and Performance Metrics cookbook