How to Speed Up a Small Business Website

I have been building websites for more than 15 years, and if you read why I'm done with WordPress, you know speed is one of the things I care about most. Not because a speed score is fun to brag about, but because a slow site gets in the way of the whole point of having a website. Somebody found you. They tapped your link. Now they are staring at a blank screen on their phone.

Here is the good news. Most small business sites are not slow because of some deep technical mystery. They are slow because of a handful of very common things, and most of those can be fixed without starting over.

This is the practical version. How to measure your speed, what the numbers mean, and the fixes I would go after first.

Why website speed matters for a small business

A website has one job for most small businesses. Get the visitor to call, book, buy or fill out a form. Every second they spend waiting is a second they could hit the back button and tap your competitor instead.

Speed also plays a part in search. Google says its core ranking systems look to reward content that provides a good page experience, and that Core Web Vitals are used by its ranking systems. But Google is also clear that a great score does not guarantee top rankings, and that chasing a perfect score just for SEO "may not be the best use of your time." Relevant, helpful content still comes first.

So here is how I think about it. Speed will not save a bad website. But a slow website can drag down a good one. Fast enough is the goal, not perfect.

Step 1: Test your site the right way

Before you change anything, get a baseline.

The easiest free tool is Google's PageSpeed Insights. Paste in your URL and it gives you two different kinds of data:

• Real-user data (field data). According to Google's About PageSpeed Insights page, this comes from the Chrome User Experience Report and reflects real visitors over the previous 28 days. If your site does not get enough traffic, this section may be empty.
• Lab data. This is a simulated test run with Lighthouse. It is useful for finding problems, but Google notes it may not capture real-world bottlenecks.

A few tips when you test:

• Test on mobile first. Most local customers are finding you on their phone, and the mobile test is usually the tougher one.
• Test more than your homepage. Check your top service page, your contact page and your most-visited blog post too.
• Run it more than once. Google says lab scores can change from run to run even if you changed nothing, because of network and hardware variability.
• Check Search Console. If your site is verified, the Core Web Vitals report in Google Search Console shows how groups of your pages are doing over time.

Write down your starting numbers. You want to know whether your fixes actually helped.

Step 2: Understand the three numbers that matter

PageSpeed Insights throws a lot at you. You do not need all of it. Start with the three Core Web Vitals. Here are the "good" targets from Google's Web Vitals guide:

• Largest Contentful Paint (LCP) measures loading. It is how long it takes for the biggest thing on the screen, usually a hero image or a big headline, to show up. Good is 2.5 seconds or less.
• Interaction to Next Paint (INP) measures responsiveness. When someone taps a button or opens a menu, how quickly does the page react? Good is 200 milliseconds or less.
• Cumulative Layout Shift (CLS) measures visual stability. It is that annoying moment when you go to tap something and the page jumps. Good is 0.1 or less.

Google recommends measuring these at the 75th percentile of page loads, which basically means the site should feel good for most of your visitors, not just the ones on fast Wi-Fi.

The lab "performance score" out of 100 is also there. Google calls 90 and up good. It is a helpful check, but I would focus on the three numbers above, because they reflect what real people experience.

Step 3: Fix your images first

If I could only fix one thing on most small business sites, it would be images.

The web.dev article on browser-level lazy loading points out, using HTTP Archive data, that images are the most-requested asset type for most websites and usually take up more bandwidth than anything else. And on small business sites, it is common to see a giant photo straight off a camera or phone uploaded at full size.

Here is the image checklist:

• Resize before you upload. If an image displays at 1,200 pixels wide, do not upload one that is 5,000 pixels wide.
• Compress it. Most photos can get much smaller without anyone noticing a difference.
• Use a modern format. Google's web.dev guide to using WebP images says WebP files are usually 25 to 35 percent smaller than comparable JPEG and PNG files.
• Lazy-load images further down the page. Adding loading="lazy" to an image tells the browser to wait until the visitor scrolls near it, as MDN explains in its lazy loading guide.
• Do not lazy-load your hero image. This one trips people up. Google specifically warns not to lazy-load images that are visible when the page first loads, especially the LCP image. That top image should load right away.
• Always set image width and height. This lets the browser save the right amount of space before the image arrives, so the page does not jump around. That helps your CLS score.

If you only do this step, you may see a real difference. Just test it to be sure.

Step 4: Make your main content load first

Your LCP number is usually about one thing, the biggest element at the top of the page. Google's Chrome team lists the most effective ways to improve it in The most effective ways to improve Core Web Vitals. A few that apply to most small business sites:

• Make the hero image easy to find. Use a normal image tag in the HTML, not something that needs JavaScript to load first. Google notes that hiding the main image behind JavaScript is always slower.
• Give it priority. Adding fetchpriority="high" to the main hero image tells the browser it matters most.
• Get the extra stuff out of the way. Non-critical scripts and widgets can be loaded later so they do not compete with the content people actually came to see.

You do not need to understand every detail to ask your web person the right question. "What is our LCP element, and is it loading as early as possible?" is a great one.

