Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize first contentful paint. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | -9% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 25% | 0% |
| case-04 | ✓→✗ | ▼ Worse | -6% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -15% | 0% |
| case-05 | ✓→✓ | = Same ✓ | 9% | 0% |
FCP is the first visual signal that a page is loading—fast FCP reassures users that the site is responding, reducing perceived wait time and bounce rates.
Measure FCP using Lighthouse or PageSpeed Insights. Verify first content appears within 1.8 seconds.
Optimize FCP by eliminating render-blocking resources, inlining critical CSS, and reducing server response time.
Explain how FCP measures the time until the first text or image is painted, indicating page load has begun.
Review the routes, assets, and loading behavior that affect Optimize first contentful paint. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/performance/first-contentful-paint
Other measured skills in the registry, with their headline benchmark lift.