A slow website costs you visitors before they read a word. People on phones, often on mobile data, leave pages that take too long to show something useful. Search engines notice too: page experience, measured through Core Web Vitals, is one of the signals Google uses.
The good news is that most business websites are slow for a handful of fixable reasons. This guide explains what to measure, how to measure it, and the fixes that make the biggest difference, whether your site runs on WordPress or is custom-built.
What Core Web Vitals measure
Google's Core Web Vitals focus on three aspects of how a page feels:
- Largest Contentful Paint (LCP): how long until the main content, usually the hero image or headline, is visible. This is the "is it loading?" feeling.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps a button or opens a menu. This is the "is it stuck?" feeling.
- Cumulative Layout Shift (CLS): how much the page jumps around while loading. This is the "I tapped the wrong thing" feeling.
Google publishes thresholds for "good" values for each metric. Check the current guidance on its web.dev documentation rather than relying on numbers copied around the internet.
How to measure
Two kinds of data matter:
- Field data: measurements from real visitors using Chrome, shown in PageSpeed Insights and in Google Search Console's Core Web Vitals report, when your site has enough traffic.
- Lab data: a simulated test of a single page load, from PageSpeed Insights or Lighthouse in Chrome's developer tools.
Field data tells you what users actually experience. Lab data helps you find causes and test fixes. Always test on mobile settings, because most of your visitors are likely on phones.
Test your key pages separately: home, main service pages, contact, and any landing pages used in ads. They often have different problems.
The fixes that matter most
1. Images
Images are the most common cause of slow business sites. Photos uploaded straight from a camera or a designer, at full resolution, can be many times larger than the screen needs.
- Resize images to the largest size they are displayed at.
- Use modern formats such as WebP or AVIF.
- Serve different sizes for phones and desktops with responsive images.
- Lazy-load images below the first screen, but not the main hero image: it should load immediately, with high priority.
- Always set width and height, so the browser reserves space and the layout does not jump.
Image-heavy sites benefit most. AgriDev, for example, has big field photography, and uses page caching to keep image-heavy pages fast.
2. Fonts
Custom fonts make sites look polished, but each weight is a separate download.
- Use only the weights you need.
- Host fonts on your own domain where possible, and preload the main one.
- Use a font display setting that shows text immediately with a fallback font.
- For Arabic and English sites, choose fonts carefully, since Arabic fonts can be large. Load each script only on pages that need it. See bilingual Arabic and English websites.
3. Third-party scripts
Chat widgets, analytics, tag managers, social embeds, heatmaps and ad pixels add up quickly, and they often hurt interaction responsiveness most.
- List every script on the site and why it is there.
- Remove the ones nobody uses.
- Load the rest after the main content, or only on the pages that need them.
- Replace heavy embeds, such as video players, with a lightweight preview that loads the player on click.
4. Hosting and server response
If the server takes a long time to send the first byte, everything else waits. Causes include overloaded shared hosting, no caching and servers far from your visitors.
- Use page caching, so pages are served ready-made instead of built on every visit.
- Use a CDN, so static files come from a location close to each visitor. This matters when your visitors are spread across several countries, for example across the Middle East and Europe.
- Choose hosting with enough resources for your site. See hosting a website for a business.
5. Layout stability
Layout shifts come from images without dimensions, late-loading banners, cookie notices that push content down, and fonts swapping in. Reserve space for anything that loads late, and show notices as overlays rather than inserting them above content.
6. Heavy page builders and plugins
On WordPress, speed problems often come from accumulated plugins and complex page-builder layouts. It is possible to have a fast WordPress site with a page builder; it requires discipline:
- Keep plugins to the ones you need, and remove inactive ones.
- Use a caching plugin or server-level caching.
- Avoid stacking sliders, animations and effects on the first screen.
- Keep WordPress and plugins updated.
Custom-built sites with a framework like Next.js can be extremely fast by default, with images optimized, pages pre-rendered and only the needed code sent to each page. They require a developer for content changes beyond what a CMS offers. See WordPress or a custom Next.js site.
Forms and interactivity
Interaction delays usually come from too much JavaScript running at once. On business sites the main culprits are sliders, animation libraries, chat widgets and complex forms. Keep the first screen simple, load interactive extras only when the visitor scrolls to them, and make sure the contact form and call button respond instantly on a mid-range phone. Test by tapping through the site on an older Android device: if the menu or form feels sluggish there, many of your visitors feel it too.
Speed and SEO
Speed is one part of SEO, not the whole of it. A fast page with thin content will not rank; a useful, well-structured page that loads quickly has the best chance. Fixing speed also improves conversions directly, because fewer people leave before your contact form or call button appears. For the content side, see SEO basics.
A practical order of work
- Run PageSpeed Insights on your top pages, on mobile.
- Fix images: resize, convert, set dimensions, prioritize the hero image.
- Audit and trim third-party scripts.
- Turn on caching and a CDN.
- Reduce fonts.
- Fix layout shifts.
- Re-test, and check Search Console's report over the following weeks, since field data updates gradually.
Keeping it fast
Sites get slower over time: a new plugin here, a large image there, a marketing script added for one campaign and never removed. Prevent this by:
- Re-testing key pages after every significant change.
- Agreeing image size guidelines with whoever uploads content.
- Reviewing scripts and plugins every few months.
- Monitoring uptime and response time. See monitoring and alerts for a small product.
Common mistakes
- Testing only on a fast office connection and a desktop.
- Lazy-loading the hero image.
- Installing a "speed" plugin on top of a heavy setup, without removing the cause.
- Chasing a perfect lab score instead of real visitor experience.
- Adding every marketing tool without asking what it costs in speed.
Summary
Most slow business websites can be made fast with a few focused fixes: smaller images, fewer scripts, sensible fonts, caching and a CDN. Measure on mobile, fix the biggest problems first, and keep checking as the site evolves.
If your site feels slow or you are planning a new one, see websites I have built such as AgriDev and Alpha Green, and get in touch.