Performance metric
What is FCP?
First Contentful Paint measures when the browser first renders text, an image, an SVG, or another visible piece of content. It is the first sign that the page is not blank.
Plain-English version
When the first text or image appears.
Target
Under 1.8s
FCP thresholds
Use thresholds as a triage tool. Field data matters most when there is enough real Chrome traffic for the page.
Good
≤ 1.8s
Needs work
1.8–3s
Poor
> 3s
Why it matters
What a visitor feels when FCP is bad.
Why FCP matters
FCP shapes the first impression. A page with a slow FCP feels blank even if the rest of the content eventually loads quickly.
What a poor result usually means
A poor FCP often means slow server response, render-blocking CSS, too much JavaScript before rendering, large fonts, or a page shell that waits too long before showing content.
nimo audit lens
How nimo reads FCP in an audit.
The glossary explains the metric. The free audit checks the page, separates field data from lab diagnostics, and points at the first review step.
How nimo interprets it
nimo treats FCP as blank-screen risk. It answers when the page first proves that something is loading.
Source to trust first
Use lab diagnostics to find render-blocking causes quickly. Compare CrUX FCP when enough field data exists.
Evidence to inspect
- TTFB before the browser can render anything.
- Render-blocking CSS and early JavaScript.
- Font loading that delays visible text.
- Client-rendered shells that wait before showing content.
First fix to review
Make above-the-fold text or shell content render without waiting on non-critical CSS, JavaScript, or late data.
How to validate
Rerun the same audit and confirm first content appears earlier without causing an LCP or CLS regression.
What to fix first
Do not chase the score. Fix the bottleneck.
The right fix depends on the metric, the page template, and whether the issue appears in real visitor data.
- Improve TTFB before optimizing later rendering steps.
- Inline critical CSS and defer non-critical styles.
- Load essential fonts efficiently and avoid blocking the first render.
- Reduce JavaScript that runs before the first paint.
- Avoid blank loading shells for content that can render immediately.
How nimo helps
Run the free audit, then ask: “How can I make my page render faster?”
nimo helps explain whether visitors see a blank screen because of the server, CSS, JavaScript, or all three.
No signup needed. Takes about 30 seconds.