How fast should a website load? What it costs you when it doesn't

If you have ever asked how fast a website should load, you have probably been given two answers: "as fast as possible", which is no use to anyone, or a wall of acronyms. This guide gives you actual numbers, what slow pages cost a small business, and the order to fix things in.

How fast should a website load in 2026?

Google publishes three targets, called Core Web Vitals. According to Google's web.dev documentation, a page is "good" when the largest piece of content appears within 2.5 seconds of the page starting to load, when the page responds to a tap or click in 200 milliseconds or less, and when the layout does not jump around (a shift score of 0.1 or less). Google measures this at the 75th percentile of real visits, split by mobile and desktop (Google web.dev, Web Vitals).

That 75th percentile detail matters. It means a quarter of your visitors can have a worse experience than the target and you still pass. If the site only feels fast on your own laptop, you are not seeing what the slowest quarter of your customers see.

For a plain business website, the practical target is simple: under 2.5 seconds to see the main image or headline on a phone, and nothing that shifts as you try to tap it.

How slow pages cost you enquiries and sales

Google and SOASTA analysed more than 10,000 mobile web domains and reported that 53 per cent of mobile visits are abandoned when a page takes longer than three seconds to load. The same research found that as load time goes from one second to seven seconds, the chance of a mobile visitor bouncing rises by 113 per cent (Google, 2017). It is an older study, but the figures are still the ones most speed research gets compared against.

A newer one looked at what tiny gains are worth. A study commissioned by Google and run by 55 and Deloitte followed 37 European and American brand sites and more than 30 million sessions. It found that a 0.1 second improvement in mobile load speed lifted retail conversion rates by 8.4 per cent (Deloitte and 55 for Google, 2020). Those are big brands, so do not expect the same lift on a small site, but the direction is the same.

Portent looked at it from the conversion side, using page views from 20 sites. On the e-commerce sites in its sample, the conversion rate was 3.05 per cent for pages that loaded in one second and 1.12 per cent for pages that loaded in three (Portent). Its lead generation sites fell more gently, from almost 40 per cent at one second to 29 per cent at three, so speed matters for enquiry forms too.

What a slow site costs: a worked example

This one is hypothetical, so treat the numbers as arithmetic, not a forecast. Say a Sydney online shop gets 2,000 mobile visits a month and the average order is $120.

If its pages behaved like the fast end of Portent's e-commerce sample (3.05 per cent), that is about 61 orders, or roughly $7,320 a month. If the same shop loaded like the three-second pages (1.12 per cent), it is about 22 orders, or roughly $2,690. The gap is around $4,600 a month, from the same traffic and the same products.

A real shop will not match Portent's averages exactly. The point is that you paid for those visits, and a slow page throws part of them away. If you sell online, our post on why shoppers abandon carts covers the checkout side of the same leak.

What usually makes small business sites slow

When we look at a slow small business site, it is rarely one dramatic thing. It is usually a short list:

• Huge images. A phone photo uploaded straight from the camera can be several megabytes. The page only needs a fraction of that.
• Too many scripts. Chat widgets, tracking pixels, booking plugins and review badges each add a request, and many load before your content does.
• A page builder or theme carrying features you never use. Template sites often ship code for dozens of layouts when you use three.
• Cheap, crowded hosting. If the server takes a second just to start answering, nothing you do on the page can fully make up for it.
• Web fonts and sliders. Four font weights and a rotating hero banner add up fast.

Weight is a design decision as much as a technical one. On our Kayinat Perfumery build, the brief was a premium look, and the tension with speed was real: rich imagery wants weight, good rankings and impatient customers want none. Restraint in animation and letting typography carry the luxury was how we handled it.

How to test your own site in ten minutes

You do not need a paid tool. Run these in order:

1. Open Google's PageSpeed Insights and paste in your homepage address. Look at the mobile tab first.
2. Check whether the report shows real-visitor data for your site. If it does, that is what Google sees. If it only shows lab data, your site probably has too little traffic for Google to have collected any.
3. Note your Largest Contentful Paint. Anything over 2.5 seconds needs work.
4. Scroll down to the opportunities list. Image sizing and unused scripts are the ones to look for.
5. Open the site on your own phone, on mobile data with wifi off. Be honest about how it feels.

Also test your main service page and, if you sell online, a product page. A fast homepage with a slow quote page still loses enquiries.

Fixes in order of payoff

Work down this list. It runs from the changes most sites need first to the ones that only matter once the basics are done.

1. Resize and compress images. Export them at the size they display, in a modern format such as WebP, and lazy-load anything below the fold. This alone often moves the needle most.
2. Remove scripts you do not use. Ask what each widget earns you. If the answer is nothing, delete it.
3. Load the rest later. Chat boxes and review badges can wait until after the main content shows.
4. Cut font weights. Two weights are plenty for most brands.
5. Reserve space for images and banners so the layout does not jump as things arrive.
6. Check your hosting. If the basics are fixed and the site is still slow to start responding, the server is the problem.

This is part of the technical groundwork on our SEO foundations page, because Google measures speed directly. If your site is already slow and you want to know why, start with our guide to why a website is slow.

When a rebuild beats tuning

You can tune a lot, but a bloated theme will not reach 2.5 seconds on a phone however well you compress images. Rebuild if:

• The slow part is the theme or page builder, not your content.
• Removing every non-essential plugin still leaves it slow.
• You are planning a redesign soon anyway. Fix speed as part of the website redesign instead of paying twice.