Short answer: most slow websites are slow for the same few reasons: oversized images, too many third-party scripts and plugins, slow hosting, and pages that shift around while they load. Test your site with Google PageSpeed Insights on mobile, then fix things in this order: images, the main (largest) element at the top of the page, unnecessary scripts, caching and hosting, and finally layout shifts and slow interactions. Those steps fix the large majority of speed problems.
Why speed matters
Speed affects whether visitors stay and whether they buy. A study by Google and Deloitte, Milliseconds Make Millions, linked a 0.1-second improvement in mobile site speed to an 8.4% increase in retail conversions. Google also uses page experience signals, including Core Web Vitals, in its search systems. And many sites still have room to improve: the HTTP Archive's 2025 Web Almanac found that fewer than half of mobile sites pass all three Core Web Vitals.
What Core Web Vitals measure
Google's Core Web Vitals are three numbers, measured on real visitors' devices:
- Largest Contentful Paint (LCP): how quickly the main content appears. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds to a tap or click. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the page jumps around while loading. Good is 0.1 or less.
How to test your site (free)
- PageSpeed Insights: enter a URL and look at the mobile tab. The top section shows real-visitor data when Google has enough of it; the lab test below lists specific problems.
- Google Search Console → Core Web Vitals: shows which groups of pages pass or fail across your whole site.
- Your own phone on mobile data: load your key pages away from office Wi-Fi. It is the experience most of your visitors get.
Test your homepage, a main service or product page, and a blog post, because each is built differently.
The fixes, in order
1. Shrink and convert images
Images are usually the biggest files on a page. Resize them to the largest size they are actually shown at, and use modern formats such as WebP or AVIF. On the websites we build, uploads are converted to WebP and capped at a sensible size automatically, so editors can't slow a page down by uploading a huge photo.
2. Make the main element load first
The largest element at the top of the page (often a hero image or heading) decides your LCP. Don't lazy-load it, give it fetchpriority="high" if it is an image, and make sure it is not hidden behind a slider or animation that waits for scripts. Google's guide to optimising LCP covers the details.
3. Cut third-party scripts and plugins
Chat widgets, tracking pixels, sliders, popup tools and unused plugins all add code that competes with your content. List every script and plugin, remove what you don't use, and load the rest after the main content.
4. Turn on caching and a CDN
Caching stores ready-made pages so they don't have to be built for every visitor, and a content delivery network (CDN) serves them from a location close to the visitor. Many modern hosts include both; on WordPress, a good caching plugin and a CDN make a large difference.
5. Use hosting that fits your traffic
Very cheap shared hosting is often the slowest part of a site. If your server takes a long time to respond even for a simple page (PageSpeed shows this as a slow server response), better hosting is the fix.
6. Stop the layout jumping
Give every image, video and embed a fixed width and height (or aspect ratio), reserve space for banners and cookie notices, and load web fonts so text doesn't reflow. See Google's guide to CLS.
7. Make taps respond quickly
Slow responses to taps usually come from heavy JavaScript running on the main thread. Remove unused scripts, break up long tasks and avoid large page builders where possible. Google's INP guide explains how to find the cause.
8. Load fonts and CSS efficiently
Use one or two font families, host them yourself where possible, and remove unused CSS from themes and plugins.
Is it time to rebuild?
If the theme or page builder itself is the problem, every fix above becomes a fight. Signs it's time to rebuild: the site fails Core Web Vitals even after images and plugins are cleaned up, simple pages are very heavy, or every change needs a developer. A modern setup, for example Next.js on a fast host, makes good speed the default; we compare the options in Next.js vs WordPress.
Speed is one part of getting enquiries
A fast site still needs a clear message, proof and an easy next step. Our guide on why a website isn't generating leads covers the rest, and our traffic drop guide helps if visits have fallen.
Want a faster website? We build sites with Core Web Vitals in mind from day one, and can audit and fix an existing one. See our website design and development service or book a free 15-minute call.
