Speed is not a technical detail. It is the first thing that decides whether a visitor stays — and it happens before they have seen what you sell.
On mobile, where most visits arrive, the difference between two seconds and five is the difference between a customer and a bounce.
Want to see how slow your site is?
Send us your address and we will return a speed check with the three issues costing you most.
What “fast” means in numbers
Google publishes specific thresholds, the Core Web Vitals. Three measurements, with clear limits.
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP | When the main content appears | ≤ 2.5 s | > 4 s |
| INP | How long it takes to respond to a tap | ≤ 200 ms | > 500 ms |
| CLS | How much the page jumps around while loading | ≤ 0.1 | > 0.25 |
The third is the one that irritates people most without anyone naming it: you go to tap a button, an image loads, the button moves and you tap something else.
The practical target: under 3 seconds on a phone with an average connection. Not on your own wifi with a new handset.
How to measure properly
Two tools, two different answers — and you need both.
- PageSpeed Insights. Gives a score and specific recommendations. Free, no sign-up.
- Real-user data in Search Console. Shows what your customers actually experience, rather than a lab test.
The test worth more than either: open your site on a phone, on mobile data rather than wifi, away from your office. Time it with a watch.
Measure three pages, not one: the home page, a service or product page, and contact or checkout.
What is usually to blame
In 90% of cases, the same five things in the same order.
| Cause | How often | How easily fixed |
|---|---|---|
| Enormous images | Very often | Easily |
| Cheap or overloaded hosting | Often | Moderate |
| Far too many plugins | Often | Moderate |
| Third-party scripts (chat, ads, tracking) | Often | Easily |
| A heavy theme or page builder | Less often | Hard |
The first row is half the problem. A 4 MB photograph straight off a phone, uploaded as-is, is enough to wreck a page’s load time on its own. The same file at the right dimensions and format is 150 KB.
What to fix first
In order of return per hour of work:
- Compress and convert your images. Sized to what the page needs, in WebP. Biggest gain, least effort.
- Turn on caching. Returning visitors stop re-downloading the same files.
- Clean out plugins. Uninstall what you do not use — not merely deactivate it.
- Defer third-party scripts. Chat and tracking load after the content.
- Check your hosting. If the server takes over 600 ms to respond, nothing else will be enough.
The first four are usually a single day’s work. The fifth means moving host, but it is also the most permanent.
What it costs
| Intervention | Indicative cost |
|---|---|
| Image optimisation and caching | €200 – €600 |
| Cleaning plugins and scripts | €150 – €500 |
| Hosting upgrade | €10 – €60 per month |
| Changing theme or rebuilding | €1,500 and up |
The first two lines solve most problems. You only reach the fourth when the site has other issues too — at which point the conversation is a redesign, not a repair.
Want to know which of these applies to you?
Ask us for a free check and we will tell you what can be fixed in a day and what needs a project.
What speed affects besides your Google ranking
Ranking is the least of it. Three more immediate effects:
- Completed orders. A slow checkout is among the most expensive causes of abandonment — see what else fixes it in cart abandonment.
- Advertising cost. You are paying for clicks that leave before the page renders.
- Trust. A slow site reads as abandoned, regardless of how good your work is.
On an e-shop with many products, speed also affects how many of your pages get crawled — the technical side is in e-shop SEO.
Frequently asked questions
How often should I check speed?
Every quarter, and always after any significant change to the site.
Is the video on my home page hurting me?
Considerably, if it autoplays on mobile. Use an image and let the video play on tap.
Is my hosting to blame?
Check the server response time. Consistently above 600 ms, yes — and no other improvement will rescue it.
Do I need a CDN?
If your customers are all in Greece and the server is nearby, the gain is small. If you sell abroad, it helps.
Do I need a score of 100/100?
No. Above 80 on mobile with good Core Web Vitals is entirely sufficient. Chasing perfection costs disproportionately.
The first step
Open PageSpeed Insights, enter your address and look at two things only: the LCP figure and the list of images it suggests compressing.
If those images are over 500 KB, you have found your problem — and it can be fixed today. Regular checks are part of maintenance.
Next step
Book a free 30-minute call with the team at The Dev Alley. We will look at your numbers and tell you what is worth fixing.