A slow site costs customers, not just seconds. The visitor who waits doesn't wait long: they go back and click the next competitor. Speed is now measured with three indicators defined by Google, the Core Web Vitals, and fixed with a handful of targeted actions: lighter images, sorted scripts, serious hosting. You need to know what you're measuring, what it costs, and where to start.
The orders of magnitude are known: according to Google, the probability of a bounce increases by 32% between 1 and 3 seconds of loading. And Deloitte's Milliseconds Make Millions study showed that a gain of 0.1 second on mobile raises conversions by 8.4% in online commerce.
According to a Google study, 53% of mobile visits are abandoned when a page takes more than 3 seconds to load
Why a slow site drives your customers away
Slowness acts on three levels. The first impression: a laborious load evokes a dirty storefront. Friction: every wait in a journey gives a chance to abandon. Visibility: Google factors page experience into its ranking; with equivalent content, the fast site starts with an advantage.
An asymmetry to understand: you view your site on a good computer, with a cached version. Your prospects arrive on a mid-range smartphone, on 4G on a train. It's for that reality you must optimize, and it's that reality Google's tools measure.
Core Web Vitals: the three measures that matter
The Core Web Vitals are the three indicators Google uses to grade your visitors' real experience, measured on real Chrome users, not in a lab.
LCP: perceived display speed
The Largest Contentful Paint measures the time to display the largest visible element of the page, often an image or a title. Threshold set by Google: 2.5 seconds maximum. It's the most telling indicator: the moment the visitor feels that “the page is here”.
INP: responsiveness to clicks
The Interaction to Next Paint measures the delay between a visitor's action — click, menu, input — and the page's visible reaction. Integrated into the Core Web Vitals on 12 March 2024 in place of FID, it evaluates all interactions. Threshold: 200 milliseconds maximum. A site that “lags” when you click fails here.
CLS: visual stability
The Cumulative Layout Shift measures layout jumps during loading: that button that slips away under your finger because a banner pushes the content. Threshold: 0.1 maximum. It's the indicator of irritation and missed clicks.
The common causes of a slow SME site
In audits of Belgian sites, the same suspects keep coming back:
Images that are too heavy: the photo straight out of the camera, several megabytes, displayed in a 400-pixel block. The number-one cause, and the simplest to fix.
The accumulation of scripts: chat, advertising pixel, videos, modules added over the years. Each seems harmless; together, they smother the page.
Cut-price hosting: a saturated shared server adds its delay before the page is even built.
Superfluous animations and carousels: spectacular in a demo, costly for INP, rarely useful for conversion.
The absence of caching: every visit recalculates what could be served instantly.
Speeding up concretely: where to start?
Resize and compress all images, and adopt modern formats like WebP: often half the problem solved in a day.
Defer what isn't essential: chat, analytics, video can load after the content, not before.
Remove unused modules and widgets: the annual inventory often gains more than any fine-tuning.
Reserve space for images and banners so nothing jumps during loading (that's the whole of CLS).
Choose hosting with servers in Europe and a content delivery network: distance is paid in milliseconds.
Measure before, during, after
Two free tools are enough. PageSpeed Insights gives the snapshot: real visitor data and fixes ranked by impact. Search Console tracks the evolution of the Core Web Vitals page by page. Always measure the mobile version as a priority: that's where most of the traffic plays out.
A point of attention: speed is mostly won at the design stage. A light structure, images sized from the start, features chosen rather than stacked: it's the approach we apply in our website creation in Belgium projects. Catching up a badly built site always costs more than building well.
Frequently asked questions
How do I know if my site is slow without being a technician?
Open PageSpeed Insights, enter your site's address and look at the “Core Web Vitals” section in the mobile version. If LCP, INP and CLS are green, you're within bounds. Complete it with a real-world test: your site, on your phone, on 4G, in private browsing.
Speed is mostly an e-commerce topic, isn't it?
No. The Deloitte study also measured lead-generation sites: for 0.1 second gained, the bounce rate improved by 8.3%. For a showcase site, slowness is paid for in forms never sent and calls never made.
Do I have to rebuild the whole site to make it fast?
Not necessarily. Images, scripts, cache and hosting are fixed on an existing site and resolve the majority of cases. If the structure itself is at fault — an obese theme, code accumulated over years — the redesign becomes the most economical option over time.
Priority action plan
Measure: run your five most-visited pages through PageSpeed Insights, mobile version, and note the three indicators.
Lighten the images: resizing to real dimensions, compression, WebP format.
Inventory the scripts and remove or defer everything that doesn't directly serve the visitor.
Check the hosting: servers in Europe, active caching, a content delivery network if your audience justifies it.
Web speed isn't a topic for technicians, it's a revenue topic. Google's thresholds give the heading, the free tools the diagnosis, and most fixes are resolved in a few days. Your visitors will never tell you your site is slow: they'll leave without a word. Better to know before they do.
If simple fixes are no longer enough, our website creation service builds in performance from the design stage, rather than catching up afterwards.
Website
November 4, 2025
5 min read
