Why is my website slow is one of those questions with seven answers, and the reason it is so frustrating is that most advice picks one of them and treats it as the whole story. Compress your images. Change your host. Install a caching plugin. Each is sometimes right and usually not the thing actually wrong with your site.
So why is my website slow is really seven questions, and the good news is that they are not equally likely. Two of them account for most slow small business websites, both are free to fix, and you can tell in about five minutes which one you have.
On this page
First, measure it properly
Almost everybody measures this wrong, and measuring it wrong sends you off fixing the thing that was never broken.
Do not test on your own laptop on your own wifi. Your browser has your site cached, your connection is good, and you are probably sitting near the server. Your site will feel fine to you and slow to everybody else, which is exactly the situation that produces the question in the first place.
Test on a phone, on mobile data. That is how most of your visitors arrive. If you want a number rather than a feeling, put your web address into Google’s PageSpeed Insights and read the mobile tab, not the desktop one.
The number worth reading is Largest Contentful Paint, which is how long until the biggest thing on the screen appears. Google’s own published thresholds put 2.5 seconds or less as good, up to 4 seconds as needing improvement, and anything above 4 seconds as poor. Most small business sites that feel slow come in between 5 and 12 seconds on a phone.
Write your number down before you change anything. Otherwise you will make three changes, the site will feel faster because you are now expecting it to, and you will not know which one worked. That has cost more afternoons than any technical problem on this page.
The seven causes, commonest first
In rough order of how often they turn out to be the answer.
1. The images are enormous
This is the one, more often than everything else combined.
A photograph taken on a modern phone is somewhere between four and twelve megabytes and about 4,000 pixels wide. Uploaded straight to a website it is still four to twelve megabytes, and it is being sent to somebody on mobile data to be displayed in a space 340 pixels wide. A page with six of those on it is asking a visitor to download thirty or forty megabytes to look at a shop front.
The same image, resized to the width it is actually shown at and saved as WebP, is usually under 150 kilobytes. That is not a small improvement. It is often the difference between eleven seconds and two.
How to tell if this is you. Right click any large image on your site, open it in a new tab, and look at how long it takes on its own. If a single photo takes a noticeable moment, you have found your problem.
2. Too many things loading that nobody asked for
Every plugin, tracking script, font, chat widget, review badge and social feed adds requests. Each is small. Twenty of them are not.
The usual accumulation on a small business site is a page builder, a slider, an analytics tag, a Facebook pixel, a cookie banner, three Google fonts, a chat widget and two plugins installed for something that was tried once in 2023 and never removed.
How to tell. Count your active plugins. If it is over about fifteen on a small site, that is worth an afternoon on its own, and the ones to remove are the ones you cannot remember installing.
3. Cheap hosting, or hosting a long way from your customers
Shared hosting at the bottom of the market puts hundreds of sites on one machine. When one of them has a busy morning, everybody else waits.
Distance matters too, and it is the part people miss. A site hosted in the United States serving customers in West Africa is sending every request across an ocean and back before anything appears. That is real time, on every request, and no amount of image compression removes it.
How to tell. If the page takes a long time before anything at all appears, and then everything arrives at once, that is the server thinking, not your images. If it appears quickly and then fills in slowly, it is the opposite.
4. Nothing is cached
Without caching, every visitor causes your server to rebuild the page from scratch: run the code, query the database, assemble the HTML. With caching it builds the page once and hands out copies.
On WordPress this is one plugin and about ten minutes, and it is the single highest-return technical change available on most sites. Many hosts now offer it at the server level, which is better still and costs nothing.
5. A heavy theme or page builder
Some themes ship with everything anyone might want and load all of it on every page, including the parts your site does not use. Page builders that let you drag boxes around often produce deeply nested markup and load their own framework on top of the theme’s.
This is the most annoying cause because the fix is not a setting, it is changing the theme, which means rebuilding the pages. Worth knowing before you choose a theme rather than after.
6. Fonts and embedded third parties
Three font families in five weights is twelve files, and text often waits for them before it appears. Two families is usually plenty, and the system fonts are free and instant.
Embedded maps and videos are worse. An embedded map can pull in more than the rest of the page combined. A video embed loads a player whether or not anybody presses play. Both are fine as a link or a still image that loads the real thing when clicked.
7. Too much on the page
Rotating sliders, autoplaying video backgrounds, animation libraries, parallax. Each was a design decision that made the page more impressive and slower, and sliders in particular are worth losing on their own merits: most visitors never see past the first panel.
Why is my website slow on WordPress specifically
Most small business sites run on WordPress, and it has its own version of the same seven problems. Worth knowing which is which before you start disabling things at random.
The theme loads everything. Multipurpose themes sold with dozens of demo layouts ship the code for all of them. You installed it for one layout and you are serving the other twenty nine. This is the single biggest WordPress specific cause and the only real fix is a lighter theme.
The page builder adds a second framework. A builder loads its own styling and scripting on top of the theme’s, so the page carries two of everything. Fine on a fast connection, heavy on mobile data.
Plugins load on every page. A plugin that powers a form on the contact page usually loads its files on the home page too, because it does not know where it will be needed. Ten plugins doing this is a lot of dead weight on a page that uses none of them.
The media library was never optimised. WordPress makes several sizes of every image you upload, but it does not shrink the original, and if a theme or a builder asks for the full size then the full size is what gets sent.
The database has years of revisions in it. WordPress keeps a copy of every draft of every page forever unless told otherwise. On an old site that is thousands of rows the database reads past on every query.
The practical WordPress order is: optimise the media library in a batch, remove the plugins you cannot justify, add caching, clean out old revisions, and only then consider the theme. The first four are an afternoon. The fifth is a project, and it is the one worth paying somebody for.
If you are on Wix, Squarespace or Shopify instead, most of this does not apply: the platform handles caching and hosting, and your two remaining levers are image sizes and how many third party apps you have installed.
What a slow site actually costs
Two things, and one of them is invisible.
The visible cost is people leaving. Somebody who arrived from a search result has no attachment to you. If nothing has appeared after a few seconds they go back and click the next result, and you never learn it happened. There is no notification for a visitor who did not wait.
The invisible cost is that Google knows. Page experience is part of how search results are ordered, and loading speed is part of page experience. A slow site does not simply lose the visitors it gets, it gets fewer of them to begin with.
There is also a cost nobody counts. A business owner who knows their site is slow stops sending people to it. They stop putting it on cards, stop linking it in messages, and start sending everything to WhatsApp instead. The site becomes an embarrassment rather than an asset, and that decision is usually made quietly and never revisited.
Fix them in this order
The order matters, because the first three are free and account for most of the gain.
One. Resize and convert the images. Resize each to the width it is actually displayed at, save as WebP, and replace them. On WordPress a plugin will do the whole library in a batch. This alone fixes a large share of slow sites.
Two. Remove what you are not using. Every plugin you cannot justify, every tracking script from a service you stopped using, every font beyond two families. Deactivate rather than delete first, and check the site still works.
Three. Turn on caching. A plugin, or your host’s own setting if it has one. Ten minutes.
Four. Measure again. Same phone, same conditions, same tool. Compare it against the number you wrote down. Most sites are finished at this point, and if yours is, stop here.
Five. Only now, look at hosting. If the server is still slow to respond after the first three, that is a hosting problem and no amount of further tinkering fixes it. Move to a better plan, or to a host closer to your customers.
Six. Last, the theme. If it is still slow after all of that, the theme or the page builder is the cause, and that is a rebuild rather than a fix.
When it is not worth fixing
Sometimes the honest answer to why is my website slow is that speed is not really the problem at all.
If your site was built more than five or six years ago, is not comfortable on a phone, and cannot be edited without help, then making it load faster gets you a site that is quickly bad rather than slowly bad. The money is better spent on rebuilding it, and a modern build will be fast without anybody working at it.
The same is true if the site loads quickly and still brings you nothing. That is not a speed problem, it is a content and visibility problem, and the fix is what the pages say rather than how fast they say it. A page that loads in one second and does not tell anybody what you charge has not been helped by the second it saved.
Frequently asked questions
How fast should a website load?
Google’s published guidance puts Largest Contentful Paint at 2.5 seconds or less as good, up to 4 seconds as needing improvement, and above 4 as poor. Measure it on a phone on mobile data, because that is how most people arrive and it is always worse than your laptop suggests.
Why is my website slow on mobile but fast on my computer?
Because your computer is on a better connection, has the site cached, and has a faster processor. The mobile number is the real one. If you only ever check on your own laptop you will conclude the site is fine while your customers experience something else entirely.
Will compressing images really make that much difference?
On most small business sites, yes, and it is usually the largest single gain available. A photograph straight from a phone can be forty times bigger than it needs to be, and a page carrying six of them is asking every visitor to download all of it.
Do I need to change hosting to speed up my website?
Usually not, and it is the wrong thing to try first because it costs money and takes a day. Do the images, the unused plugins and caching first, then measure again. Move hosting only if the server is still slow to start responding after that, or if it is a long way from your customers.
Does website speed affect Google rankings?
Yes, as part of how Google assesses page experience, though it is one factor among many and not the biggest. The more direct cost is visitors leaving before the page appears, which happens whether or not it affects your ranking.
How much does it cost to fix a slow website?
The first three fixes are free if you can edit your own site, and an afternoon of somebody’s time if not. Hosting is a monthly cost. A rebuild is a project, and worth pricing against what a website costs rather than treating as a repair.
My site is fast but still gets no enquiries. What now?
Then speed was never the problem. Look at whether the pages answer what people actually want to know: prices, hours, what is included and how to reach you. That is usually where enquiries are lost, and it is a different fix entirely.
Where to start
Open your site on your phone, on mobile data, right now, and count. Then run it through PageSpeed Insights and write the mobile number down.
If it is over four seconds, start with the images. That one change fixes more slow websites than everything else on this page combined, and it costs nothing but an afternoon.
If you would rather not spend the afternoon, see what we do for clients.
