Speed is not cosmetics
A slow website is often treated as a minor annoyance, something to fix later. For the visitor, though, it is the difference between a site that works and one that seems broken. Someone standing on the street with a phone, looking for your repair shop or clinic, will not wait five seconds for a blank screen. They close the tab and open the next result.
You do not need a study to believe this; remember your own behaviour. On a slow online shop we do not feel like finishing the order, and on a slow tradesman's site we wonder whether the company is even still active. Speed is measured not only in seconds but in trust.
That is why speed is part of the business, not cosmetics. A slow site does not just annoy people — it means enquiries you never received. And you never find out about them, because people left without leaving a trace.
What usually slows company websites down
The reasons are usually mundane, and rarely just one. The most common is oversized images: a photo from a phone or a photographer, several megabytes large, dropped onto the page without resizing. Next come plugins — each adds code that has to load, even if only a single page uses it.
Heavy page builders are convenient while building but often produce bulky code the browser has to process. On top of that come third-party scripts: analytics, chat widgets, maps, embedded videos, tracking snippets. Each one is small; together they add a noticeable delay.
Then there is cheap hosting, where your site shares a server with many others and responds slowly even to the first request. And finally fonts: if a site loads five variants of three typefaces, the text appears late or jumps around. None of these is a disaster alone, but together they drag a site down.
How to check it yourself
You do not have to be technical. The first tool is free: Google's PageSpeed Insights. Paste in your address and after a moment you get a score for mobile and desktop and a list of what slows the page. Do not be scared by a red number or a list of jargon — what matters is noticing what repeats and where the biggest items are.
The second test is even simpler and more honest. Take your phone, switch off Wi-Fi and open your site over mobile data, ideally somewhere with mediocre signal. That is how most customers see it. How long until the first content appears? Can you tap straight away, or does the page keep shifting? Does the form respond without making you wait?
Try it on two or three inner pages, not just the home page, and repeat it, because results vary. If the site feels slow to you, you do not need a number to know there is a problem.
What can be fixed cheaply
The good news is that much can be improved without a rebuild. The biggest effect usually comes from handling images properly: the right dimensions, a modern format, and loading an image only when it is about to appear on screen. Often an hour or two of work makes the difference visible.
Removing unused plugins and scripts helps too. Go through the list and ask of each one whether anyone really needs it. A tracking snippet from an old tool whose reports nobody reads is pure loss. Better hosting or a cache that serves finished pages faster can help, as can cutting the number of font variants.
These fixes are cheap, quick and unlikely to break anything. But they have a ceiling: they can improve a site, not transform it. If the foundation is slow, small fixes only lighten it a little.
When a rebuild is the honest answer
There are situations where patching is not worth it. If the site runs on an old version of a system that is no longer developed, if every change is painful, or if a page builder is woven into every page so deeply that it cannot be removed, the cost of patching approaches the cost of a new site. Then the honest thing is to say so.
A simple question helps decide: how much time and money would it take to bring the site to acceptable speed, and what will you have afterwards? If after a week of tweaks you have a site that is only somewhat better and still hard to edit, the saving is just a deferred expense.
We are not saying a new site answers everything. If your content is good, the site works and it is merely overloaded with images, lighten it. A new foundation makes sense only when the problem sits not in the details but in the construction itself.
Pre-generated pages, and search
Websites are built in different ways. A classic system such as WordPress assembles the page every time someone opens it: the server queries a database, runs the plugins and only then sends the result. With pre-generated (static) pages, as produced for example by Next.js, the finished page is prepared in advance and the server simply hands it over. It is the difference between a dish cooked to order and one already waiting on the counter.
The result is usually a noticeably faster site that also copes better with a rush of visitors. The limit: content that changes by the minute needs a different approach.
And search? Speed is one of many factors Google considers, and not the decisive one — content, trustworthiness and how well a page matches what people are looking for matter more. A fast site promises no ranking; it only removes one obstacle. If you would like a view on your own site, we can take a look and tell you whether small fixes are enough or a rebuild makes sense.