A slow website doesn't forgive: visitors leave, Google penalises you, and your credibility takes a hit. The good news is that most speed problems have concrete, measurable solutions.
Why speed matters so much
Website speed isn't just about comfort — it directly affects three growth levers. First: user experience. Past two to three seconds of loading time, a significant share of visitors close the tab; this is documented behaviour, not folklore. Second: conversion rate. The faster your site, the smoother the path to purchase or contact. Third: SEO. Google has incorporated Core Web Vitals into its ranking algorithm since 2021 — a slow site ranks lower, regardless of content quality.
What actually slows a site down
Before optimising, you need to know where to look. Here are the most common culprits:
- Unoptimised images: a 4 MB photo loaded full-page is often the main cause of a slow site. Without compression or modern formats (WebP, AVIF), every visit is an unnecessary download.
- Too many plugins and third-party scripts: every tool you add (chatbot, social widget, analytics tracker, ad pixel) loads extra resources — often invisibly from the interface.
- Underpowered hosting: a cheap shared server responds slowly, especially at peak times. Hosting is often the most overlooked variable.
- Bloated code: general-purpose CMS platforms like WordPress stack layers of code you only use 20% of. A custom-built site loads only what it needs.
- No caching: without a cache, every visitor forces the server to rebuild the same page from scratch.
Concrete levers to speed up your site
Once you've identified the causes, here are the actions to prioritise:
- Compress and convert images to WebP or AVIF format, sized to exact display dimensions.
- Enable lazy loading: off-screen images only load as the user scrolls — native in HTML with
loading='lazy'. - Choose fast hosting (dedicated server, VPS, or specialised provider) with a server geographically close to your visitors.
- Limit third-party scripts to the strict minimum, and defer them where possible.
- Set up a CDN (Content Delivery Network) to serve static assets from a server near each visitor.
- Enable browser and server-side caching to avoid regenerating pages on every request.
- Opt for lean, custom code rather than a bloated CMS — the approach we take at KELAP for the websites we build.
How to measure your site's speed
Two free tools are the standard reference. Google PageSpeed Insights (pagespeed.web.dev) analyses your URL and returns a score from 0 to 100, with precise recommendations ranked by impact. It's powered by Lighthouse, the Chrome diagnostic tool you can also run directly from your browser's DevTools.
The other essential reference is Core Web Vitals: three metrics Google measures on every indexed page.
- LCP (Largest Contentful Paint): time to render the largest visible element — ideally under 2.5 seconds.
- CLS (Cumulative Layout Shift): visual stability during loading — a score near 0 is the goal.
- INP (Interaction to Next Paint): responsiveness to user interactions — replaced FID in 2024, target under 200 ms.
Custom build vs template: the speed impact
Your site's architecture has a direct effect on performance. A site built on a general-purpose CMS loads dozens of unused CSS and JS files by default. A custom-developed site only loads what it actually uses. This is one of the reasons we advocate for the custom approach — something we cover in detail here: WordPress or custom site?. And if you want to go further on technical SEO, our SEO page details our approach.
Where to start?
Run an audit on PageSpeed Insights today — you'll have a clear picture in under two minutes. If the results are worrying, or if you'd like a deeper analysis of what's weighing on your performance, reach out and we'll take a look together.