Your website is slower than grandma’s dial-up

Remember the screech of a dial-up modem? Your grandma does. She also remembers waiting for a single photo to appear line by line, and she has no intention of reliving that on your homepage. Neither do your customers. Nobody writes a complaint about a slow website. They just tap back, open the next result and buy from someone else, while your analytics politely records another “bounce”.

How slow is “slow”, really?

Your site feels fast to you because you open it every day on office Wi-Fi, on a good laptop, with half of it already cached in your browser. Your customer opens it once, on a mid-range phone, in a tram, with two bars of signal. That is the version that matters. Speed isn’t about a stopwatch. It’s about how long someone stares at a blank or jumpy screen before they can actually do something useful.

Core Web Vitals, minus the jargon

Google measures user experience with three numbers called Core Web Vitals, and it shows them in Search Console for every site with enough visitors. Largest Contentful Paint (LCP) is how long the main thing on the page takes to appear, usually the big image or the headline. Google’s target is 2.5 seconds or less. Interaction to Next Paint (INP) is how quickly the page reacts when someone taps a button or opens a menu. The goal is under 200 milliseconds. Cumulative Layout Shift (CLS) measures how much things jump around while loading. Under 0.1 counts as good.

In human words: show something useful fast, react instantly, and stop moving the button just as I’m about to tap it. If you’ve ever tried to press “Cancel” and hit “Buy now” because a banner loaded above it, you’ve met a bad CLS in person.

The good news is that Google publishes these targets openly, so you are not chasing a secret formula. A page that passes all three won’t magically jump to the top of search, but a page that fails them hands an easy advantage to every competitor who bothered.

Check your speed in ten minutes

You don’t need a developer for the diagnosis. Open PageSpeed Insights, paste your homepage address and switch to the mobile tab, because that’s the one that hurts. Look at the field data at the top first: it comes from real Chrome users, not from a lab. Then open Google Search Console, go to the Core Web Vitals report and see which groups of pages are marked “Poor” or “Needs improvement”. Finally, do the low-tech test: open your site on an older phone with Wi-Fi switched off and count, honestly, how long you wait.

Write down three pages: the homepage, your most visited product or service page, and the contact or checkout page. Those three are where speed turns into money, so that’s where you start. Fixing a page nobody visits feels productive, but it changes nothing.

The usual suspects (and how to arrest them)

Images are guilty in most cases we investigate. A photo straight from a camera or a stock site can weigh more than the rest of the page combined. Resize images to the size they are actually shown at, export them as WebP or AVIF, and add lazy loading to everything below the first screen. Keep the main image light and let it load first, before anything decorative.

Next come plugins and third-party scripts. Every chat widget, heatmap, pop-up, cookie tool and that third analytics tag someone added “just in case” adds code your visitor has to download before the page settles. Make a list, ask what each one actually earns you, and remove the ones nobody has opened in a year. Then fonts: four font families in six weights is a fashion show, not a website. Two families with a couple of weights each, loaded with font-display: swap, are plenty.

Last, the server. Cheap shared hosting with no caching and no CDN means every visitor waits for the server to wake up and assemble the page all over again. Page caching and a CDN are usually quick wins, and on WordPress or a similar CMS they are often just one setting away.

Sliders, videos and other heavy jewellery

Autoplay video backgrounds and five-slide carousels look impressive in a design presentation. On a phone they mostly look like a loading spinner, and very few visitors ever wait for slide three. One strong image with a clear headline usually beats the carousel on speed and on clarity. If video really tells your story, show a still poster image first and load the video only when someone presses play.

Speed is a habit, not a one-off

Sites get slow the same way people gain weight: one extra plugin, one huge banner, one more tracking code at a time. Nobody notices the single change, everybody notices the total. So put speed on the calendar. Check Search Console once a month, run PageSpeed Insights after every bigger update, and agree on one simple rule with whoever edits the site: no image goes up without being resized first.

A fast site also helps everything else you do. Visitors reach a page that is already there, search engines get a cleaner technical base, and your enquiries stop fighting a loading spinner for attention.

When a tune-up isn’t enough

Sometimes the honest answer is that the site sits on a heavy theme stacked with page builders, and every fix is a plaster on top of another plaster. That doesn’t automatically mean starting over. Often the smart move is to rebuild the few pages that bring in money, keep the content you already have, and leave the rest for later.

If you’ve run the tests above and the numbers made you wince, send us your link. We’ll look at your Core Web Vitals and tell you plainly which fixes are worth doing first and which ones can wait. Your grandma will thank you. Probably by phone.

Rastezh DigitalThe studio team