First Contentful Paint (FCP) measures the time from when a user requests a page until the browser renders the first piece of content — text, an image, an SVG, or a non-blank canvas. It is reported by both Lighthouse and the Chrome User Experience Report, and sits early in the loading timeline.
Why it matters
FCP is the moment users stop staring at a blank screen, so it shapes perceived speed long before the page is fully usable. web.dev classifies an FCP under 1.8 seconds as good and over 3.0 seconds as poor. A slow FCP usually points to render-blocking resources or a slow server, and it tends to drag LCP along with it — fixing FCP often improves the whole loading sequence. Unlike Core Web Vitals, FCP is not used directly for ranking, but a poor FCP almost always coincides with poor field metrics that are.
How to fix
- Reduce server response time so TTFB stays under 800 ms.
- Inline critical CSS and defer or async non-essential stylesheets and scripts.
- Preload key fonts and use
font-display: swapto avoid invisible text. - Strip render-blocking third-party tags from the document head.
- Serve compressed, modern image formats and prioritise the hero image.
- Compare runs in Lighthouse to confirm fixes hold across builds, then validate against lab data trends.