Full guide
A slow website is one of the quietest, most expensive problems a business can have. Nobody complains, they simply leave. Visitors form an opinion of your brand in the first couple of seconds, and if the page is still loading when they get there, many of them have already decided to look elsewhere. Google reports that as page load time grows from one second to three seconds, the probability of a visitor bouncing rises sharply, and the trend only gets worse from there (see Google's research on mobile page speed). The good news is that speed is one of the most fixable things on a website, and the wins compound: a faster page keeps more visitors, ranks higher in search and converts more of the traffic you already pay for.
This guide walks through the modern toolkit and the techniques that matter most, in the order you should tackle them. Diagnose first, then fix the biggest offenders, then keep an eye on the numbers so the site stays fast as it grows.
Why does website speed matter so much?
Speed touches everything that decides whether a website earns its keep. It shapes the first impression, it influences how long people stay, and it affects how many of them take action. It also feeds directly into search rankings, because Google uses page experience signals to help decide which results to show. A fast site is easier to crawl, easier to use and easier to trust, while a sluggish one leaks visitors at every step. In a competitive market, the difference between a two second page and a six second page can be the difference between a customer and a missed opportunity.
What are Core Web Vitals and what should you aim for?
Core Web Vitals are the three metrics Google uses to measure real user experience, and they give you concrete targets rather than vague advice. Largest Contentful Paint measures how quickly the main content appears, and you want it under 2.5 seconds. Interaction to Next Paint measures how responsive the page feels when someone clicks or taps, and you want it under 200 milliseconds. Cumulative Layout Shift measures how much the layout jumps around as it loads, and you want it below 0.1. Google's own Core Web Vitals documentation sets out these thresholds in detail. Treat these three numbers as your scoreboard: get them into the green and most of the speed problems your visitors notice will already be solved.
Here are the three metrics side by side, with the thresholds Google uses to mark a page as good, needs improvement, or poor.
| Metric | What it measures | Good | Needs work | Poor |
|---|---|---|---|---|
| Largest Contentful Paint | How fast the main content appears | Under 2.5 s | 2.5 s to 4 s | Over 4 s |
| Interaction to Next Paint | How responsive the page feels to taps and clicks | Under 200 ms | 200 ms to 500 ms | Over 500 ms |
| Cumulative Layout Shift | How much the layout jumps while loading | Under 0.1 | 0.1 to 0.25 | Over 0.25 |
Which tools should you use to measure website speed?
You cannot improve what you do not measure, so begin with a proper diagnosis. The good news is that the best tools are free and quick to run.
- Google PageSpeed Insights grades your page, reports real-world Core Web Vitals data and lists specific fixes ranked by impact.
- Lighthouse, built into Chrome's developer tools, audits performance, accessibility, best practices and SEO in one pass.
- GTmetrix produces a waterfall chart that shows exactly which files load slowly, so you can see the bottleneck rather than guess at it.
- WebPageTest lets you test from different locations and connection speeds, which is invaluable if you serve customers across the country.
Use these lab tools to find problems, then check the field data from real visitors to confirm the fixes actually landed. A page can score well in a test and still feel slow to someone on a patchy mobile connection, so always look at both.
How do you optimise images for faster loading?
Images are almost always the heaviest thing on a page, which makes them the highest-value place to start. Compress every image before it goes live so you strip out wasted data without any visible drop in quality. Serve modern formats such as WebP or AVIF, which are typically much smaller than older JPEG or PNG files at the same quality. Size each image to the space it actually fills, rather than uploading a huge file and letting the browser shrink it. Finally, lazy load anything below the fold so the browser only fetches images as the visitor scrolls toward them. Done together, these steps often cut page weight dramatically and produce the single biggest speed gain available.
What do caching and a content delivery network actually do?
Caching and a content delivery network both reduce the work and the distance between your server and your visitor. Browser caching tells a returning visitor's browser to keep copies of files like your logo and stylesheet, so the next visit loads almost instantly instead of downloading everything again. A content delivery network stores copies of your site on servers around the world and serves each visitor from the one nearest them, which slashes the time data spends travelling. For an Australian business with customers in other states, that geographic shortcut can shave precious time off every page load. Together they are one of the most reliable upgrades you can make.
How do code and hosting affect page speed?
Once images and caching are handled, the page itself and the server behind it come into focus. Minify your CSS, JavaScript and HTML to remove the spaces and comments a browser does not need, and combine or defer scripts so they do not block the page from rendering. Preload the handful of resources that matter most, such as your main stylesheet and key fonts, so the browser fetches them early. Behind all of this sits your hosting: a cheap, overcrowded shared server can hold back even a perfectly optimised page. If your server response time is consistently slow, upgrading to faster, better-resourced hosting can lift the whole site at once. Trim the plugins and third-party scripts you do not truly need, because each one adds requests and weight.
How do you keep a website fast over time?
Speed is not a one-off project, it is a habit. Websites tend to get slower as they grow, picking up new images, plugins, tracking tags and features that each add a little weight. Build a simple routine: test your key pages every month or two, watch your Core Web Vitals in Google Search Console, and treat any new tool or script as something that has to earn its place. When you add a feature, check what it costs in load time. Modern approaches like edge computing and AI-assisted optimisation are making fast sites easier to maintain, but the fundamentals never change. Lighter pages, fewer requests and smart caching will keep your website quick, your visitors happy and your search rankings healthy for the long run.
In short
How do you speed up a website?
Key takeaways
- Measure before you optimise, because you cannot fix what you have not diagnosed.
- Images are usually the heaviest part of a page, so compression and modern formats win the most.
- Caching and a content delivery network cut the distance and the work between server and visitor.
- Speed protects both your search rankings and your sales, so it pays for itself.