SEO

Website Speed & Core Web Vitals: Complete Guide for 2026

Is your website too slow? Discover how Core Web Vitals (LCP, INP, CLS) impact your SEO and conversions. Practical methods to optimise your website speed in Belgium.

Published
8 min
1,469words
#Core Web Vitals#website speed#LCP#INP#CLS#web performance#PageSpeed#SEO Belgium#optimisation

Why your website speed has become critical

In 2026, user patience is at an all-time low. 53% of mobile visitors leave a site that takes more than 3 seconds to load. For a Belgian SME, every extra second of loading time means lost customers — and lower Google rankings.

A site loading in 1 second shows a 40% conversion rate. At 3 seconds, it drops to 29%. Every second literally translates to lost revenue.

Google is making it clear: since the March 2026 core update, Core Web Vitals carry even more weight in rankings. Sites passing all three thresholds receive a cumulative visibility boost; failing even one metric creates a compounded penalty.

Core Web Vitals: the 3 metrics you must master

Core Web Vitals are three indicators Google uses to evaluate your visitors' real experience. Not a lab test — actual field data from real users.

LCP — Largest Contentful Paint (Loading)

LCP measures how long it takes to display the largest visible element on the page (often a hero image or main heading).
RatingThreshold
✅ Good≤ 2.5 seconds
⚠️ Needs improvement2.5 – 4 seconds
❌ Poor> 4 seconds
Common causes of poor LCP:
  • Uncompressed images or legacy formats (unoptimised JPEG/PNG)
  • Slow server response time (high TTFB)
  • Render-blocking CSS or JavaScript
  • Web fonts delaying text display

INP — Interaction to Next Paint (Responsiveness)

INP replaced First Input Delay (FID) in March 2024. It measures the delay between a user interaction (click, tap, keypress) and the visual update on the page.
RatingThreshold
✅ Good≤ 200 ms
⚠️ Needs improvement200 – 500 ms
❌ Poor> 500 ms
Common causes of poor INP:
  • Heavy JavaScript blocking the main thread
  • Too many third-party scripts (analytics, chat widgets, ads)
  • Complex event handlers on buttons/forms

CLS — Cumulative Layout Shift (Visual stability)

CLS measures unexpected element movements during loading. When a button "jumps" because an image loads above it — that's CLS.
RatingThreshold
✅ Good≤ 0.1
⚠️ Needs improvement0.1 – 0.25
❌ Poor> 0.25
Common causes of poor CLS:
  • Images without defined width/height dimensions
  • Ads or embeds inserting dynamically
  • Web fonts causing a Flash of Unstyled Text (FOUT)
  • Content injected above existing content

The direct impact on your business in Belgium

Impact on SEO

In 2026, only 47% of websites reach Google's "good" thresholds across all three metrics. Sites in position 1 on Google show a Core Web Vitals pass rate 10% higher than those in position 9. That's no coincidence.
Websites with excellent Core Web Vitals scores enjoy up to 40% better search visibility compared to those with poor scores.

Impact on conversions

