Why website speed matters, and how to fix a slow site
Slow pages cost enquiries and rankings. Here is what makes a site slow and the fixes that make the biggest difference.
- Most visitors arrive on a phone over mobile data, so test on a phone first
- Images, heavy themes and too many plugins cause most slowdowns
- Fix the biggest files first, then caching, then code
Most people who visit a small business website arrive on a phone, often over patchy mobile data. If the first screen takes too long to appear, many of them press back and try the next result. Speed is not a technical vanity metric. It decides whether your marketing spend turns into enquiries.
What a slow site really costs
A slow site loses people before they read a single word. It also sends a poor signal to Google, which uses page experience as one of many ranking factors. And it makes paid ads more expensive, because you pay for clicks from people who leave before the page loads.
The usual causes
In almost every slow site we audit, the same few problems account for most of the delay.
- Huge images uploaded straight from a camera or phone, often several megabytes each
- Page builders and themes that load code for features the page does not use
- Ten or twenty plugins, each adding its own scripts and styles
- Cheap shared hosting that responds slowly when traffic rises
- Chat widgets, trackers and embeds that all load before the content
Fix the biggest things first
Start with images. Resize them to the size they are shown at, convert them to modern formats such as WebP, and lazy-load anything below the first screen. This alone often halves the page weight.
Next, remove what you do not need. Every plugin and third-party script should earn its place. Then add caching so pages are served ready-made instead of being built on every visit, and serve files through a CDN so they come from a server near the visitor.
Measure on a real phone
Desktop tests on office Wi-Fi hide the problem. Open your site on a mid-range Android phone on mobile data. Google PageSpeed Insights and the Core Web Vitals report in Search Console show how real visitors experience your pages.
- 1Test on a phone
- 2Compress images
- 3Remove unused scripts
- 4Add caching and CDN
- 5Re-test monthly
When a rebuild is cheaper than repairs
If a site is built on a heavy theme with layers of plugins, repairs can only go so far. A lean static or lightly built site can load in a fraction of the time, costs less to host and is easier to keep secure. We rebuilt evoastra.com this way.
Before anything else, check the size of the largest image on your home page. If it is over 500 KB, start there.
Keep it fast
Speed drifts. New images, new plugins and new tracking codes creep in. Put a monthly check in the calendar, and make sure whoever updates the site knows how to compress images before uploading them.
Tell us what you’re working on. Free estimate within 24 hours, NDA on request.