Google made Core Web Vitals an official ranking factor in 2021. Since then, every SEO article has told you to care about them — and almost none have explained what they actually mean for a furniture shop in Kirchberg or a law firm in the Cloche d'Or.
This guide skips the developer jargon. We'll explain what each metric measures, what "good" looks like, and — based on 32 audits we've run on Luxembourg SME websites — which five issues come up almost every time.
What are Core Web Vitals, actually?
Core Web Vitals are three measurements Google uses to assess how a page feels to real users. Not whether your code is clean. Not whether you have keywords in the right places. Whether the page loads fast and doesn't jump around while someone's trying to use it.
Google uses data from real Chrome users to score your site — that's called the Chrome User Experience Report (CrUX). If enough real visitors have loaded your site recently, Google knows how fast it actually is for them. That data feeds directly into your rankings.
LCP — Largest Contentful Paint
This measures how long it takes for the biggest visible element on the page to load. For most SME sites, that's either a hero image or a large heading. A good LCP score is under 2.5 seconds. Over 4 seconds is "poor" — and you will rank lower than a competitor who has solved it.
The most common LCP culprit on Luxembourg SME sites: a large, unoptimised hero image uploaded at 4MB from a smartphone. Compressing it and serving it in modern WebP format is often enough to halve the LCP time.
CLS — Cumulative Layout Shift
This measures how much the page visually jumps as it loads. You've experienced this: you're about to tap a button, and an image loads above it and shoves everything down — so you tap the wrong thing. Google penalises sites that do this to users. A good score is under 0.1.
CLS is almost always caused by images or embeds without defined dimensions. If your HTML doesn't tell the browser how tall an image is before it loads, the browser has to guess — and guesses wrong, causing a layout shift.
INP — Interaction to Next Paint
INP replaced FID (First Input Delay) in 2024. It measures how quickly the page responds after a user taps or clicks — any interaction, not just the first one. A good INP score is under 200ms. Slow INP usually means too much JavaScript running on the main thread.
The business version: if your site scores "poor" on any of these three metrics, you are being outranked by a competitor with a similar site who just fixed their images. That's the stakes.
The 5 issues we find on almost every Luxembourg SME site
After 32 audits, the same problems appear with remarkable consistency. Here they are, in order of how often we see them.
1. Unoptimised hero images
The most common LCP killer. A homepage hero image uploaded straight from a camera or Canva export — often 3–6MB, often PNG, often not resized for web. Fix: compress to WebP, serve at the right resolution (typically 1440px wide maximum), add a width and height attribute so the browser can allocate space before the image loads.
How much it matters: we've seen LCP drop from 8.2 seconds to 1.6 seconds just by replacing the hero image with an optimised version. That's a PageSpeed score jump from 34 to 87.
2. No image dimensions set
Every image that loads without a declared width and height is a potential CLS event. The fix is two attributes in your HTML: width="800" height="600". That's it. The browser can now reserve the correct space and nothing shifts when the image arrives.
3. Render-blocking scripts and fonts
Most WordPress and Wix sites load 8–15 scripts in the <head> — analytics, chat widgets, cookie banners, social plugins — all blocking the page from rendering until they've loaded. Combine this with Google Fonts loaded without preconnect, and you've added 1–2 seconds to every page load before the user sees anything.
Quick fixes: move non-critical scripts to load asynchronously or defer them; add <link rel="preconnect" href="https://fonts.googleapis.com"> before your font stylesheet; use a cookie banner that loads after the rest of the page, not before it.
4. No mobile-specific layout
A desktop layout squeezed into a phone screen is not a mobile layout — it's a zoomed-out desktop layout. We still see this on Luxembourg sites built in 2019–2022 using older WordPress themes. The result: text too small to read, tap targets too close to hit, horizontal scrolling, and a CLS disaster as the desktop layout reflows.
This is the one issue that can't be fixed with a line of CSS. It requires a proper responsive layout — which is why our Quick Refresh and Full Rebuild packages both prioritise mobile as the primary build target, not an afterthought.
5. SSL missing or mixed content
HTTPS has been a ranking signal since 2014. In 2026, we still audit Luxembourg sites serving over HTTP — or serving the page over HTTPS but loading images over HTTP (called "mixed content"), which triggers browser security warnings. Both cases result in an SEO penalty and a trust signal problem. SSL certificates are free; there is no reason not to have one.
Want to see your exact scores? Open Chrome DevTools (F12), go to the Lighthouse tab, and run an audit on your homepage. Or paste your URL into pagespeed.web.dev for Google's live report. If any metric shows red, it is affecting your rankings today.
What should a Luxembourg SME actually do?
If you're not a developer, the honest answer is: either fix the issues above yourself (the image issues are doable), or get a professional audit first.
Here's what we recommend:
- Run your site through PageSpeed Insights (pagespeed.web.dev) and screenshot the results
- If LCP is over 2.5s, check your hero image first — size, format, compression
- If CLS is over 0.1, check whether your images have width/height attributes
- If you're on WordPress, deactivate plugins one at a time and re-run the test to find the script offenders
- If INP is over 200ms and you're not a developer, this likely needs professional work
If fixing these yourself isn't realistic, our free site audit includes a full Core Web Vitals breakdown with specific, prioritised recommendations — no technical knowledge required to understand it.
The bottom line
Core Web Vitals are not a developer problem. They are a business problem: slow sites lose rankings, lose visitors, and lose revenue. The good news for Luxembourg SMEs is that your local competitors are mostly in the same boat. The sites that fix these issues first will take the rankings.
We've seen it happen 32 times.