You will never see the customers a slow website costs you. Nobody emails to complain or leaves a one star review. They tap your link, wait a beat too long and go back to the search results, gone before your hero image finished loading.
That makes speed a dangerous problem to have. You can't see it, and it is costing you right now.
Website speed affects sales directly. A slow site loses visitors before they see your offer and converts fewer of the ones who stay. It can also hold you back in search. The good news is that speed is one of the most fixable problems on any website, and every improvement recovers customers you have already paid to attract.
The numbers are merciless
Two studies make the point. Google's 2016 Need for Mobile Speed research found 53% of mobile visits are likely to be abandoned when a page takes longer than three seconds to load. Portent looked at just over 100 million page views across 20 sites and found an e-commerce site that loads in one second converts at 2.5 times the rate of one that takes five.
Think about how you browse. You tap a link on your phone, standing in a queue at Woolies with half your attention elsewhere. The screen stays white and a spinner turns, so you hit back and tap the next result. At no point did you decide to reject that business. Your customers do the same to you.
The damage isn't limited to people who leave. Visitors who stick around on a sluggish site are already irritated. Buttons lag, the layout jumps as images load, and the form freezes when they tap submit. Each one chips away at trust at the moment you are asking for a phone number or a card.
Speed is the first promise your brand makes, and a slow site breaks it before you say a word.
Why speed also affects your rankings
Google says its core ranking systems look to reward a good page experience, and speed is part of that. Relevance still comes first, so a fast page will not outrank a better answer. But where several pages answer the query equally well, the sluggish one starts behind. Slow can cost you twice. Once in rankings, then again in conversions.
Google measures this with Core Web Vitals, three metrics that each cover something a visitor feels:
- Loading. How quickly the main content appears. Largest Contentful Paint (LCP) tracks when the biggest visible element, usually your hero image or headline, finishes rendering. Google's target is 2.5 seconds or less.
- Responsiveness. How quickly the page reacts when someone taps or clicks. Interaction to Next Paint (INP) measures that delay, and good is 200 milliseconds or less.
- Visual stability. Whether things jump around as the page loads. Cumulative Layout Shift (CLS) catches the moment you go to tap a button and an ad pushes it down the screen. Aim for a score of 0.1 or less.
These are measured from real visitors on real devices. A lab test on a fast office connection doesn't count. So your site might feel fine on your laptop and still fail for the people who buy from you. We go deeper into the current rules in Core Web Vitals in 2026.
What makes a website slow
- Bloated images and heavy scripts that make phones crawl.
- Cheap, overloaded hosting shared with a crowd of other sites.
- Template code stuffed with features you never use. Every visitor still downloads the booking calendar and the animation library, even on pages that have neither.
- No caching and no optimisation, just "it works on my laptop."
A few more worth checking:
- Plugin pile-ups. Every plugin added to fix a small problem brings its own code and its own requests. Twenty of them and the site is carrying a backpack full of bricks.
- Third-party scripts. Chat widgets, tracking pixels, review badges, social embeds and pop-up tools. Each one loads from someone else's server, on someone else's schedule.
- Autoplaying video and sliders. They are heavy, and in our view the classic homepage carousel rarely earns the speed it costs.
- Custom fonts loaded badly. Several font families and weights can hold up the text people came to read.
The fix is plain engineering. Lean code and optimised assets, built around the moment a real person on a real phone taps your link.
How to test your site's speed today
You can check where you stand in about ten minutes.
- Run Google PageSpeed Insights on your homepage and your most important money page, such as your main service page or top product. Look at the mobile result first.
- Check the real-user data. If the page gets enough traffic, the report shows how real Chrome users experienced it over the previous 28 days. That matters more than the lab score.
- Open the Core Web Vitals report in Search Console. It groups similar pages and rates each group good, needs improvement or poor, so you can see whether the problem is one template or the whole site.
- Test on a real phone on mobile data. Turn the wifi off, tap your own ad or search result and watch what a customer sees.
- Note the biggest offenders. PageSpeed Insights lists the specific images and scripts slowing things down. That's your fix list.
Don't obsess over a perfect score. You want a site that feels instant to real people and passes the three metrics above. A 100 is a trophy.
The fixes, in the order we would tackle them
Work through this list from the top.
- Compress and resize images. Serve modern formats like WebP or AVIF, at the size they are displayed. A phone doesn't need a photo sized for a billboard. On an image heavy site this is where we would start.
- Cut third-party scripts. Audit every widget and tag. Remove what nobody uses, and load the rest after the main content so it doesn't block the page.
- Lazy-load what's below the fold. Images and videos further down the page should load as people scroll.
- Upgrade hosting and add a CDN. A content delivery network serves your site from a location close to each visitor, which matters when your customers are spread from Perth to Cairns.
- Turn on caching. Stop rebuilding the same page from scratch for every visitor.
- Trim the code. Remove unused plugins, along with the styles and scripts they left behind. If a bloated theme is the root cause, a rebuild may be cheaper than endless patching.
- Reserve space for images and embeds. Set dimensions so the layout doesn't jump as things load.
Some of these you can do in an afternoon with a free image compressor. Others need a developer. And sometimes the honest answer is that the site was built cheaply on a foundation that can't be made fast. We've written about the real cost of a cheap website, and speed is usually the first place it shows.
A worked example: the leak nobody could see
Here's a hypothetical. Say you run a landscaping business on the Central Coast. You spend $2,000 a month on Google Ads, sending people to a quote page built on a heavy template. The page has a full-screen video background, a slider, a chat widget, three tracking scripts and a quote form that loads last.
On office wifi it seems fine. On a phone in a car park on patchy mobile data, the form takes so long to appear that plenty of people give up. You don't see them leave. You see clicks in your ad account and not enough quote requests, so you assume the ads aren't working and raise the budget.
Now you fix the page. A single compressed photo replaces the video, and the slider goes. The chat widget loads after the form. Images are resized and the tracking is cleaned up. Your offer hasn't changed and the ad spend is still $2,000, but more of the people you're already paying for now reach the form and use it.
The business is made up, but the logic holds. You didn't buy more traffic. You stopped wasting the traffic you had. If your landing pages need more than speed, our guide to landing pages that print money covers the rest.
The cheapest growth lever you own
Most growth costs money. More ads, more content, more outreach. With speed, the traffic is already paid for. A faster site won't bring you more visitors. It stops you losing the ones you have.
And the benefit reaches every channel. Your ads convert better because visitors reach the offer. Your email clicks land on pages that load. Every dollar you spend on marketing works harder when the destination is fast.
To prove it to yourself, measure before and after. Record your mobile Core Web Vitals, bounce rate and conversion rate on your key pages, make the fixes, then compare the same numbers a month later. Now speed is a line item with a return you can see.
Common speed mistakes
- Testing on your own device. Your fast laptop and office connection hide the problem your customers see.
- Chasing a score instead of the experience. A perfect lab score means little if real visitors still wait.
- Adding a plugin to fix a plugin. Speed plugins stacked on a bloated site treat the symptom.
- Fixing it once and forgetting it. Every new widget and oversized image drags speed back down. Check it every quarter.
- Only fixing the homepage. Your service pages, product pages and landing pages are where the money is made. Test those too.
Fix the leak you cannot see
We build sites that feel instant, because a fast site respects the customer and converts more of them. If yours makes people wait, it is making them leave. Our web development team builds lean, fast sites and rescues slow ones.
Frequently asked questions
How fast should my website load?
Fast enough that the main content appears within about 2.5 seconds on a mobile phone and the page responds straight away when someone taps. The practical benchmark is passing Google's Core Web Vitals for real users, which you can check in PageSpeed Insights or Search Console. If your pages pass for mobile visitors and feel instant on a real phone, you're in good shape.
Does website speed affect SEO?
Yes. Google says Core Web Vitals are used by its ranking systems, alongside many other signals. Speed won't outrank better content on its own, but when pages are otherwise comparable a faster, smoother experience helps. A slow site also loses visitors who do arrive, which costs you the enquiries and sales the ranking was meant to bring.
What is the most common cause of a slow website?
Oversized images are a common culprit, along with too many third-party scripts and plugins, heavy page builder themes and cheap shared hosting. A PageSpeed Insights test shows which files slow your pages down, so you can fix the biggest offenders first instead of guessing.
Is it cheaper to speed up my website or rebuild it?
It depends on the foundation. If the site is reasonably built and the problem is images, scripts and hosting, optimising it is usually cheaper. If the theme itself is bloated or the site relies on dozens of plugins, patching can cost more over time than a lean rebuild. A proper audit tells you which situation you're in.