The Real Cost of a Slow Website
Fifty-three percent of mobile users leave a page that takes more than 3 seconds to load. That's not a hypothetical statistic. That's a customer who found you, clicked your link, and left before seeing a word of your content.
The cost isn't abstract either. A lost lead is revenue you didn't make. A visitor who bounced because the page was loading is someone who might have called you, submitted a form, or placed an order. Slow sites leak money in two ways: direct bounce losses and damage to your search ranking, which reduces traffic in the first place.
Most small business owners have no idea how fast or slow their site actually is. The reason is simple: they test it from their own laptop, on their home wifi, after the site is cached. That's the best-case scenario. Your customers are testing it on their phones, on 4G networks, often in areas with mediocre signal. The experience they have is completely different from what you see.
What You're Actually Measuring
Speed has two parts. The first is straightforward: how long it takes for the page to start showing up on screen. The second is less obvious but more important to the user experience: how stable and usable the page is while it's loading.
Google calls the stability part "Core Web Vitals." Basically, it's measuring whether content jumps around on the page while assets are still loading, whether the page feels interactive before it fully loads, and whether any unexpected delays frustrate the user mid-interaction. If you've ever been trying to click a button and the page suddenly shifts and you click something else, that's a bad Core Web Vital.
You don't need to understand all of this in detail. You need three things: your score, whether that score is good or bad, and the top 3 issues the tool identifies.
Step 1: Run Google PageSpeed Insights
Go to pagespeed.web.dev. It's Google's official speed and Core Web Vitals testing tool, it's free, and it doesn't require an account.
Paste your homepage URL into the box. Wait 20 to 30 seconds while it tests.
You'll get two scores: one for mobile, one for desktop. The mobile score is what matters. Most websites score reasonably well on desktop (where they're being accessed from powerful computers with fast wifi) and poorly on mobile (where users actually access them). Pay attention to that gap.
How to Read Your Score
Ninety to one hundred is good. Fifty to eighty-nine means there's room to improve. Below fifty is actively hurting your business. Those aren't arbitrary cutoffs. They're based on real user behavior and conversion data.
Mobile score is your primary concern. Desktop score is secondary context.
If your mobile score is 75, you're probably fine. Most users can get to your content. You're not losing leads just because the page is slow. If your mobile score is 35, you have a real problem that's costing you traffic and business.
Step 2: Find the Opportunities Section
Below your score, PageSpeed shows a section called "Opportunities." This is the useful part. It lists specific things you can fix, ranked by how much they'll improve your score.
The top three issues on most websites are the same: images that are too large, render-blocking resources (usually fonts and JavaScript loading at the wrong time), and slow server response time.
Screenshot or bookmark this section. It's useful whether you fix it yourself or hand it to a developer.
What the Top Issues Actually Mean
Oversized images. A photo taken on a smartphone is often 5 to 8 megabytes. On a website, it should be 100 to 300 kilobytes. That's a 20x reduction. You're sending massive files over the network when a much smaller file looks identical on screen. This is the single easiest thing to fix.
Render-blocking resources. Something is making the browser wait before it can show the page. Usually it's a font file loading or a third-party script running at the wrong time. A developer can fix this in an hour. It's not a structural problem. It's an ordering problem.
Slow server response time. Your hosting server is taking too long to respond to requests. This is less common for WordPress and Shopify sites (both providers handle this reasonably well) and more common for older custom-built sites or very cheap hosting plans.
Step 3: Run GTmetrix for More Detail
Go to gtmetrix.com. Enter your homepage URL. Run a free test.
GTmetrix shows you a Waterfall chart. It's a visualization of every asset the page is loading and how long each one takes. Most of this is noise. What you're looking for are assets taking more than 2 seconds to load. Note what they are. Usually they're images, videos, or third-party scripts.
GTmetrix will also give you specific recommendations. The top one or two are usually worth reading. The rest are technical optimization details.
Three Fixes That Solve Most Speed Problems
Image compression is the fastest win. Go to squoosh.app. It's a free image compression tool built by Google. You don't need an account. Drag a large image from your site into it. Squoosh will show you before and after file sizes. A 2.8 megabyte image often compresses to 180 kilobytes without any visible quality loss. If your site has ten images and each one compresses by 80 percent, you've solved a major speed problem.
If you're on WordPress, your next move is plugin cleanup. Go through your plugin list and deactivate anything you don't actively use. Every plugin adds some overhead, even if it's not doing anything visible. Even deactivated plugins add a small amount of load time. Delete the ones you don't need.
Finally, set up Cloudflare's free CDN. A CDN serves your site from servers around the world instead of from a single server location. Someone in London loading your site from a server in California is slower than loading it from a server in London. Cloudflare handles the distribution for free. The setup takes about 30 minutes once, mostly waiting for DNS changes to propagate.
What to Do Based on Your Platform
If you're on Squarespace, Wix, or Shopify, you have limited control over speed optimization. These platforms handle most infrastructure automatically. Your main job is compressing images before uploading them. Don't spend time chasing advanced optimizations on these platforms. Image compression and nothing else will give you the biggest return.
If you're on WordPress, you have full control. All three of the fixes mentioned above are doable by you or a developer. Start with image compression. That's free and requires nothing but your time.
If you have a custom-built site, take the PageSpeed report and hand it to your developer. They'll understand what to fix. You've done the hard part: quantifying the problem.
Don't Panic at the Number
A mobile score of 60 is not a crisis if your content is good and the user experience is clean. The page loads in reasonable time, the layout doesn't jump around, and visitors can read and interact with your content. A score of 22 means something is genuinely broken. Something is taking 10 seconds to load or the page is basically unusable until it fully renders.
If your score is 65, you don't need to rebuild your site. If your score is 22, you need to take action. Most sites fall somewhere in the middle where improvement is worth the effort but not worth panic.
What's Next
If you run this audit and find problems bigger than a few image files, or if you'd rather hand the fix to someone than manage it yourself, that's the kind of thing I do. Reach out if you want to talk through what you found.
---
FAQ
What is a good Google PageSpeed score?
Ninety or higher is excellent. Seventy to eighty-nine is solid and acceptable for most businesses. Fifty to sixty-nine means there's room for improvement and your site is probably losing some visitors because of speed. Below fifty means your speed problem is actively hurting you and it's worth fixing soon.
Does website speed affect my Google ranking?
Yes. Google's algorithm includes page speed and Core Web Vitals as ranking factors. A faster site gets a small ranking boost. More importantly, a faster site has lower bounce rates, which signals to Google that your content is relevant and useful. The ranking effect is indirect but real.
What is Core Web Vitals and why does it matter?
Core Web Vitals measure three things: how quickly the first visible content appears (LCP), how stable the layout is while loading (CLS), and how quickly the page responds to user input (INP). These metrics track the actual user experience, not just raw speed. A page that loads content in order and doesn't shift around feels faster than a page that jumps and reorganizes itself even if the raw load time is the same.
How do I compress images for my website for free?
Use squoosh.app. Drag your image into the tool. Adjust the quality slider if needed. Download the compressed version. It usually takes 30 seconds per image and reduces file size by 60 to 80 percent without visible quality loss. For bulk image compression, ImageMagick (command line) and XnConvert (graphical) are free alternatives.
My PageSpeed score is low. Do I need to rebuild my site?
No. A low score usually means a few specific problems, not a broken foundation. Oversized images, plugin bloat, or a slow server are fixable in hours or days. You would only need to rebuild if your site is so old that the codebase itself is unmaintainable, which is rare for sites that are still generating traffic.