See what blocks the first paint
Most slow first paints come down to the same few files. Toggle the fixes and watch First Contentful Paint move on a simulated slow phone.
Twelve fixes, ordered by how often they make the biggest difference. Tick them off as you go; your progress stays in this browser.
0 of 12 done
Most slow first paints come down to the same few files. Toggle the fixes and watch First Contentful Paint move on a simulated slow phone.
First Contentful Paint ≈ 1.9 s → Needs improvement
Magenta bars block rendering: the browser won't paint until they finish. Simplified model of a mobile load with 600 ms server response; real pages have more files, but the rule is the same.
Run the speed test first and look at “What to fix first”: Lighthouse ranks opportunities by estimated time saved on your actual page. Fix the failing Core Web Vital before chasing the score, and fix mobile before desktop. For a step-by-step plan for your platform, use the fix-plan button on the results.
On most sites: compress and properly size images (especially the hero image), defer non-essential JavaScript and third-party tags, and cache HTML at a CDN. Those three usually fix LCP and TBT together.
Not always. On WordPress, a caching plugin, an image optimisation plugin and removing unused plugins cover a lot. On Shopify, removing unused apps and oversized theme images helps most. Structural fixes, such as JavaScript bundle size, need a developer.
Studies published on web.dev by companies including Vodafone and Rakuten 24 linked Core Web Vitals improvements to higher sales and conversion rates. The effect varies by site, so measure your own before and after.