Website Speed Optimisation: The Complete Guide for Business Websites

Website speed optimisation is the work of making pages load and respond quickly for real visitors on real devices, especially phones on mobile data. It matters because slow pages lose enquiries, cost more to advertise and give search engines a reason to prefer a competitor. The good news is that most business sites can be made much faster without a rebuild, as long as the work is done in the right order.

This guide is ordered by impact per hour of work. It explains how to measure speed properly, what Core Web Vitals mean, and how images, hosting, caching, code and third-party tools each affect performance. It draws on performance projects we have run on WordPress, WooCommerce and hand-coded sites, including one where a faster server made almost no difference.

Why speed matters for business

Speed affects three things a business cares about: whether visitors stay, whether they convert and how much traffic you get in the first place.

Visitors on phones are impatient. If the main content takes several seconds to appear, or the page freezes when they tap a button, many leave before they read anything. That is lost revenue you never see in your reports, because the visitor never reached the point where you track them.

Speed also affects paid advertising. Google Ads considers landing page experience when deciding how your ads perform, so a slow landing page can make every click cost more. For one mobile tyre fitting business spending around £100 a day on ads, we rebuilt the landing pages in hand-coded HTML so they loaded almost instantly on a phone. When ads bring the traffic, speed decides how much of it you keep.

Then there is search. Google uses page experience signals, including Core Web Vitals, within its ranking systems. Relevance and quality still matter more, so a fast page with weak content will not outrank a slower page that answers the question better. When two pages are closely matched, though, speed can tip the balance, and it always affects what visitors do once they arrive.

Finally, website speed optimisation makes a site cheaper to run. Lighter pages use less bandwidth and server capacity, and search engines can crawl more of your site with the same effort.

Measuring properly: lab vs field

The most common mistake is optimising for the wrong number. There are two kinds of speed data, and they answer different questions.

Field data

Field data comes from real Chrome users visiting your site, collected in the Chrome UX Report. It reflects real devices, networks and behaviour. Core Web Vitals assessments use the 75th percentile over the previous 28 days, meaning three out of four visits need to meet the target. You see field data at the top of PageSpeed Insights when your site has enough traffic, and in the Core Web Vitals report in Search Console.

Lab data

Lab data comes from a single simulated test, usually Lighthouse, on a throttled device and connection. It is useful for finding causes and testing fixes, because you can repeat it instantly. It is not what Google uses to judge your real-world performance, and the score can swing between runs.

How to test

Start with the field data to see which metric is failing and on which pages. Then run lab tests on those pages to find the cause. Test on mobile settings, because that is where most problems show. And do not chase a perfect score: our guide to PageSpeed Insights scores explains why a score of 100 is rarely worth the effort.

Core Web Vitals

Core Web Vitals are three measurements Google uses to describe loading, responsiveness and visual stability. The thresholds for a "good" rating, published on web.dev, are:

Largest Contentful Paint

LCP is usually the hero image or main heading. It is slowed by slow servers, large images, render-blocking CSS and fonts, and images that are lazy-loaded when they should load first. See how to improve Largest Contentful Paint.

Interaction to Next Paint

INP replaced First Input Delay in March 2024 and is stricter, because it measures responsiveness across the whole visit. Heavy JavaScript, page builders and third-party scripts are the usual causes. See how to fix Interaction to Next Paint.

Cumulative Layout Shift

CLS comes from images without dimensions, late-loading fonts, cookie banners and adverts that push content down. See how to fix Cumulative Layout Shift. For the full picture of all three, read our Core Web Vitals guide.

Images

Images are the single biggest cause of slow business websites, and the easiest to fix.

The essentials

1. Use modern formats. WebP is supported everywhere and AVIF is widely supported. Both are far smaller than JPEG or PNG at similar quality.
2. Resize to the size displayed. A 4,000-pixel photo shown at 800 pixels wastes most of its weight. Use responsive images with srcset so phones download smaller versions.
3. Compress sensibly. Most photos look identical at a quality setting well below 100.
4. Set width and height on every image so the browser reserves space and nothing jumps.
5. Lazy-load images below the fold, but never the hero image. The main image should load immediately, ideally with a high fetch priority.

On the tyre fitting site mentioned above, 91 images were re-encoded to WebP and came to around 4MB in total across the whole site. Many business sites carry more than that on a single page. Our guide to image optimisation for websites covers formats, sizing and tools in detail.

Hosting and caching

Hosting sets the floor for how fast a site can be. If the server takes a second to respond before anything else happens, no front-end work can fully recover that second.

What good hosting looks like

• A supported, current PHP version for WordPress sites.
• Servers in or near the UK if your customers are here.
• Enough resources that pages are not queued at busy times.
• Server-level caching and HTTP/2 or HTTP/3.

Caching

Caching stores ready-made copies of pages so the server does not rebuild each page for every visitor. Page caching is the most important layer for WordPress sites, followed by browser caching, object caching and a content delivery network for static files. Our guide to website caching explains each layer.

