Site Speed Optimization (Core Web Vitals)

Imagine: your site loads in 5 seconds, but LCP is 4.5 s. Google already marks the page as slow, and traffic drops by 20%. We've encountered this dozens of times: the culprit is not the hosting but an unoptimized hero element, slow TTFB, or render-blocking CSS. Our team has optimized Core Web Vitals for over 200 projects with 7+ years of experience, delivering green metrics on any stack. In this article, we break down how to improve LCP, INP, and CLS using modern techniques. You'll learn which tools track progress and how much time a typical optimization takes. No magic wands—only precise server config, preloads, and font optimization. Every second of delay reduces conversion by 7%, and Core Web Vitals optimization can boost it by 10–15%. Speed and Google Page Experience compliance are mandatory for competitiveness.

Three metrics and target values

INP replaced FID. FID measured only the first interaction; INP measures all interactions. More details in the MDN documentation.

Core Web Vitals optimization strategy

When should you consider optimization?

If at least one metric falls into the red zone, you lose up to 20% of traffic. Green metrics give an advantage in ranking. This is especially important for e-commerce: every second of delay reduces conversion by 7%. Google research shows that 53% of mobile users leave if loading takes longer than 3 seconds.

Why is LCP the main metric?

LCP is the moment when the largest element (usually a hero image or H1) appears on screen. The main causes: missing preload, slow TTFB, render-blocking CSS/JS, and unoptimized images. Preloading the LCP image is 2 times more effective than simply optimizing images.

<link rel="preload" as="image" href="/images/hero.webp"
      imagesrcset="/images/hero-400.webp 400w, /images/hero-800.webp 800w, /images/hero-1200.webp 1200w"
      imagesizes="100vw">

<img src="/images/hero.webp" fetchpriority="high" loading="eager"
     width="1200" height="630" alt="LCP optimization">

How does INP affect user experience?

INP measures the delay between a user action and the next paint. Poor INP indicates an overloaded main thread. Techniques:

async function processLargeList(items) {
    for (let i = 0; i < items.length; i++) {
        processItem(items[i]);
        if (i % 50 === 0) {
            await new Promise(r => setTimeout(r, 0));
        }
    }
}

import { startTransition } from 'react';

function handleSearch(query) {
    setInputValue(query);
    startTransition(() => {
        setSearchResults(filterResults(query));
    });
}

CLS: layout stability without surprises

CLS is the sum of element shifts during loading. Each shift irritates users and reduces conversion. Solutions:

<img src="photo.webp" width="800" height="600" alt="layout stability">
<style>
.hero-image {
    aspect-ratio: 16 / 9;
    width: 100%;
}
</style>

@font-face {
    font-family: 'Inter';
    font-display: optional;
    src: url('/fonts/inter.woff2') format('woff2');
}

Measurement and monitoring tools

import { onCLS, onINP, onLCP, onFCP, onTTFB } from 'web-vitals';

function sendToAnalytics({ name, value, rating, id }) {
    gtag('event', name, {
        event_category: 'Web Vitals',
        event_label: id,
        value: Math.round(name === 'CLS' ? value * 1000 : value),
        non_interaction: true,
        custom_map: { metric_rating: rating }
    });
}

onCLS(sendToAnalytics);
onINP(sendToAnalytics);
onLCP(sendToAnalytics);
onFCP(sendToAnalytics);
onTTFB(sendToAnalytics);

How we optimize Core Web Vitals: step-by-step plan

1. Audit all pages via PageSpeed Insights, CrUX, and Lighthouse.
2. Identify quick wins (preload, sizes, fonts) and deep issues (JS optimization, server delays).
3. Implement changes by priority impact on LCP, INP, CLS stabilization.
4. Monitor in real time after deployment.
5. Document results and recommendations.

What's included in the work

• Full Core Web Vitals audit with a report for each page.
• Elimination of blocking resources, image and font optimization.
• Server caching and CDN configuration if needed.
• JavaScript optimization (breaking long tasks, lazy loading).
• Providing ready-made code with comments for your team.
• Monitoring metrics for 3 months and adjustments.

Work process

• Audit: analysis of all pages, identifying bottlenecks.
• Implementation: making code changes, configuring server caching.
• Monitoring: tracking via CrUX and web-vitals after deployment.
• Warranty: documentation and support of green metrics for 3 months.

Timeline and cost

Typical Core Web Vitals optimization takes 2 to 4 weeks. Cost is calculated individually after the audit, typically ranging from $500 to $2000. Our turnkey optimization includes a free initial audit. Write to us: we will evaluate your project and provide a detailed plan.

Order a free Core Web Vitals audit to get an exact optimization plan and timeline. Get a consultation from our engineer on your metrics.

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:

1. Move to <img> with fetchpriority="high" and loading="eager"
2. Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
3. <link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
4. 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.

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?

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.