Website speed: it's not something you claim, it's something you measure (and how to tell if yours is costing you customers)

We have been building and managing websites and online shops for several years, and there's a phrase we read all the time on home pages: "fast website". The problem is that, written there, it doesn't mean anything. The speed of a website isn't an adjective to put on display, it's a fact: either a page opens quickly, or it doesn't, and whoever is looking at it feels the difference firsthand, often from their phone and with little patience. In this guide we'll look at what really happens when a website is slow, why speed isn't something to declare but something to measure, how to check it objectively with a stopwatch in hand, and why a well-built website stays fast even as it grows with more products and photos.

What really happens when a page opens slowly

Imagine someone who has just tapped your link on Instagram or searched for your business on Google. They're walking, they're on mobile data, they have a thousand other things to do. They tap, and the website takes a few seconds too many to appear: white screen, then half a page, then images settling into place. In those few moments, something simple and merciless happens: the person goes back. They haven't seen your offer, haven't read your prices, haven't realized how good you are. They've already left.

The point is that abandonment due to slowness is invisible. You don't get a complaint email, it doesn't leave a trace in the shop. That contact simply never turns into a phone call or an order, and you'll never know about it. Studies and industry experience on user experience have agreed for years on one fact: attention, especially on smartphones, drops off very quickly after the first two or three seconds. It doesn't take a huge delay — just a few repeated seconds on every page are enough to erode a significant share of potential customers.

We covered this mechanism in more detail, from the point of view of a shop losing sales without realizing it, in the article on when the website is slow and customers run away. Here we want to tackle the next question, the one almost nobody asks: how do I know, objectively, whether my website is fast or not?

"Fast website" written on the homepage doesn't mean anything

Whoever built your website told you it's fast. Maybe you read it yourself in a presentation or a quote. But fast compared to what? Tested with which connection, on which phone, on which page, at what time of day? Without a measurement, "fast" is just an opinion, and opinions about speed are almost always optimistic, because whoever built the website tests it on their own computer, with a fast connection, on a homepage that's just been opened.

The speed you perceive sitting in your shop with good wifi isn't the one the customer experiences out on the street. And it's precisely the customer's experience that counts, because that's what decides whether they stay or leave. That's why speed shouldn't be declared, it should be measured: with the same yardstick for everyone, under realistic conditions, and by repeating the test. The good news is that measuring it is within anyone's reach, for free, without being a technical expert.

KeideaCMS

Want to know if your website is costing you customers?

Request a free speed check →Discover KeideaCMS plans

How to really measure speed: the method

Measuring a website's speed doesn't require expensive tools or technical skills. It requires a method — that is, running the test the same way every time, so the results can be compared. Here's how we do it, and it's the same thing you can do.

1. Start with a stopwatch, seriously. Take your phone, turn off wifi and use mobile data, open your website in a new tab and count the seconds that pass before you can read and tap on anything. It's the most honest measure, because it's exactly what the customer experiences.

2. Test the right pages. Not just the homepage, which is usually the most polished, but also a product or service page and the contact page. These are the pages where sales are decided, and they're often the heaviest.

3. Pair it with an objective tool. Use a free tool like Google's PageSpeed Insights: paste in a page's address and it gives you real loading measurements, both for mobile and desktop. Don't stop at the overall score, look at the values of the individual metrics, which we'll cover shortly.

4. Repeat and compare. A single measurement isn't worth much. Repeat the test on different pages, at different times, before and after any changes. Speed is a consistent behavior, not a lucky one-off result.

This method turns a bar-room debate ("I think it's fast", "it seems slow to me") into data that can be looked at together. And data, unlike opinion, can be improved and then checked again.

The three measurements that matter (Core Web Vitals)

When you measure speed with a tool like PageSpeed Insights you're faced with several numbers. To make sense of them, three measures are enough — the ones Google itself uses to assess page experience, which it calls Core Web Vitals. These are public benchmarks, the same for everyone, and that's what makes them useful: they tell you where you stand against a recognized standard, not against an opinion.

You don't need to memorize them. You just need to know they exist, that they are public, and that they give you a common yardstick. If you want to understand more deeply how Google evaluates page experience and why these measures also affect rankings, we've written about it in the guide to Core Web Vitals. Here, the underlying message is enough: speed has units of measurement, and anyone who tells you otherwise is asking you to trust them instead of checking for yourself.

Why a website becomes slow (and gets worse as it grows)

A website is rarely born slow. Most of the time it starts out light, with few pages and few images, and loads quickly. Then the real life of the business weighs it down: products, high-resolution photos, banners, newsletter components, chat, tracking pixels, external services are added. Each piece, taken on its own, seems harmless. Added together, they turn a nimble page into a heavy one.

On top of this there's the problem of where the website lives. Many websites are on shared hosting, meaning a single server where dozens or hundreds of other websites coexist. As long as traffic is low this may be enough, but when visits grow, or when server neighbors consume resources, your website slows down exactly when it should be running faster. It's the most annoying paradox: slowness strikes when business is going well and the catalog has expanded.

This is why speed isn't a quality you achieve once at launch and then take for granted. It's something to design from the start and maintain over time. And this is where the difference lies in how the website is built and hosted.

Dedicated hosting and architecture: the speed that supports growth

A website stays fast over time for two reasons that work together: where it's hosted and how it's built. On the first front, having dedicated resources instead of a crowded server means performance doesn't depend on neighbors and doesn't collapse when visits increase. On the second, a well-designed architecture ensures that pages and the catalog stay light even as products and photos grow: images served in the right format and size, pages that load what's needed first, an orderly structure that doesn't get weighed down with every addition.

The same logic applies even more so to those who sell online, where the number of products and images keeps growing and every second of delay on a product page is one less cart. We've explored the relationship between performance, construction and growth in the guide to building an ecommerce site and, for company websites, in the guide to creating professional websites. In both cases the concept is the same: speed isn't an accessory to add later, it's the consequence of choices made well from the start and maintained over time.

Speed as a service, not as a promise

Now for the practical point. If speed is measured and must be maintained, the question for a business owner isn't "who tells me on the homepage that the website is fast", but "who takes responsibility for keeping it fast over time, and lets me verify it". This is exactly how we designed KeideaCMS.

With KeideaCMS, pages and the catalog are built to load quickly, hosting on dedicated servers is included in the fee, and maintenance is ongoing, so performance stays under control even as the business grows. It's not software to install and then keep in order on your own: it's a managed service, with a fixed fee that includes hosting, security, updates and support. The domain, content and data remain yours, and they're exported to you if one day you decide to move elsewhere; the platform's code, on the other hand, we maintain and update. In exchange for the fee, you're not buying a program, you're buying continuity.

And, consistently with everything we've said, we don't ask you to take our word for it. Speed is checked before and after, stopwatch in hand, with the same public tools that anyone can use. If you want to start there, we can measure your current site together and show you where time is being lost, with no obligation. You can see the options and the fee among our plans.

Is your website making you lose customers?

No need to guess: it can be measured. Let's check your website's speed together, stopwatch in hand.

Request a free check →Discover KeideaCMS