Do you need a CDN?

A content delivery network stores copies of your images, CSS and JavaScript on servers around the world and serves each visitor from the nearest one. For a UK business with mostly UK visitors and good UK hosting, the gain is often modest. A CDN helps more when you have visitors across several countries, large media files or traffic spikes, and many CDNs also add security features such as bot filtering. Just check that its security settings do not block legitimate crawlers.

Diagnose before you upgrade

We worked on a heating engineer's WordPress site that was moved to a more powerful server in the hope of fixing its speed. It stayed slow. The real problems were a heavy page builder setup and no page caching at all, so every visit made the server build the page from scratch. Better hardware only shaved a little off the same slow process. If your pages are heavy, fix the pages first, then choose hosting to match.

Code, fonts and scripts

After images and caching, the next biggest wins come from reducing what the browser has to download and run.

Page builders and themes

Page builders load a lot of CSS and JavaScript to support every possible layout. Add-on packs add more. If you use Elementor, our guide to why Elementor sites are slow shows what to switch off. On WordPress generally, our WordPress speed optimisation guide covers themes, plugins and database clean-up.

Fonts and icons

Web fonts and icon fonts are frequent culprits. On the heating engineer's site, icon font add-ons and remotely loaded Google Fonts were adding weight to every page. Replacing the icons with inline SVG and turning off the remote font loading cut page weight considerably with no visible change to the design. Self-host the fonts you need, load only the weights you use and use font-display settings that show text straight away.

JavaScript

Defer scripts that are not needed for the first view. Remove plugins and features nobody uses. Heavy sliders, animation libraries loaded on every page and large frameworks for simple pages all add up. Animation can be fast, but only when it is built with performance in mind.

Third-party tools

Third-party scripts are code you do not control: chat widgets, analytics, advertising pixels, heatmaps, review badges, embedded maps and videos, and cookie consent tools. Each one adds network requests and work on the main thread, and together they are one of the main causes of poor INP.

How to get them under control

• List every third-party script on the site and who asked for it.
• Remove anything unused. Old tracking pixels from finished campaigns are common.
• Load scripts only where needed. A booking widget does not need to load on your blog. We built a small plugin that lets scripts be added to individual pages for exactly this reason.
• Delay non-essential scripts until after the page has loaded or until the user interacts.
• Use facades for YouTube videos and maps: show a static preview and load the real thing only when clicked.

Cookie consent tools deserve a special mention. They load on every page for every visitor, often before anything else, and a poorly configured banner can hurt LCP, INP and CLS at once. Choose a lightweight consent tool and check its impact after installation.

Our guide to third-party scripts explains how to measure the cost of each one.

When a rebuild is the better fix

Sometimes optimisation hits a ceiling. If a site is built on a heavy theme with several page builder add-ons, dozens of plugins and years of layered changes, each fix delivers less and the site stays fragile. At that point a rebuild can be cheaper than another round of tuning.

We have rebuilt several business sites as hand-coded HTML, including the tyre fitting firm above and a chauffeur company in Birmingham, because speed was central to how they win work. Others were rebuilt on WordPress with a lean custom theme so the owners could keep editing content. In both cases, website speed optimisation became part of the build rather than a repair job afterwards.

Signs a rebuild may be the better option:

• The site fails Core Web Vitals on every template, not just one or two pages.
• The theme or builder is no longer maintained, or blocks updates.
• Removing one plugin breaks several unrelated features.
• You are planning a redesign within the next year anyway.

Website speed optimisation: fix order and maintenance

When time and budget are limited, work in this order. It is based on the typical impact per hour of work on business websites.

1. Optimise and resize images, and fix hero image loading.
2. Turn on proper page caching and check server response time.
3. Remove or delay unnecessary third-party scripts.
4. Fix fonts and icons: self-host, subset and replace icon fonts.
5. Reduce CSS and JavaScript from themes, builders and plugins.
6. Fix layout shifts from images, banners and late-loading elements.
7. Review hosting once the pages themselves are lean.

Test on the devices your customers use

Your office laptop on fast broadband is not a realistic test. Check your analytics for the devices and browsers your visitors actually use, then test on a mid-range Android phone over mobile data as well as on desktop. Problems with responsiveness, in particular, often only show on slower phones.

Keeping it fast

Speed decays. New plugins, bigger images, extra tracking and new page sections all creep in over time. Check Core Web Vitals in Search Console monthly, re-test key pages after any significant change and agree a simple performance budget, such as a maximum page weight for key templates. Our website speed case study shows the full process on a real trade website, from diagnosis to results.

Speed work often overlaps with WordPress maintenance, so our guide to WordPress for business is worth reading alongside this one. For hands-on help, see our web development and SEO services.

Frequently asked questions

Get a speed audit

If your site feels slow or fails Core Web Vitals, book a speed audit and we will show you exactly what is slowing it down and what to fix first.