The figures speak for themselves:

  • Bounce rate: 9% for sites loading in < 2s vs 38% for sites > 5s
  • Conversions: a 0.1-second improvement increases conversions by 8.4% in e-commerce
  • Revenue: one second of delay = 7% lost conversions (that's €7,000 per month lost for a site generating €100,000/month)

Mobile first

In Belgium, 75% of Google searches happen on mobile in 2025. Google now uses mobile scores as the primary ranking signal — including for desktop results. A slow site on smartphones gets penalised everywhere.

How to measure your Core Web Vitals

Google PageSpeed Insights

The go-to free tool: PageSpeed Insights. It shows your real scores (28-day field data) and lab scores, with actionable recommendations.

Google Search Console

In the "Core Web Vitals" report, Search Console classifies all your pages as good/needs improvement/poor. It's the ideal overview to prioritise your fixes.

Chrome DevTools (Lighthouse)

For developers: open DevTools (F12), Lighthouse tab, run a Performance audit. You'll get a score out of 100 and detailed technical recommendations.

10 practical actions to boost your speed

1. Optimise your images

Images account for an average of 50% of a page's weight. Immediate actions:
  • Convert to WebP or AVIF: WebP offers 25-35% better compression vs JPEG, supported by 97%+ of browsers. AVIF is even better but has less compatibility.
  • Resize: don't load a 4000px image if it displays at 800px.
  • Compress: use TinyPNG, Squoosh (Google), or ShortPixel. Aim for < 200 KB per image.
  • Lazy loading: add loading="lazy" to all images below the fold. Do NOT add it to hero/header images (it degrades LCP).

2. Choose performant hosting

Server response time (TTFB) is the foundation. A €3/month shared hosting plan won't deliver a good LCP. Prioritise:

  • Hosting with servers in Europe (ideally Belgium or the Netherlands)
  • A CDN (Content Delivery Network) for static files
  • HTTP/2 or HTTP/3 enabled

3. Minimise critical CSS and JavaScript

  • Inline critical CSS: embed the CSS needed for the first render directly in the <head>.
  • Defer/async: load non-essential scripts with defer or async.
  • Remove dead code: regularly audit unused CSS/JS (Coverage tab in Chrome DevTools).

4. Preload critical resources

Use <link rel="preload"> for elements that compose your LCP:
<link rel="preload" as="image" href="/hero-image.webp">
<link rel="preload" as="font" href="/fonts/main.woff2" crossorigin>

5. Define dimensions for all images and videos

To avoid CLS, every <img> and <video> must have explicit width and height attributes, or use aspect-ratio in CSS:
<img src="photo.webp" width="800" height="600" alt="Description" loading="lazy">

6. Optimise web fonts

  • Use font-display: swap to show text immediately with a fallback font.
  • Host fonts locally (avoid Google Fonts calls that add a DNS request).
  • Limit yourself to 2-3 font variants maximum.

7. Limit third-party scripts

Every third-party script (analytics, chat widget, ad pixels, social media) adds weight and blocks the main thread. Audit and remove what's not essential. For the rest, load them deferred.

8. Enable browser caching

Set aggressive Cache-Control headers for static files:
Cache-Control: public, max-age=31536000, immutable

Files with a hash in the name (style.a3f2c.css) can be cached indefinitely.

9. Use a CDN

A CDN distributes your files across servers close to your visitors. For a Belgian audience, a CDN with nodes in Brussels, Amsterdam, and Frankfurt significantly reduces latency.

10. Monitor continuously

Performance is not a one-off project. Set up ongoing monitoring:

  • Check PageSpeed Insights monthly
  • Configure alerts in Search Console
  • Test after every content or plugin update

Common mistakes to avoid

  • Heavy carousels/sliders: they degrade both LCP and CLS. Prefer a static hero image.
  • Autoplay videos: massive loading without interaction. Use a preview image with click-to-play.
  • Too many WordPress plugins: each plugin adds CSS and JS. 20+ plugins = guaranteed slow site.
  • Ignoring mobile: testing only on desktop hides the reality for 75% of your audience.
  • Lazy loading the LCP element: putting loading="lazy" on your hero image is counterproductive — it must load immediately.

FAQ — Frequently asked questions

Are Core Web Vitals really a Google ranking factor?

Yes. Google has confirmed them as a ranking signal since 2021. The March 2026 update reinforced their weight, introducing holistic scoring: passing all three thresholds gives a cumulative boost; failing even one creates a compounded penalty.

My site has a good Lighthouse score but a poor Search Console score — why?

Lighthouse is a lab test (ideal conditions). Search Console uses real user data (75th percentile over 28 days). If your visitors have slow connections or older devices, real-world scores will be lower.

How long does it take to see the impact of improvements?

Google collects data over 28 days. After your optimisations, expect 4 to 6 weeks before new scores appear in Search Console and influence your rankings.

Is WordPress too slow for good Core Web Vitals?

No, but you need to be methodical: lightweight theme, limited plugins, caching enabled (WP Rocket, LiteSpeed Cache), optimised images. A well-configured WordPress site can easily pass all three thresholds.

How much does a performance optimisation cost?

For a Belgian SME, a complete performance optimisation typically costs between €500 and €2,000 depending on site complexity. The ROI is quick thanks to improved conversions and Google rankings.

Conclusion: speed is not a luxury — it's a competitive advantage

In 2026, with only 47% of sites passing Core Web Vitals, optimising your speed places you in the top half — immediately. It's a measurable SEO advantage, a proven conversion boost, and a better experience for your Belgian visitors on desktop and mobile alike.

Don't let a slow website hold back your growth. Measure your scores today, prioritise high-impact actions, and turn performance into a competitive edge.

LeadCo

LeadCo Agency

Founder of LeadCo

Web developer and conversion expert based in Brussels. I build websites that turn your visitors into paying customers.

Discover our services

Need a website that converts?

Let’s discuss your project for free

Request a quote