Your site is slow and it's costing you sales: a practical speed guide

A site that takes 5 seconds to load doesn't sound like a big deal — until you measure it in dollars: the probability a visitor bounces jumps more than 90% when load time goes from 1 to 5 seconds. Google knows it too: page speed has been a ranking factor for years, measured through Core Web Vitals. The good news: most slow sites are slow for three or four specific, fixable reasons.

In this guide you'll learn to measure your site's speed for free, read Core Web Vitals without a PhD, and pinpoint which of the five usual suspects is holding you back. With that, you can fix it yourself — or at least ask your developer for the right things, by name.

Key takeaways

• +Load speed is both a Google ranking factor and a bounce driver: a slow site loses rankings and sales at the same time.
• +Core Web Vitals are Google's three official metrics, with public thresholds: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.
• +Always check the mobile score in PageSpeed Insights, not desktop: most of your traffic comes from phones, and that's where slow sites die.
• +Unoptimized images are cause number one for slowness: serving them as WebP or AVIF at the correct size can double your score.
• +If your server takes longer than 800 milliseconds to respond (TTFB), no amount of downstream optimization will save you: decent hosting costs USD 10-30 a month.
• +A website built right on Next.js loads in under 2 seconds out of the box, because content ships pre-rendered from the server.

How do you measure your website's speed for free?

Before you have an opinion, measure. Go to PageSpeed Insights — it's free, it's Google's own tool — and enter your URL: in seconds you get a score from 0 to 100 plus a breakdown of what's slowing you down. Look at the mobile score, not desktop: most of your traffic is mobile, and that's where slow sites die. Under 50 is red: you're losing sales right now. Between 50 and 89, there's work to do. Above 90, you can relax.

PageSpeed shows two kinds of data: lab data (a simulation run on the spot) and field data, which reflects the real experience of Chrome users on your site over the last 28 days. Field data rules — it's what Google actually uses to evaluate you. And if you have Search Console, the Core Web Vitals report lists exactly which URLs are failing and on which metric — the perfect starting point for prioritizing.

What are Core Web Vitals?

Core Web Vitals are the three metrics Google uses to measure a page's loading experience: how fast content appears, how responsive the page is, and how visually stable it is. They come with official, public, stable thresholds, and they affect ranking. In plain terms:

• +LCP (Largest Contentful Paint): how long the main content takes to appear — the hero image, the big headline. Official target: under 2.5 seconds.
• +INP (Interaction to Next Paint): how long the page takes to react when a user taps a button or opens a menu. Official target: under 200 milliseconds.
• +CLS (Cumulative Layout Shift): how much content jumps around while loading (the button that moves right as you're about to tap it). Official target: under 0.1.

You don't need a perfect 100. You need all three metrics green for real users. A site scoring 85 with all three Core Web Vitals green beats one scoring 95 in the lab with a red CLS in field data.

The 5 causes we see in 90% of cases

1. Unoptimized images

The 4 MB photo uploaded straight from the camera is cause number one — and the easiest to fix. Images need to be served in a modern format (WebP or AVIF, which weigh a fraction of JPG), at the actual size they're displayed at — not a 4,000-pixel photo squeezed into a 400-pixel box — and with lazy loading: images below the fold load only once the user scrolls down. This alone can double your score.

2. Too many plugins and scripts

Every WordPress plugin, every tracking pixel, every floating chat widget, every embedded map adds weight and blocks rendering. It's common to audit a site and find 15 scripts loading when only 4 are actually used: the chat nobody answers, the pixel from a 2023 campaign, the slider that isn't on any page anymore. Audit what you actually use and delete the rest — it's the cheapest optimization there is.

3. USD 2 hosting

The cheapest hosting crams hundreds of sites onto the same server, and your site waits its turn on every visit. The symptom is TTFB (time to first byte): if it goes over 800 ms, the server alone eats up a third of your LCP budget before a single pixel shows up, and no downstream optimization saves you. Decent hosting costs USD 10-30 a month and pays for itself with the sales it stops scaring off.

4. Bloated themes and page builders

Visual builders generate bloated code: they load entire animation, icon, and style libraries just to show a button. That's the price of convenience, and on mobile — modest processors, spotty networks — it's a steep one. If your site runs on a multipurpose theme that "does everything," it's probably loading a ton of stuff you don't use on any page.

5. No cache, no CDN

Caching stops the server from rebuilding the page on every visit: it builds it once and serves the ready-made version thousands of times. A CDN (content delivery network) keeps copies of your site on servers spread around the world and delivers from whichever one is closest to the visitor. Together they're the two cheapest wins relative to their impact — several good options start free.

How much does speed actually matter for SEO?

Speed has been a confirmed Google ranking factor for years, now measured via Core Web Vitals. It's not the heaviest factor — content and authority matter more — but it works as a gatekeeper: between two pages with comparable content, the faster one wins, and a really slow site can get knocked out of the running no matter how good its content is.

There's an indirect effect that weighs just as much as the direct one: users abandon slow sites, and that behavior — bouncing back and picking another result — tells Google your page didn't answer the search. Slowness punishes you twice: in the metric, and in how your visitors behave.

Speed in dollars: what every second costs you

Industry studies have agreed for years: every extra second of load time cuts conversion, and in e-commerce the effect is brutal because the shopper is comparing. If your store takes 6 seconds and your competitor's takes 2, the abandoned cart isn't a mystery. Mobile amplifies it: worse connections, less patience, and the back button a thumb's-width away.

Run the numbers with your own data: if your site gets 5,000 visits a month and converts at 2%, that's 100 inquiries or sales. Add even a handful of extra conversions a month from a speed fix — and studies consistently show it does — and the optimization pays for itself within the first quarter. It's one of the few marketing investments with such a direct return.

What to fix first: the order that pays off

• +First, hosting: if TTFB is over 800 ms, migrate before optimizing anything else — everything else is built on top of that foundation.
• +Second, images: modern format, correct size, lazy loading. On most sites, this is 80% of the improvement.
• +Third, scripts: delete what you don't use and defer what isn't critical (the chat widget can load two seconds later — nobody notices).
• +Fourth, cache and CDN: properly configured, they multiply the effect of everything above.
• +Fifth, the fine-tuning: fonts, critical CSS, preloading. This pays off once everything above is done — not before.

And if you need to start over

Sometimes optimizing is just patching holes: if the foundation is a heavy theme on weak hosting, every improvement fights the underlying architecture, and the score climbs from 30 to 55 — never to 90. That's when it's worth doing the full math: what does it cost to keep paying for patches versus what does it cost to build it right, once.

The sites we build on Next.js load in under 2 seconds out of the box, because content ships pre-rendered from the server: no plugin pile-up, no extra libraries. It's not magic — it's starting with the right technology. And the price ranges for a well-built new site — a landing page from USD 800, a company site from USD 1,500 — tend to surprise anyone who's spent years paying for optimizations that never moved the needle.

Nobody comes back to a slow website. And Google doesn't recommend it either.

If you've measured your site and the result has you worried, don't try to fix it blindly by buying optimization plugins. At loco22 we run speed audits that tell you exactly what's slowing your site down, what it costs to fix, and what return to expect — and if the honest answer is rebuild instead of optimize, we'll tell you straight. The first consultation is free.