Step 5: Cut plugins, scripts and widgets you do not need

This is the one I feel the strongest about.

Over time, most sites pile up extras. A chat widget. Two analytics tools. A popup. A social feed. An old tracking pixel from a campaign that ended a long time ago. A slider nobody clicks. On WordPress, it is often a stack of plugins, some doing the same job.

Each one may seem small, but they add up. Google's Chrome team says sites are shipping more JavaScript than ever, and that too much JavaScript can hurt how quickly a page responds when someone taps it. They also recommend cleaning up old tags in tag managers.

Here is a simple way to audit your site:

• List every plugin, script and widget on the site.
• Ask what each one does for the business. If nobody can answer, it is a candidate to remove.
• Look for duplicates. Two form tools, two SEO tools, two analytics setups.
• Remove one thing at a time and retest. That way you know what made the difference and nothing breaks without you noticing.

The fastest code on your website is the code that is not there.

Step 6: Stop the page from jumping around

A page that shifts while you are trying to read or tap is frustrating, and it shows up in your CLS score.

According to web.dev's guide to optimizing CLS, the most common causes are:

• Images without dimensions
• Ads, embeds and iframes without dimensions
• Content injected into the page after it loads
• Web fonts

The fixes are usually simple. Set width and height on images. Reserve space for embeds like maps and videos. Be careful with banners and popups that slide in and push the page down. The Chrome team also notes that banners that animate in from the top or bottom often contribute to layout shift.

Step 7: Look at your hosting and use a CDN

Sometimes the problem is not the page. It is how fast the server responds in the first place.

Google calls this Time to First Byte, and its Chrome team says the best ways to improve it are serving content from close to your visitors and caching it. Their recommendation for doing both is a CDN, a content delivery network that keeps copies of your site on servers in many locations.

A few things to check:

• Is your hosting plan very cheap and very crowded? Shared hosting can be fine for small sites, but if your server is slow before the page even starts loading, nothing else you do will fully fix it.
• Is caching turned on? Many hosts and platforms offer it, but it is not always on by default.
• Are you using a CDN? Many hosting companies include one or make it easy to add.

Step 8: Keep it fast

Speed is not a one-time project. Sites slow down a little at a time as new images, plugins and scripts get added.

A simple habit works well here:

• Retest your key pages after big changes. New homepage, new plugin, new tracking script.
• Check Search Console's Core Web Vitals report every month or so.
• Set a few rules for anyone who edits the site. Resize images before upload. Ask before adding a new plugin or widget.

This is the same mindset I talked about in how to update old blog posts. A little regular maintenance beats a big rescue project later.

Common website speed mistakes

These are the ones I would watch out for:

• Chasing a perfect 100. Google itself says a perfect score just for SEO may not be the best use of your time. Aim for good, then get back to running your business.
• Only testing on desktop on fast office internet. Your customers are on phones.
• Lazy-loading everything, including the hero image. It makes the most important image show up later.
• Adding a speed plugin to fix problems other plugins caused. Sometimes the better fix is removing the thing causing the problem.
• Uploading huge photos straight from a phone or camera.
• Making a bunch of changes at once. If something breaks, or the score gets worse, you will not know why.

Final thoughts

You do not need to become a developer to have a fast website. Test your key pages on mobile. Focus on the three Core Web Vitals. Fix images first. Make sure your main content loads right away. Cut the extras you do not need. Stop the page from jumping. Then check it every so often so it stays fast.

A fast site pairs best with a site that has the right pages and a clear next step for visitors. If you are still working on that part, start with what pages a small business website should have, and make sure your site matches your listing if you have already worked through how to get your business on Google Maps.

And if your site is slow, bloated, or just not bringing in calls, that is exactly the kind of thing we build around at Built by Knup. Lean pages, only what the business needs, and a clear path from "found you" to "contacted you." If you are shopping around, here is how to choose a web designer for your small business.

FAQ

How do I check how fast my website is?

Use Google's free PageSpeed Insights tool at pagespeed.web.dev. It shows real-user data from the last 28 days when your site has enough traffic, plus a simulated lab test with suggestions. If your site is verified in Google Search Console, the Core Web Vitals report there shows how your pages are doing over time.

What is a good page load time for a website?

Google's main loading target is Largest Contentful Paint, which should happen within 2.5 seconds for a good user experience. Google also recommends Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads.

Does website speed affect SEO?

It can. Google says Core Web Vitals are used by its ranking systems and that good page experience aligns with what its systems reward. Google also says a good score does not guarantee top rankings, and relevant, helpful content still matters most.

What slows down a website the most?

On many small business sites, the biggest culprits are oversized images, too many plugins, scripts and widgets, slow hosting, and the main hero image loading late. Images are the most-requested type of file on most websites, so they are usually the best place to start.

Can I speed up my website without rebuilding it?

Usually, yes. Resizing and compressing images, using modern formats like WebP, lazy-loading images below the fold, removing unused plugins and scripts, setting image dimensions, and turning on caching or a CDN can all help without a full rebuild. Test before and after each change so you know what worked.