The time until the browser first renders qualifying content, such as text or an image.
First Contentful Paint records when the browser first displays qualifying content, such as text or an image, after navigation begins. It answers an early question: has something meaningful started appearing on the screen? It does not mean the main content is complete, the page is fully interactive or every resource has finished loading.
FCP and Largest Contentful Paint describe different points in the experience. A small piece of text can appear early while the large content block arrives much later. Looking at both can help distinguish a long blank opening from a page that begins drawing quickly but takes longer to show its substantial content.
For a business owner, the useful question is what the visitor actually sees at that first paint and what happens next. Improving an early measurement by displaying a token element does not necessarily make the page more useful. Review the loading sequence alongside the numbers so the diagnosis stays connected to the experience you want customers to have.
Takeaway: Use FCP to understand the beginning of visible loading, then check that useful main content and working controls follow promptly. Do not report it as the website’s total loading time.
Example
A photography studio’s page displays its name quickly but leaves the portfolio area empty while images are prepared. Its early contentful paint does not tell the whole story. The team watches the sequence and investigates when the actual portfolio becomes visible rather than declaring the page fast from the first number alone.
What to check
Keep the test environment and data source with the result. Compare FCP with response timing and LCP where available. If a change improves one measurement but makes the intended content harder to reach, investigate the trade-off before treating it as a successful optimization.
For more detail, see Web.dev FCP guide.