Why a slow website loses customers (and how to speed it up)

Four seconds are not a technical whim

In the lab we talk about Core Web Vitals. On the sofa people say «it won't open». The gap between those two sentences is your problem. Google treats LCP — the moment the main content appears — as acceptable under about 2.5 seconds on mobile. Beyond that, patience collapses. Past three seconds, more than half of smartphone visits leave. You do not need the decimal. You need to feel the wait.

Here is the detail that hurts: many companies measure the site from the office PC, on a fast network, with a warm cache. The customer arrives on shaky 4G, with ten tabs open, after tapping an ad you paid for. If the landing is slow, you are paying to educate the competition.

The evening the site makes you wait

Elena does not think «bad LCP». She thinks «this firm is not ready». The white screen is a judgement on the service, not the server. Long forms, CTA below the fold, phone number as an image: every friction confirms the doubt. Better the second result.

If you pay for Google Ads or a social campaign, every extra second is burned budget. The click is already yours. The page is giving it back.

The evening the site answers

Same Elena, same sofa. The page opens at once: name, promise, Call us, a short form. She understands what you do and for whom. The number is tappable. The request lands with someone who answers, not in a mailbox opened on Monday.

Speed here is not a design prize. It is respect. It says: «we know you have little time». That sentence, spoken without words, converts more than a slogan in the hero.

Photos that arrive too late

The two-megabyte hero, the six-shot slider, PNGs left «at maximum». The visitor does not see quality: they see emptiness. Compress, use WebP or AVIF, crop for mobile, load below-the-fold only when needed: often the first move that shifts the needle without rebuilding the site.

A «beautiful» photo that arrives late is a photo that does not exist. The customer is already elsewhere.

The distant server (and the network in between)

Cheap hosting in a distant datacentre, no cache or CDN, PHP waking on every visit: the site is slow even with images in order. You do not need an enterprise plan. You need hosting that is up to the job, a warm cache, and someone who sees uptime before the customer does.

If the shop or the management system behind the site is lazy, the shopfront inherits the laziness. Speeding up only the WordPress theme while the catalogue queries a dusty database is a demo trick.

Guests who stay in the living room

Chat, pixels, heatmaps, three players, a popup on the first pixel. Each one asks for coffee before you have said hello. Keep what you use, load the rest later, free the tap (INP). A site «full of tools» often cannot say hello.

Tracking matters. Tracking that makes the form wait does not. If the request fires after three seconds of scripts, you have measured everything except the sale.

The phone, not the twenty-seven-inch monitor

Most visits arrive from a smartphone. Widescreen hero, slow menu, vanishing CTA, tiny fields: you are designing for yourselves, not for Elena. Measure from the phone, on 4G, no cache. Fix the bottleneck before a full restyle.

One goal per page. One primary CTA visible without acrobatic scrolling. Then the rest.

Five questions to bring to a meeting

Tap each card. Behind it is how we use the question in the studio when an owner says «the site is slow» and means three different things.

1. Have you opened the site on a phone, on 4G, with no cache — or only from the office PC?
2. Which URL must convert this week, and into which action?
3. Does the form reach a named person, with a response time?
4. Are you paying for ads on a page that opens after too long a breath?
5. Who owns speed after go-live — who can say no to a plugin?

If a meeting does not produce a name, a page and a number, you are talking about «the site» the way people talk about the weather: everyone agrees, nobody is responsible.

In short: what to do Monday morning

Steps

1. Measure from the phone the page that must convert (LCP / INP).
2. Compress the hero and above-the-fold images; drop the useless slider.
3. Cut third-party scripts you do not use; the form must answer the tap.
4. One visible CTA, one goal per page, form into CRM or inbox with an owner.
5. One change at a time: that is how you learn what worked.

Quick checklist

• Real test on a smartphone, mobile network, empty cache.
• Primary CTA visible without acrobatic scrolling.
• Lead with a clear destination (CRM or inbox) and a named owner.
• Core Web Vitals under an acceptable threshold on critical URLs.
• Speed owner named.

KPIs (max three)

• Conversion rate of the key page.
• LCP / INP on mobile for URLs you pay for or that must convert.
• Qualified leads per week that actually reach someone.

Practical value (and the next step)

A site is valuable if it brings a call or a request — not if it «looks nice on a Mac». Practical value is a page that opens in time, a clear message, a contact that reaches a person.

This week: measure from the phone the page that must convert. Cut the weight of the hero. Keep one visible CTA. Make sure the form lands in the CRM or inbox, with a named owner. Then one change at a time — so you know what worked.

If you want a second opinion on the scope of your case, Foggetti Studio can help you read the current state and define a realistic intervention, without rebuilding everything out of habit.