Why your website is slow, and what to do about it
A site that takes five seconds to open has lost a share of its visitors before they saw anything. The good news is the cause is almost always the same one, and it is rarely solved by a redesign.
When somebody asks me why their site is slow, they usually already have a theory: the hosting, too many plugins, "something with WordPress". In practice the answer is far more boring nine times out of ten, and better still, far cheaper to fix. Here is what it looks like when you start from measurement instead of guesswork.
Speed is not an aesthetic question
A waiting visitor has none of the patience you have for your own site. For tourism and service businesses much of the traffic arrives on a phone, often on a mobile network outside town, and there the difference between two and five seconds is the difference between an enquiry and a closed tab.
Google measures this and uses it. Core Web Vitals is a set of metrics describing how quickly the main content appears, how quickly the page responds to a tap, and how much the layout jumps while loading. It is not the dominant ranking factor, but it is the one that decides between two pages of similar quality. If you are in that position, and most small businesses are, speed is one of the few places where an advantage can be won technically.
Images are almost always the main culprit
In every audit I have run, images were the single largest weight. The reason is simple: a photograph straight out of a camera is several thousand pixels wide and several megabytes, and it gets displayed in a frame a few hundred pixels across. The browser downloads the whole file regardless.
The fix has three parts. First, images are saved in a modern format like WebP, typically two to five times smaller than the same JPEG. Second, several sizes of the same image are prepared so a phone downloads the smaller one. Third, images below the fold load only as the visitor approaches them. Together these often halve the weight of a page with no visible change at all.
Plugins and scripts nobody uses
The second most common cause is things loading on every page but used on one, or none. A booking calendar that lives on the contact page but whose script loads everywhere. A tracking tool somebody added three years ago that nobody looks at. A gallery installed to try out, then left in place.
On WordPress this accumulates invisibly, because each plugin brings its own CSS and JavaScript. It is not unusual for a site to load ten stylesheets and twenty scripts, a third of which are actually used. Removing inactive plugins and limiting the rest to the pages that need them is usually the second largest win, right behind images.
Hosting and where the server sits
Hosting is the real cause less often than people assume, but when it is, you can see it immediately: the page does nothing for a long time, then loads normally. That waiting period is time to first byte, and it depends on the server rather than on your site.
For Croatian visitors it also matters where the server physically is. The cheapest plans tend to sit on shared hardware with several hundred other sites, and then your speed depends on what the neighbours are doing. Moving to decent European hosting usually costs less per month than an hour of development work, which makes it one of the few decisions where the answer is almost always obvious.
Measure instead of guessing
Before any fix, it is worth measuring. PageSpeed Insights is free and gives two things: a lab test and, if the site has enough traffic, real data from actual visitors. That real-world data is what Google uses, so it matters more than the score in the test.
Search Console shows the same picture over time and grouped by page type, which is more useful than a single test. If the numbers do not move in the right direction within a few weeks of a fix, the wrong thing was fixed. That is the only reliable way to avoid an expensive redesign that solves a problem which was never there.
What to check first
- Open the site on a phone using mobile data rather than wi-fi, and time the wait
- Check the weight of the largest image on the homepage; anything over 300 KB is a candidate
- Look at the list of active plugins and ask whether each one is genuinely used
- Run PageSpeed Insights and read the field data, not just the score
- Turn on Search Console if it is not already, because without it there is no history
When a fix is not enough
A repair makes sense when the structure is sound and the problem is speed, neglected plugins or missing technical groundwork. If the site is not responsive, runs on a system that is no longer maintained, or the content is so out of date it needs rewriting anyway, then a new site is the more honest answer. An audit shows which of the two you are looking at within a few hours, and it is worth doing before committing to the more expensive option.