A slow website is the most common problem we get asked about that nobody ever planned for. The site looked fine the week it launched. Two years later it takes six seconds to show anything on a phone, and the owner assumes the fix is a rebuild. Usually it is not.
Speed is a measurable, fixable property of a website, not a mystery. This guide covers what actually counts as slow, the handful of causes behind almost every sluggish small business site, how to diagnose yours in about ten minutes, and which fixes are worth doing first.
What Counts as a Slow Website?
Google publishes the numbers, so you do not have to guess. The Core Web Vitals thresholds are the closest thing to an official definition of a slow website that exists.
Largest Contentful Paint, which is how long until the biggest visible element appears, should happen within 2.5 seconds. Interaction to Next Paint, which measures how quickly the page responds when someone taps or clicks, should stay at or under 200 milliseconds. Cumulative Layout Shift, which measures how much the page jumps around while loading, should stay at or under 0.1. Google measures these at the 75th percentile of page loads, split between mobile and desktop.
That last detail matters more than people expect. The 75th percentile means the experience of your slower visitors counts, not the experience you get testing your own site on office fiber with everything already cached in your browser.
The Real Causes of a Slow Website
Nearly every slow website we look at is slow for one of five reasons, and often for several of them at once.
Images uploaded straight off the camera
This is the single most common cause, and the easiest to fix. A photo straight from a phone or a camera can be 4000 pixels wide and several megabytes. Displayed in a 600 pixel wide slot, every one of those extra pixels still has to travel down a mobile connection first. Resize images to the size they are actually shown at, save them in a modern format such as WebP, and enable lazy loading so images below the fold wait their turn.
Plugin and script sprawl
Every plugin you install tends to load its own stylesheet and its own JavaScript on every page, whether that page uses the plugin or not. Add a chat widget, a review carousel, a booking embed, three analytics tags and a heat map tool, and the browser is fetching a couple of dozen files before it can finish drawing anything. Audit what is installed and deactivate what you no longer use.
Page builder bloat
Visual builders are genuinely useful, and they also generate a lot more markup than a hand built layout needs. Deeply nested containers, unused global styles and animation libraries loaded for one fade effect all add weight. The builder is not the problem. Building a simple page with fifteen nested wrappers is.
Hosting that is doing too much for too many
Entry level shared hosting puts your site on a server with a large number of other sites. When one of them has a busy day, your response time suffers, and no amount of image optimization compensates for a server that takes two seconds to begin replying. If your time to first byte is consistently poor while everything else measures well, the host is the bottleneck.
No caching and no content delivery network
Without caching, your server rebuilds the same page from scratch for every single visitor. Caching stores the finished result and serves that instead. A content delivery network goes further and keeps copies close to where your visitors physically are. Both are usually a settings change rather than a project.
How to Diagnose a Slow Website in Ten Minutes
Measure before you change anything. Guessing at a slow website usually produces work that does not move the numbers.
Run your home page, your busiest service page and one product or contact page through Google PageSpeed Insights, and read the mobile results rather than the desktop ones. Where enough real traffic exists, the tool shows field data from actual visitors alongside its lab test, and the field data is the one that reflects reality. Note which of the three Core Web Vitals is failing, because each points somewhere different. A poor Largest Contentful Paint usually means images or server response. A poor Interaction to Next Paint usually means too much JavaScript. A poor Cumulative Layout Shift usually means images or ads without reserved space.
Google Search Console reports the same metrics across your whole site rather than page by page, which is how you find out whether you have one slow website template or one slow page.
How to Fix a Slow Website, in Priority Order
Work top down. The first three items resolve the majority of slow website complaints and none of them require rebuilding anything.
- Compress and resize every image, convert to WebP, and turn on lazy loading below the fold.
- Turn on caching, and add a content delivery network if your host offers one.
- Remove plugins and tracking scripts you no longer actively use.
- Load only the fonts and font weights you actually display, and self host them where you can.
- Defer non critical JavaScript so it stops blocking the first paint.
- Reserve space for images, embeds and banners so nothing shifts as the page loads.
- Move to better hosting if time to first byte stays poor after all of the above.
A rebuild belongs at the bottom of that list, not the top. Rebuilding is the right call when the site is also outdated in structure, content and conversion design, not when it is merely heavy.
Does a Slow Website Actually Hurt Your Google Rankings?
Yes, but less dramatically than most articles claim. Google states plainly that Core Web Vitals are used by its ranking systems, so speed is a real signal rather than a myth.
Google is equally plain about the limits. Its documentation says Search always seeks to show the most relevant content even when page experience is sub-par, and it cautions that perfecting these scores purely for search reasons may not be the best use of your time. Speed is a tiebreaker between comparable pages, not a substitute for being the best answer.
The stronger argument for fixing a slow website has nothing to do with rankings. Every second a visitor waits is a second they can spend deciding to leave, so a slow website quietly wastes traffic that was hard won in the first place. Speed protects the conversions your marketing already earned.
Slow Website Questions Small Business Owners Ask
Why is my website so slow all of a sudden?
A sudden slowdown usually points to something that changed rather than something that was always wrong. The common culprits are a new plugin or tracking script, a recently uploaded batch of full size images, a theme or platform update, or a hosting neighbor consuming shared server resources. Check what changed most recently first.
Why is my WordPress site slower than other sites?
WordPress itself is not slow. The usual causes are plugin sprawl, where each active plugin loads its own scripts and styles on every page, page builder markup that ships far more code than the layout needs, and shared hosting without server level caching. Fewer plugins and real caching fix most of it.
How do I check my website speed properly?
Run your page through Google PageSpeed Insights, which reports both lab results and real visitor field data when enough exists. Test the pages that actually matter, meaning your home page, your top service page and a product page. Test on mobile, because mobile is where most sites fall down.
Does site speed really affect Google rankings?
Google states that Core Web Vitals are used by its ranking systems, so speed is a genuine signal. It is not a dominant one. Google also says it shows the most relevant content even when page experience is sub-par, so speed rarely rescues thin content and rarely sinks genuinely useful pages.
How fast does my site actually need to be?
Google’s published thresholds are a good target. Largest Contentful Paint should happen within 2.5 seconds, Interaction to Next Paint should stay at or under 200 milliseconds, and Cumulative Layout Shift should stay at or under 0.1, measured at the 75th percentile of visits across mobile and desktop.
The Bottom Line
A slow website is almost always a maintenance problem wearing the costume of a design problem. Measure first, fix images and caching before anything else, and only consider a rebuild when the site has genuinely outgrown its structure rather than just its weight.
Build a Site That Loads as Well as It Looks
Speed is one part of a site that works, and our guide to website design for small business covers the rest, from structure to conversion. If the slowness comes with dated design and confusing navigation, our piece on when a small business has outgrown its website will help you tell the difference between a tune up and a rebuild, and our website design services handle both. If you are tired of guessing why visitors leave before the page finishes loading, get in touch with our team for a look at your site. For more practical guides like this one, subscribe to the Demur Design newsletter in the footer below.
This article is researched and drafted with AI, then reviewed, fact-checked, and published by Demur Design.
