A customer taps your link, sees a white screen, waits, and goes back to the search results. You never hear about it. That is the problem with a slow website: the cost is invisible. Nobody fills in a form to tell you the page took too long. They simply choose someone else.
This website speed guide is the map for everything we have written on the subject. It explains what “fast” actually means, where the time goes when a page loads, and how to find the part that is slow on your site before spending money on fixes. Each section below opens a group of detailed guides, so you can go as deep as you need on the one problem you actually have.
It is written for business owners, not developers. You do not need to understand code to follow it, though a few sections will be easier with someone technical beside you.
What a fast website actually means
Speed is not one number. A page can start showing text quickly and still take a long time before the main image appears. It can look finished and then freeze when someone taps a button. It can load in full and then jump around as a banner slides in, so the visitor taps the wrong thing.
Google groups these experiences into three measurements it calls Core Web Vitals:
- Largest Contentful Paint (LCP) — how long until the biggest piece of content, usually a hero image or a headline, is visible. Google counts 2.5 seconds or less as good.
- Interaction to Next Paint (INP) — how quickly the page responds when someone taps, clicks or types. Good is 200 milliseconds or less. INP replaced the older First Input Delay measurement in March 2024.
- Cumulative Layout Shift (CLS) — how much the layout moves around unexpectedly while it loads. Good is 0.1 or less.
Google judges these at the 75th percentile of real visits, which means most of your visitors, not just the lucky ones on fast connections, need to get a good experience for a page to pass.
None of this means a site has to score 100 in a testing tool. A score is a simulation. What matters is whether real people on real phones can read, tap and buy without waiting.
Where the time goes when a page loads
Every page load follows roughly the same journey. The browser looks up your domain, connects to the server, waits while the server builds the page, downloads the HTML, then fetches the stylesheets, scripts, fonts and images the HTML asks for. Only then can it draw the page and make it respond.
Seen this way, “my website is slow” splits into much smaller questions. Is the server slow to answer? Is the page heavy? Are scripts holding up the drawing? Is one image the size of a poster? Each has a different fix, and fixing the wrong one wastes money. The sections below follow that journey.
1. Finding out why your website is slow
Start here if you are not sure where the problem is. The most useful thing you can do before changing anything is describe the slowness precisely: is it slow on phones only, only on the first visit, only at busy times, only for visitors abroad, only on the home page, or only since a particular change? Each of those points somewhere different.
Our guide to why a website loads slowly walks through that triage step by step and sends you to the right detailed guide for your symptom.
- Website Slow on Mobile but Fast on Desktop? Here’s Why
- Website Slow on First Load but Quick After That?
- Website Slow at Peak Times? Why Busy Hours Hurt
- Website Slow in Other Countries? Fixing Overseas Speed
- Website Suddenly Slow? A What-Changed Checklist
- Website Slow After Installing a Plugin? What to Check
- WordPress Slow When Logged In but Fast for Visitors?
- Homepage Loads Slowly? Why Only the Home Page Is Slow
- Website Slow After Migration? What Didn’t Move With It
- Website Slow After a Redesign? Why New Sites Get Heavier
2. Core Web Vitals in plain language
If Search Console has started showing “poor” or “needs improvement” URLs, or a PageSpeed report is full of red, this section explains what each metric is telling you and what usually causes a bad result. Start with Core Web Vitals explained, then go to the metric you are failing.
- How to Improve Largest Contentful Paint (LCP)
- Interaction to Next Paint Explained: What INP Measures
- How to Fix Poor INP: Finding the Slow Interaction
- How to Fix Cumulative Layout Shift on Your Site
- Reading the Core Web Vitals Report in Search Console
- Field Data vs Lab Data: Which Speed Numbers to Trust
- Core Web Vitals Assessment Failed? What It Means
- Do Core Web Vitals Affect SEO? What Google Has Said
- What Is Time to First Byte (TTFB) and How to Measure It
- First Contentful Paint Explained: FCP vs LCP
3. Measuring speed without fooling yourself
Testing tools disagree with each other and with themselves. Run the same test twice and the score moves. That does not make them useless, but it does mean you need a method: the same tool, the same page, several runs, mobile and desktop, written down before and after every change. Our guide on how to test website speed properly sets out that method, and you can run a quick check yourself with our free website speed test.
- How to Read a PageSpeed Insights Report, Section by Section
- Why Your PageSpeed Score Changes Every Time You Test
- Is a 100 PageSpeed Score Necessary for Your Website?
- GTmetrix Waterfall Chart Explained, Row by Row
- Lighthouse vs PageSpeed Insights: Why Scores Differ
- How to Use WebPageTest: A Beginner’s Guide
- Check Page Load in Chrome DevTools: The Network Tab
- How to Monitor Website Speed Over Time
- What Is Page Size? Page Weight Explained Simply
- Reduce HTTP Requests: Which Ones Actually Matter
4. Images, video and other media
On most small business sites, images are the single biggest part of the page. A phone photo uploaded straight from the camera, a slider with six large banners, or a background video can outweigh everything else on the page put together. The good news is that media problems are usually the cheapest to fix. Read how images slow a website down first, and see our older practical guide to image optimization for the basics.
- WebP vs AVIF vs JPEG: Best Image Format for Websites
- Convert Images to WebP in WordPress and Check It Works
- Lazy Loading Images Explained, and the Hero Image Mistake
- Responsive Images srcset: Smaller Images for Phones
- Do YouTube Embeds Slow Down Your Website? Use a Facade
- Is a Background Video Slowing Down Your Site? What to Do
- Do Sliders Slow Down Websites? What to Check and Change
- SVG Icons vs Icon Fonts: Is Font Awesome Slowing You?
- WooCommerce Product Images Slow? Fix the Grid and Gallery
- Image Dimensions vs File Size: Resize Before You Upload
5. Caching: serving pages without rebuilding them
A WordPress page is built fresh on every visit unless something stores a ready copy. Caching is that something, and there are several layers of it: in the visitor’s browser, on your server, inside the database layer and at a CDN. Getting caching right is often the largest single improvement for a WordPress site. Getting it wrong breaks carts and logins. The types of website cache guide explains which layer does what.
- Page Caching in WordPress: How a Full Page Cache Works
- Leverage Browser Caching: Cache-Control Headers Explained
- Redis Object Cache for WordPress: When It Is Worth It
- PHP OPcache Explained: The Cache Your Host Runs for You
- How to Choose a WordPress Caching Plugin for Your Server
- LiteSpeed Cache Settings: A Safe, Staged Setup
- Caching WooCommerce Cart and Checkout: What to Exclude
- Cache Preloading Explained: Warm Up Your Website Cache
- Cloudflare Caching for WordPress: Defaults, HTML, Purging
- Caching Plugin Broke My Site: Safe Rollback and Fixes
6. Code: CSS, JavaScript, fonts and third-party scripts
Themes, page builders and plugins load code on every page whether that page needs it or not. Tracking pixels, chat widgets and embedded tools add more, from servers you do not control. This section deals with the warnings PageSpeed reports most often, starting with render-blocking CSS and JavaScript.
- How to Reduce Unused CSS Without Breaking Your Site
- How to Reduce Unused JavaScript on WordPress
- Minify CSS and JavaScript: What It Saves and What It Risks
- Defer vs Async JavaScript: Which to Use and What Breaks
- Critical CSS Explained: Faster First Paint, Fewer Surprises
- Are Google Fonts Slowing Your Website? What to Cut First
- How to Host Google Fonts Locally on WordPress
- Font-display Swap Explained: Stop Invisible Text
- Are Third-Party Scripts Slowing Your Website?
- Is Your Live Chat Widget Slowing Your Website?
7. Hosting and the server
Some slowness is the server’s fault and no amount of image compression will fix it. If the server takes a long time before it sends the first byte, everything else waits. The hosting and page speed guide explains what the server controls and what it does not, so you can tell whether a hosting upgrade will help before paying for one. For choosing between plan types, see shared, VPS and cloud hosting compared.
- Reduce Initial Server Response Time: Fixes in Order
- PHP Workers Explained: Why Busy Sites Start to Queue
- HTTP/2 vs HTTP/3: What Changes and How to Check
- Gzip vs Brotli Compression: Check and Enable It
- Shared Hosting Resource Limits: What Each One Does
- Is WP-Cron Slowing Your Website? Take It Off Visitors
- Autoloaded Options in WordPress: Find and Trim Them
- Slow DNS Lookup: Where It Hurts and What to Change
- When to Upgrade Hosting for Speed: Three Tests First
- Is Bot Traffic Slowing Your Website? Read the Logs First
8. WordPress, page builders and WooCommerce
WordPress itself is not slow. What we add to it can be. This section looks at plugins, themes, page builders and the parts of WooCommerce that cannot be cached by design, such as the cart and checkout. Begin with whether too many plugins slow WordPress down, and if you want a short list of quick wins, our earlier post on speeding up a WordPress website is still a good start.
- How to Find a Slow Plugin in WordPress
- Slow Elementor Website? How to Speed It Up
- Page Builder vs Gutenberg Speed: Honest Trade-offs
- How to Choose a Fast WordPress Theme
- WordPress Heartbeat API: What It Does and How to Limit It
- WooCommerce Site Slow? What to Fix First
- WooCommerce Cart Fragments: What the Request Does
- WooCommerce Checkout Slow? Find the Slow Step
- admin-ajax.php Slow? Find What Is Calling It
- Multilingual WordPress Site Slow? Causes and Fixes
9. Speed, sales and keeping a site fast
Speed work is worth doing when it changes what visitors do: more enquiries, fewer abandoned carts, ad clicks that turn into leads. This last section covers how to judge that on your own site, what a proper speed audit should give you, when to hire help, and how to stop a fast site becoming slow again six months later. Start with how website speed affects sales.
- Landing Page Speed for Google Ads: What to Fix First
- Website Speed Audit Checklist: What a Real Audit Covers
- Should I Hire Someone to Speed Up My Website?
- How to Keep a Website Fast After It Has Been Optimised
- Is AMP Still Worth It? A Plain Answer for Small Sites
- Website Performance Budget: Limits That Keep Pages Fast
- Building a Website for Slow Internet Connections
- Shopify Store Slow? What You Control and What You Do Not
- Wix Website Slow? Fixes for Wix and Squarespace Sites
- Website Speed Optimization Cost: What Drives the Price
A sensible order of work
If you want to improve your site and do not know where to begin, this order avoids most wasted effort:
- Measure first. Test your three most important pages on mobile, several times, and write the results down.
- Check the server. If the first response is slow even on a simple page, deal with hosting and server caching before anything else.
- Fix the media. Resize and compress the largest images, and stop lazy-loading the main image at the top of the page.
- Set up caching properly, with the right exclusions for carts, checkouts and logged-in users.
- Trim the code: remove plugins and third-party scripts you no longer use before trying to optimise the ones you keep.
- Measure again the same way, and keep the notes for next time.
Take a full backup before each step, and change one thing at a time. When several settings change at once and something breaks, nobody can tell which change caused it.
Frequently asked questions
How fast should a business website load?
There is no single number, because speed has several parts. A practical target is to pass Google’s Core Web Vitals for most real visitors: the main content visible within about 2.5 seconds, taps answered within 200 milliseconds and no noticeable layout jumps. Test on a mid-range phone, not only on office Wi-Fi.
Will a faster website rank higher on Google?
Speed is one of many signals and relevance comes first. A fast page with weak content will not outrank a useful slower one. Speed helps most when competing pages are otherwise similar, and it helps visitors stay on the page, which matters whatever the ranking effect.
Can I speed up my website myself?
Often, yes, for the simple steps: resizing images, removing unused plugins and turning on the caching your host provides. Code-level changes such as deferring scripts or removing unused CSS can break layouts and forms, so test them on a staging copy or ask someone experienced.
Why is my PageSpeed score different every time I test?
Lab tests run on shared machines over real networks, and your server, ads and third-party scripts respond differently from one moment to the next. Run several tests, use the middle result, and compare like with like rather than reacting to one low score.
Do I need a new website to make it fast?
Usually not. Most slow sites improve a lot with better hosting configuration, caching, lighter images and fewer scripts. A rebuild makes sense when the theme or page builder itself is the bottleneck and every page is weighed down by code the site does not need.
If you would rather have the measuring and fixing done for you, our website speed optimization service starts with an honest look at what is actually slowing your site, and tells you which fixes are worth paying for before any work begins.
