Most business owners find out their website is slow from a customer, or from a competitor’s site loading faster on the same phone. By then it has been costing money for a while, quietly.
The good news is that speed is one of the few things about a website you can measure yourself in two minutes, for free, and the causes are almost always the same five things.
Measure it before you believe anyone
Go to PageSpeed Insights and put your address in. It is Google’s own tool and it is free.
Look at the mobile score, not the desktop one. Almost all of your traffic is on a phone, phones are slower than laptops, and mobile is what Google measures you on.
Two numbers matter more than the overall score:
Largest Contentful Paint. How long until the main thing on the screen appears. Google’s own threshold for “good” is 2.5 seconds. Over 4 seconds is a problem you can feel.
Cumulative Layout Shift. Whether the page jumps around while it loads. If you have ever gone to tap a button and had an image push it out from under your thumb, that is this. It is intensely annoying and it is entirely preventable.
Write both numbers down before anybody sells you anything. If a developer cannot tell you what your current numbers are, they are guessing.
Why it matters beyond irritation
People leave. Someone standing on a street corner with one bar of signal does not wait. They go back and tap the next result, which is your competitor.
Google knows. Page speed is part of how Google ranks pages. It will not push a bad site to the top because it is fast, but between two similar businesses, the faster one has an advantage that compounds.
It hits the people you most want. Slow sites punish old phones and weak connections hardest, which in a neighborhood like the Bronx often means punishing exactly the customers you are trying to reach.
Cause one: images, and it is not close
This is the reason in the large majority of cases.
Phones now take photographs that are four or five megabytes each. Somebody uploads a dozen of them straight from the camera roll, the page technically works on the office wifi, and on a phone outside it takes fifteen seconds.
Three fixes, in order of impact:
- Resize before uploading. An image displayed 800 pixels wide does not need to be 4,000 pixels wide. Nobody sees the difference and it is often 90% of the file gone.
- Use a modern format. WebP files are typically much smaller than JPEG at the same visible quality.
- Load below-the-fold images only when needed. Anything the visitor has not scrolled to yet does not need to arrive first.
If you do only the first one, most slow small-business sites become acceptable.
Cause two: the plugin pile
This is specific to sites built on a CMS, which is most of them.
Every plugin adds code that has to be downloaded and executed. A contact form plugin, a slider, a cookie banner, a chat widget, a booking tool, an analytics stack and a security add-on can easily add up to more code than the actual page.
The test: list your plugins and ask what each one is genuinely doing. Most sites have three or four that nobody has used in two years and are still loading on every visit.
Cause three: fonts
Custom fonts are downloaded before text can appear in them. Load four weights of two different families and you have added a real delay for something almost no visitor consciously notices.
Two families is plenty. Two or three weights each is plenty.
Cause four: everything that watches you
Analytics, pixels, heatmaps, chat widgets and A/B testing tools each add third-party code, and you do not control how fast those servers respond. A chat widget nobody answers is the worst version of this: it costs speed every single visit and returns nothing.
Keep the ones you actually read the data from. Remove the rest.
Cause five: cheap hosting
Less common than people think, but real. If the server takes over a second to respond before anything can even start loading, no amount of image optimization saves you.
PageSpeed Insights reports this as server response time. If it is high and your images are already small, this is your problem.
What you can fix this week without a rebuild
- Resize and re-upload your five largest images
- Delete every plugin you cannot justify out loud
- Remove the chat widget if nobody is answering it
- Cut your fonts down to two families
- Give every image its dimensions so the page stops jumping
That list, done properly, fixes a large share of slow small-business sites without touching the design.
When the answer is a rebuild
Sometimes the architecture is the problem. If a site was built as a page builder on top of a theme on top of a CMS, each layer adds weight that no amount of tuning removes.
For comparison, here is what this site ships: 2.2 KB of JavaScript in total, one file. Not 2.2 megabytes. A typical CMS-based small business site sends hundreds of times that before it draws anything.
That is not because we are clever. It is because the site is built as plain HTML and CSS with no CMS underneath it, so there is nothing to download except the page you asked for. The tradeoff is real and worth stating: you cannot log into a dashboard and restyle the whole site yourself. What you get instead is a site that is fast by construction, has no plugins to update, and cannot be broken by an extension going out of date.
For a local business that needs a site to load fast, look right and stay working, that tradeoff is usually the correct one. For a business that publishes several times a week and wants full self-service, it is not.
Before you pay anyone to fix it
Get your current numbers from PageSpeed Insights and save them. Then ask whoever quotes you what numbers they expect afterward. Speed is one of the few parts of this work where the result is measurable by anyone, and a studio that will not commit to a number is telling you something.
Want us to look at yours? Send us the address and we will tell you what is slowing it down, whether or not you hire us.
You can also see seven sites we built and run any of them through the same tool.