/
5 min read

Website speed explained for people who don’t want the jargon

Why slow websites lose customers, what actually makes a site slow, and the practical questions to ask your web designer or developer about it.
Website speed test results
In this guide
Share

Nobody has ever complained that a website loaded too quickly. Plenty of people have given up on one that loaded too slowly, usually without telling anyone. They just tap back and pick another result. That’s why website speed matters, even if nobody complains.

Website speed can sound like a technical subject best left to developers, and the detail often is. But the basics are easy to understand, and knowing them helps you ask better questions and spot when something isn’t right.

Why website speed matters to a business

A slow site costs you in a few ways. Visitors leave before they’ve seen what you offer. Those who stay find the experience frustrating, which colours how they see your business. Forms and checkouts that lag lose people at the worst possible moment.

Website speed also plays a part in how Google assesses pages, through a set of measurements it calls Core Web Vitals. It’s one factor among many rather than a magic ranking lever, but a quick, stable site is never a disadvantage.

What “fast” actually means

Website speed isn’t one number. When people talk about it, they usually mean a mix of three things:

  • How quickly the main content appears. The moment a visitor can see the headline, image or product they came for.
  • How quickly the page responds. When you tap a button or open a menu, does something happen straight away?
  • How stable the page is while loading. Does text jump down the screen as images and adverts pop in, making you tap the wrong thing?

These line up broadly with what Core Web Vitals measure. A page can do well on one and badly on another, which is why a single score doesn’t tell the full story.

The usual culprits

Oversized images

This is the most common cause we see. A photo straight off a modern phone or camera can be many times larger than it needs to be for a website. Images should be resized to the size they’re shown at, compressed, and saved in modern formats. Good platforms and plugins can handle much of this automatically.

Too many plugins and scripts

Every chat widget, tracking tag, social feed, pop-up tool and animation library adds code that the visitor’s phone has to download and run. Individually they seem harmless. Together they can grind a page to a halt. It’s worth reviewing what’s installed and asking whether each one earns its keep.

Heavy page builders and themes

Some off-the-shelf themes load features for every possible use, whether your site needs them or not. That doesn’t mean page builders are bad; a carefully built site on a popular builder can be quick. It depends on how it’s put together.

Cheap or overloaded hosting

If your site shares a server with hundreds of others, it may be slow to respond before anything else even starts. Hosting is rarely the only problem, but it can put a ceiling on how fast the site can be.

Video and fonts

Background videos and several custom fonts in multiple weights all add weight. Use them where they genuinely help, not by default.

Most slow websites aren’t slow because of one big problem. They’re slow because of lots of small decisions that nobody added up.

How to check your own site

Start simple: load your key pages on your phone using mobile data, not Wi-Fi. Then try Google’s free PageSpeed Insights tool. Put in your address and it will show scores for mobile and desktop, plus a list of suggested fixes.

Don’t panic about the score. Look at the mobile results, note the biggest issues flagged, and treat it as a starting point for a conversation rather than an exam grade. Scores also vary a little between tests, so run it a few times.

Questions to ask your web designer

  • How are images resized and compressed on the site?
  • Which plugins or third-party scripts are loaded on every page, and are they all needed?
  • Is caching set up, and is a content delivery network used where it makes sense?
  • What kind of hosting is the site on, and is it suitable for the traffic we get?
  • How do the Core Web Vitals look for our main pages on mobile?

A good designer or developer should be able to answer these in plain English. If the answers are vague, that tells you something too.

Where to start

Run your homepage and your top service or product page through PageSpeed Insights this week. Save the results so you have a baseline. Then pick the single biggest issue, which is often images, and get it fixed.

Performance is built into how we approach website design and development, and we can review and speed up an existing site as part of our maintenance and support service.

Written by the Ignite Creative team

A web design, branding and marketing agency in Liverpool. These articles come from the questions clients ask us every week. Got one of your own? Ask us.

Stuck on something in this guide?

Send it over. We'll give you a straight answer, usually within a working day.

Keep reading

Need help with the real thing?

If an article has raised a question about your own website, brand or marketing, send us the context and we’ll take a look.