You tap a link, stare at a blank screen for a few seconds, then hit back. Everyone has done it, and your customers do it too. They don't email you to say the site is slow. They just leave and open a competitor's page instead.
You don't need to be a developer to find out whether your site has this problem. This guide shows you how to test it in about ten minutes with Google's free tools, how to read the results, and the usual suspects behind a slow site.
What a slow website actually costs you
Speed isn't just a technical detail. It hits your business in three ways:
- Lost visitors: mobile users are impatient. If nothing useful appears quickly, they go back to the search results.
- Wasted ad spend: you pay for every ad click. When the page loads slowly, some of those people leave before they ever see your offer.
- A weaker position on Google: Google's ranking systems take page experience, including loading speed, into account. Relevant content still matters most, but when pages are otherwise similar, the better experience has the edge.
A sluggish site also feels unprofessional. It's hard to trust a business whose own website stutters.
How to test your website speed in 10 minutes
1. Open PageSpeed Insights
Go to PageSpeed Insights, Google's free testing tool. Paste in your homepage URL and click Analyze. Results take about half a minute.
2. Start with the mobile tab
You'll see Mobile and Desktop tabs. Check mobile first. Most of your visitors are probably on phones, and that's where sites tend to struggle.
3. Understand the two kinds of results
The report has two sections that people often mix up:
- Real-user data: collected from actual Chrome users over the past 28 days. It only appears if your site gets enough traffic, so new or small sites often won't have it.
- Lab diagnostics (Lighthouse): a single simulated page load, with a performance score from 0 to 100.
If real-user data is available, trust it first, because that's what your customers actually experience. The lab score is great for finding problems, but it can vary from one run to the next.
4. Focus on three numbers
Ignore most of the jargon and look at the three Core Web Vitals:
- LCP (Largest Contentful Paint): how long the main content takes to appear. Good is 2.5 seconds or less.
- INP (Interaction to Next Paint): how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.
- CLS (Cumulative Layout Shift): how much the layout jumps around while loading. Good is 0.1 or less.
We explain each one in plain English in Core Web Vitals explained.
5. Test the pages that make money
Your homepage usually gets the most love. Also test product pages, service pages and any landing page you're running ads to. That's where people decide whether to contact you.
6. Try it yourself on a phone
Finally, be your own customer. Use your phone on mobile data, open a private tab and load your site. How long until you see something useful? Tap the menu, open a product, fill in the form. Your gut feeling here often says more than any score.
Common reasons websites are slow
The Opportunities and Diagnostics sections of PageSpeed Insights list specific issues. On small business sites, these come up again and again:
- Oversized images. A phone photo can be several megabytes when the page only needs a fraction of that. Resize, compress and use modern formats such as WebP or AVIF.
- Too many plugins and add-on scripts. Every tracking tag, chat widget and plugin adds weight. Together they can drag a page down, especially on budget phones.
- Bloated themes. Many off-the-shelf themes ship every feature imaginable: sliders, animations, multiple fonts. You use a fraction, but visitors download all of it.
- Slow or distant hosting. If the server is slow to respond, nothing else can make up for it. Reliable hosting plus a CDN helps pages reach visitors faster.
- No caching. Without a cache, the server rebuilds every page for every visit. Proper caching can make a big difference without changing a pixel of the design.
Fix it yourself or call in help?
A few fixes are easy to do yourself:
- Resize and compress images before uploading them.
- Remove plugins and scripts you no longer use.
- Drop autoplay videos or sliders at the top of the page if they aren't essential.
If the score is still poor after that, the cause usually lies in how the site was built: its code, how it loads fonts and scripts, or server configuration. That needs a specialist. Sometimes a few tweaks are enough; sometimes rebuilding on a leaner setup is cheaper in the long run.
Once your site is fast, the next step is helping Google understand it. Our SEO checklist for a new website walks you through it.
The bottom line
A slow website leaks money quietly. You never see the visitors who leave, but your sales feel it. Ten minutes with PageSpeed Insights tells you where you stand.
Every site Bina builds is optimized for Core Web Vitals and speed-tested on multiple devices before handover. If you've run the test and aren't sure what to fix first, send us your link. We'll take a look and tell you what to prioritize, with no strings attached.
