Website Speed and Core Web Vitals: Why They Matter for Conversions

Published Echipa indev
Website Speed and Core Web Vitals: Why They Matter for Conversions

On mobile devices — where over 70% of traffic originates for most service businesses — visitors decide within the first 2 to 3 seconds whether to stay on your page or bounce back to Google. Poor loading speed is not just a technical detail for developers: it directly lowers form completion rates, hurts Google Ads Quality Score, and caps organic SEO growth.

1. Why page speed directly affects your marketing budget

Whether you invest in Google Ads, Meta Ads, or SEO, you pay for every click that reaches your landing page. If a visitor stares at a blank screen for 3–4 seconds on an average 4G connection, a large share will abandon the tab before your lead form even renders. Google also incorporates Page Experience signals into both organic rankings and paid landing page evaluations.

2. What Core Web Vitals measure and Google’s official thresholds

Google measures real-world user experience through three primary Core Web Vitals metrics, supported by server response time (TTFB):

Metric What it measures Good (Green) Needs Improvement
LCP (Largest Contentful Paint) Time until the main above-the-fold content (headline or hero image) renders ≤ 2.5 seconds 2.5s – 4.0s
INP (Interaction to Next Paint) Responsiveness of the UI to clicks, taps, and keyboard input ≤ 200 milliseconds 200ms – 500ms
CLS (Cumulative Layout Shift) Visual stability — avoiding unexpected layout jumps during load ≤ 0.1 0.1 – 0.25
TTFB (Time to First Byte) How fast the server delivers the first byte of the HTML response ≤ 800 milliseconds 800ms – 1.8s

3. Optimizing images and above-the-fold media

Across most website audits we run, unoptimized images are the single biggest cause of slow LCP scores. A 2 MB hero photo uploaded straight from a camera can stall mobile rendering for seconds.

  • Modern AVIF and WebP formats: Use the HTML <picture> element to serve high-efficiency AVIF with automatic WebP fallback.
  • Responsive sizing (srcset and sizes): Mobile phones should never download a 1920px desktop banner for a 390px viewport.
  • Explicit width and height attributes: Lets the browser reserve exact space before download, keeping CLS at zero.
  • Hero image priority: Give the primary hero image fetchpriority="high" without lazy loading, while applying loading="lazy" to below-the-fold images.

4. Critical CSS, lean JavaScript, and main-thread hygiene

Even a fast server produces a sluggish page if the browser must download and parse hundreds of kilobytes of blocking CSS and JavaScript before first paint:

  1. Inline critical CSS & pruned stylesheets: Above-the-fold styles render immediately while non-critical CSS stays lean and purged of unused rules.
  2. Removing heavy legacy libraries: Redundant sliders, animation bundles, and unthrottled third-party scripts block the main thread and degrade INP.
  3. Self-hosted WOFF2 fonts: Hosting variable WOFF2 subsets locally with font-display: swap removes external DNS handshakes and layout shifts.

5. Server infrastructure, caching, and compression

  • Enable Brotli or Gzip compression for HTML, CSS, JS, SVG, and JSON responses.
  • Serve hashed static assets with Cache-Control: public, max-age=31536000, immutable.
  • Keep backend TTFB under 200ms with PHP OPcache and clean database queries without N+1 bottlenecks.

6. How to benchmark your site today

Run your key landing pages through Google PageSpeed Insights and review the Core Web Vitals report inside Google Search Console. Focus on mobile metrics first, as Google evaluates and indexes websites using mobile-first indexing.

Frequently asked questions

What is a good Google PageSpeed Insights score?

A mobile score between 90 and 100 indicates a fast technical foundation that supports both organic SEO rankings and paid campaign ROI.

Are AVIF images supported across modern browsers?

Yes — over 95% of browsers support AVIF natively, and wrapping images in an HTML <picture> element provides seamless WebP fallback.

Why is my Desktop score 95 while Mobile is 50?

Mobile testing simulates a mid-tier CPU and throttled 4G network, where large JavaScript bundles and unoptimized images heavily penalize LCP and INP.

How long does Core Web Vitals optimization take on an existing site?

Depending on the codebase and platform, image, caching, and script optimizations typically take from a few days up to 1–2 weeks after a technical audit.

Related articles

Let’s discuss what could work better.

Tell us where your business is now and what you want to change. We start with context rather than a list of technologies.