If your website takes more than a few seconds to show its main content, you are losing visitors before they see what you offer. A slow site quietly costs you calls, enquiries and trust. Most of the causes are ordinary: heavy images, extra scripts, a bloated builder, or hosting that cannot keep up. You can test this yourself, and you do not need a fake score to know whether the page feels late on a phone.
Why does website speed actually matter?
Speed is not a nice extra. It directly affects how many people stay on your site and how easily they find you in the first place.
Visitors leave slow sites. People are impatient, especially on a phone. If the heading and the number are still missing after a few seconds, many will hit back and call the next firm on the list. You never see that enquiry. You just notice the phone is quiet.
Google uses how a page feels as part of how it judges the page. A slow site can sit lower in results, so fewer people find you to begin with. It is not the only ranking factor. It is one you can actually control.
Most local searches happen on a phone, often on patchy signal in the van or on the pavement. A heavy site that struggles on 4G is a site that loses work. The desktop version on office wifi is a poor test. If you want the mobile half of this, read is my website mobile-friendly. Speed and a layout you can tap are related jobs. They are not the same job.
What usually makes a small-business site slow?
If your site crawls, the cause is usually one or several of these.
Huge, unoptimised images. A photo straight off a phone can be several megabytes. Put a few of those on a page and it grinds to a halt, especially on mobile. This is still the most common fixable cause I see.
A heavy website builder or theme. Many off-the-shelf themes and drag-and-drop builders are built to do everything for everyone, which means a lot of code your site does not actually need. WordPress is a frequent example, which is why there is a separate post on why WordPress sites are so slow. Wix and Squarespace can drag too if you stack apps and giant banners.
Too many extras. Chat widgets, pop-ups, sliders, review carousels, analytics, ad pixels and cookie tools all run in the background. Each one seemed small on the day you added it. Together they make the page think before it draws.
Cheap or overloaded hosting. Budget hosting often crams many websites onto one server. When the server is busy, your site slows down. You cannot fix that from the editor.
No caching, or caching that is fighting the builder. Without a ready-made version of the page, the server rebuilds it for every visit. With a messy builder, even the cached version can still be fat.
What are Core Web Vitals in plain English?
Core Web Vitals are three measurements Google uses to describe how a page feels to load. The names are ugly. The ideas are not. I will not quote fake Lighthouse scores. Your own URL is the only one that matters.
LCP (Largest Contentful Paint) is how long it takes the main thing on the screen to appear. On a local site that is usually a heading, a photo or a banner. If that takes several seconds on mobile data, people leave. Huge hero images are the usual culprit.
INP (Interaction to Next Paint) is how quickly the page responds when you tap something. A button that does nothing for a second feels broken. Heavy JavaScript, chat widgets and bloated page builders cause this. You tap Call or Send and the page thinks about it.
CLS (Cumulative Layout Shift) is whether the page jumps while it loads. You go to tap the number and an image or a cookie banner appears above it, so you tap the wrong thing. Reserve space for images. Do not shove banners in after the page has started.
You do not need to memorise the thresholds. You need a page that shows its main content quickly, responds when tapped, and does not jump. Fix the cause (image weight, extra scripts, layout) rather than chasing a 100 in a lab. A page can fit the screen and still be slow. You want both: a layout that fits, and a load that does not punish a phone on 4G.
How do you test your website speed?
Before you fix anything, find out where you stand. The quickest way is our free website speed test: paste in your address and you get a reading for mobile and desktop, plus a plain-English explanation of what is holding the page back. It runs on Google’s own PageSpeed data, so the results are the real thing, not a marketing badge.
Focus on the mobile result first. That is how most of your customers will see you. Run it again after each change so you can see whether the change helped.
Also do the human test. Open the site on your phone, on mobile data, not cafe wifi. Count the seconds until you can read the heading and tap the number. If you would not wait, your customers will not wait. Google’s PageSpeed Insights is a fine second opinion. Read the opportunities, not the single number people screenshot.
What is worth fixing, and what is not?
Worth doing: compress images to the size they actually appear, remove widgets you cannot name a reason for, drop unused builder sections, and get off the cheapest shared hosting if the server is the bottleneck. A cookie banner that does not eat the first screen helps more than people think.
Not worth doing: installing three speed plugins on top of a heavy theme and hoping. Chasing a perfect lab score while the phone number is still in an image. Paying for a “performance audit” that only restates “your images are large”.
Sometimes the cleanest fix is a rebuild. A hand-coded one-page site has no unused theme code and no plugin pile. That is the WordPress alternative for firms who are done tuning a stack they never wanted. A Page Forge one-pager is £99 to set up and £29 a month, or £299 a year, typically live in about five working days. Multi-page work is quoted. We are not a WordPress speed shop. If you stay on WordPress, the tuning is still yours, or another firm’s.
Frequently asked questions
How fast should my website load?
Aim for the main content to appear in a few seconds, ideally on mobile data, not just office wifi. Beyond that you start losing visitors. A speed test will show what is holding you back. I will not invent a score you should “hit”.
Will switching from WordPress make my site faster?
It can, especially if the current site is a heavy theme and a lot of plugins. A clean, hand-built site cuts that bloat. It is not magic if you then add the same giant video background and three chat tools.
Do Core Web Vitals affect Google ranking?
They are part of how Google judges page experience. Poor vitals can hold you back and, more immediately, they lose you the visitor who never waits. Fix the feel of the page. Do not obsess over a lab screenshot.
Is cheap hosting always the problem?
No. Cheap hosting can be the problem. Huge images and extra scripts are more common. Test first, then spend. Upgrading a host to serve a 4MB banner slightly faster is a poor buy.
Can I fix speed myself?
Images, unused widgets and a simpler first screen, yes. A builder that generates heavy markup, less so. If every change fights you, a rebuild is often cheaper than another year of lost calls.
Should I test on desktop or mobile?
Both, with mobile first. Most local customers arrive on a phone. A fast desktop score and a slow phone is a fail, not a split decision.