FCP (First Contentful Paint)
Checks First Contentful Paint — when the first text or image appears. Target under 1.8s.
What this check measures
We read CrUX p75 FCP. Target: under 1.8s. FCP precedes LCP — if FCP is bad, LCP will be worse.
Why it matters
FCP is not a Core Web Vital directly but correlates with user perception of speed. Slow FCP usually means server/TTFB is slow or critical CSS is missing.
How our audit detects it
CrUX p75 FCP. Correlate with TTFB to identify server vs. client bottleneck.
Typical findings
- error_outlineFCP 3s+ — TTFB is bottleneck.
- error_outlineFCP 2.5s on CDN — critical CSS missing.
How to fix
If TTFB is high, fix server-side. If TTFB is fine but FCP is slow, inline critical CSS above-the-fold and defer non-critical styles.
Frequently asked questions
FCP vs LCP?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
LCP (Largest Contentful Paint)
Checks Largest Contentful Paint — how fast the main content appears. Target under 2.5s.
PerformanceCLS (Cumulative Layout Shift)
Checks Cumulative Layout Shift — how much the page jumps during load. Target under 0.1.
PerformanceINP (Interaction to Next Paint)
Checks Interaction to Next Paint — responsiveness to clicks/taps. Target under 200ms.
PerformanceTTFB (Time to First Byte)
Checks Time To First Byte — server response time. Target under 600ms.