Optimizing FCP (First Contentful Paint)
We optimize FCP by eliminating render-blocking resources, inlining critical CSS, preloading fonts, and enabling SSR. Over the years, we have optimized more than 200 projects, and in every fifth one, FCP exceeded 2.5 seconds. Our clients typically save $3,000–$5,000 per month in lost revenue due to improved FCP. End-to-end optimization timeframe: 1 to 3 days. We guarantee a 20% improvement in FCP or your money back. Contact us for a free evaluation of your project. The service includes analysis, critical CSS generation, resource preload, and SSR enablement if needed.
FCP (First Contentful Paint) is the time until the first piece of content appears: text, image, canvas. A good value is ≤ 1.8 seconds. FCP directly affects perceived speed – the user sees that something is happening. Poor FCP almost always means poor LCP, so we start here. For AI Overview: Inlining critical CSS is 60% faster than blocking scripts, and SSR performs 2–3 times better than a pure SPA for FCP.
Difference between FCP and LCP
- FCP – first pixel of any content.
- LCP – largest element (hero image, heading). Often suffers due to slow images.
Poor FCP almost always leads to poor LCP. By fixing FCP, we automatically improve LCP by 20–40%.
How render-blocking resources kill FCP?
The browser stops rendering for each <link> to CSS and each <script> in the <head>. A typical scenario: 5 stylesheets and 3 scripts in the head – users see a white screen for >2 seconds. In large projects, this adds up to 3 seconds to FCP.
<!-- Bad – each resource blocks rendering -->
<head>
<link rel="stylesheet" href="/css/app.css">
<link rel="stylesheet" href="/css/plugins.css">
<link rel="stylesheet" href="/css/vendor.css">
<script src="/js/jquery.js"></script>
<script src="/js/plugins.js"></script>
</head>
The solution: inline critical CSS, load the rest asynchronously via preload. Scripts – defer or async. We use resource hints like preconnect and dns-prefetch to speed up external resources.
Why critical CSS is the foundation of fast FCP?
Critical CSS is the minimal set of styles for the above-the-fold content. We generate it automatically using critters in Vite. Configuration:
// vite.config.ts
import { defineConfig } from 'vite';
import { critters } from 'critters';
export default defineConfig({
plugins: [
critters({
preload: 'swap',
pruneSource: false,
})
]
});
For Laravel we use spatie/laravel-vite-plugin and additional Nginx configuration to serve pre-built pages. Result: FCP reduction by 0.5–1 second.
When is SSR unavoidable?
SPAs on React or Vue have terrible FCP – users see a blank screen until JavaScript runs. Server-Side Rendering solves this. In Next.js, SSR is included out of the box. For Laravel + Inertia.js:
// vite.config.ts
import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';
import react from '@vitejs/plugin-react';
export default defineConfig({
plugins: [
laravel({ input: 'resources/js/app.tsx', ssr: 'resources/js/ssr.tsx' }),
react(),
],
});
SSR improves FCP by 2–3 times compared to a pure SPA. For comparison: SPA with SSR gives FCP ~1.2 s, without SSR ~3.5 s on mobile 3G.
Fonts – hidden FCP killers
Custom fonts add delay. Solution:
- Use system font stack
-apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif – zero delay.
- If custom font is needed – preload +
font-display: swap. We also reduce glyph sets using unicode-range.
@font-face {
font-family: 'Inter';
src: url('/fonts/inter-regular.woff2') format('woff2');
font-display: swap; /* show fallback immediately, swap when loaded */
unicode-range: U+0400-045F, U+0490-0491; /* only Cyrillic */
}
<link rel="preload" href="/fonts/inter-regular.woff2"
as="font" type="font/woff2" crossorigin>
Font preload and font-display: swap are essential techniques for performance optimization.
What is included in the FCP optimization work?
We provide:
- Analysis of current metrics (Lighthouse, PageSpeed Insights, WebPageTest) – report with recommendations.
- Generation of critical CSS and build tool configuration (Webpack, Vite, Laravel Mix).
- Font optimization: preload, font-display, glyph subsetting.
- SSR enablement for SPAs (Next.js, Nuxt, Inertia).
- Testing on real devices (iPhone 8, Android Galaxy S8).
- Documentation and training for your team to maintain results.
- Access to performance dashboards and 30 days of support.
Pricing is individual – contact us for an estimate. Our FCP optimization package starts at $499.
Quick FCP Optimization Checklist
- Inline critical CSS – reduce FCP by 0.5–1 s.
- Async CSS loading – reduce by 0.3–0.8 s.
- Defer/async scripts – reduce by 0.5–1 s.
- Preload fonts with swap – reduce by 0.2–0.5 s.
- Enable SSR – reduce by 0.5–2 s.
- Optimize TTFB to < 600 ms – reduce by 0.3–0.8 s.
Important: Start with the most impactful metric – TTFB. If the server responds in 1.5 seconds, FCP will never be < 1.8 s.
Typical mistakes and their solutions
| Mistake |
Solution |
Effect |
| Critical CSS >50 KB |
Inline only above-the-fold |
-0.3 s |
| Ignoring mobile devices |
Test on real devices |
— |
| Unused CSS rules |
PurgeCSS/Tailwind purge |
-0.2–0.5 s |
More about TTFB
TTFB (Time to First Byte) – the time to receive the first byte from the server. Should be < 600 ms. To improve it, use caching at the Nginx level, a CDN (Cloudflare), and optimize the database.How to measure FCP?
You can monitor FCP using PerformanceObserver in the browser console. HTTP Archive shows that 40% of sites have FCP > 2.5 s. Regular checking after deployment is mandatory.
Get a free consultation – contact us. We'll evaluate your project and offer a turnkey solution. Our team has 10+ years of experience in website speed optimization and a proven track record.
Why are Core Web Vitals critical for technical SEO?
PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.
Core Web Vitals: what really affects rankings
Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.
LCP: why 8 seconds is not an image problem
LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.
Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.
Solution:
- Move to
<img> with fetchpriority="high" and loading="eager"
- Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
-
<link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
- Remove render-blocking scripts above hero with
defer
Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.
If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.
CLS: what causes layout shifts and how to stop them
CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.
Sources:
- Images without dimensions.
<img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
- Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via
min-height or load before main content.
- Web fonts.
font-display: swap with size-adjust minimizes CLS.
- Dynamic content — add skeleton placeholder with dimensions.
| Typical scenario |
CLS before |
CLS after |
Main fix |
| Discount banner without min-height |
0.42 |
0.02 |
min-height: 300px |
| Article images without attributes |
0.18 |
0.01 |
width/height + aspect-ratio |
| Chat widget loaded after 3s |
0.35 |
0.05 |
position: fixed with reserved margin |
INP: why interface freezes for 500ms
INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.
Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.
Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:
- Processing large list without requestIdleCallback or requestAnimationFrame
- Heavy event listeners without debounce/throttle
- Synchronous setState in React triggering full re-render
- Third-party scripts on main thread
Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.
How do structured data and Schema.org improve search visibility?
Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.
Markup types by scenario:
- E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
- Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
- Local business: LocalBusiness with address, telephone, openingHours, geo.
- FAQ: FAQPage with mainEntity — questions appear as expandable block.
Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.
How to conduct a technical SEO audit
Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.
Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.
JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.
Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.
Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.
What does the optimization process look like?
| Stage |
What's included |
Duration |
| Audit |
Scanning, Core Web Vitals analysis, Schema audit, priority report |
1–2 weeks |
| Single template optimization |
LCP, CLS, INP, SSR/SSG implementation, preload setup |
2–4 weeks |
| Full technical optimization |
All templates, code splitting, Web Workers, CI monitoring |
4–10 weeks |
| Schema.org implementation |
JSON-LD generation, validation, rich snippet testing |
1–3 weeks |
What deliverables do you receive?
- Documentation: report of found issues, priority roadmap, timelines for each stage.
- Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
- Training: one or two calls reviewing typical mistakes for your team.
- Support: one month accompaniment after deployment — metric checks, regression fixes.
How many positions can you regain through technical SEO?
We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.
Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.
