What makes a website fast, and why it matters

Why speed matters

People decide whether to stay on a page within moments. If the content has not appeared, many go back and pick the next result. On a phone with a weak connection the effect is stronger.

Search engines notice too. Google uses page experience, including loading speed, as one of the signals in ranking. A fast site does not guarantee a high position, but a slow one works against you.

How speed is measured

Google describes page experience with three measures, known together as Core Web Vitals.

• How long the main content takes to appear. This is the wait a visitor actually feels.
• How quickly the page responds when someone taps or types.
• How much the layout moves while loading. A button that jumps as you reach for it is counted here.

These are worth knowing because they describe the experience, not just a number on a stopwatch.

What usually slows a site down

• Images far larger than the space they are shown in.
• Third-party scripts: chat widgets, trackers, advertising tags, embedded video.
• More JavaScript than the page needs, all loaded before anything can be used.
• Fonts loaded in a way that hides the text until they arrive.
• A slow server, or pages built from scratch for every visitor when they rarely change.

Third-party scripts deserve particular attention. Each one was added for a reason, by a different person, and nobody is counting the total.

The fixes that matter most

• Serve images in a modern format, at the size they are displayed.
• Build pages ahead of time, or render them on the server, so content arrives ready.
• Load third-party scripts late, and remove the ones nobody uses.
• Cache pages close to the visitor with a content delivery network.
• Reserve the space for images and embeds, so the layout does not jump.

None of this is exotic. Most slow sites are slow for two or three ordinary reasons, and fixing those brings most of the gain.

Test under real conditions

A site tested on a new laptop with office broadband will always look fine. Your visitors are on mid-range phones and mobile networks.

Tools such as PageSpeed Insights show two kinds of result: a test run in controlled conditions, and data collected from real visitors where enough exists. The second is the one that reflects what people experience.

Keeping it fast

Sites rarely become slow in one step. They slow down one script, one large image and one new feature at a time.

The remedy is a performance budget: an agreed limit that every release is checked against. When a new addition would break it, something else has to go, or the addition has to earn its place. It also helps to name one person who owns the number.