How to make your website load faster

Learning how to make your website load faster usually starts with a suspicion, not a number. A customer mentions the site felt slow on their phone. A quote request comes through after a long pause, or does not come at all. You open the site on your own phone, on data instead of Wi-Fi, and it takes long enough that you start to wonder how many people give up before the page appears. That suspicion is worth taking seriously. Most of your visitors are on phones, many of them are on mobile data, and a page that takes a few extra seconds can quietly cost you enquiries every week.

The good news is that most small business websites are slow for a short list of fixable reasons. Oversized photos, plugins and scripts nobody uses any more, cheap crowded hosting, and a homepage that tries to load everything at once account for the large majority of slow sites. You do not need a rebuild to fix most of it, and you do not need to be technical to fix the biggest wins. This guide walks through the fixes in the order that matters, with Canadian examples throughout, so you can work through them one afternoon at a time.

First, know what "fast" actually means

Google measures website speed with three numbers, called Core Web Vitals, taken from real visitors using Chrome. Each one describes something a customer would notice, and each has a threshold Google considers good. Google checks these at the 75th percentile of page loads, split by mobile and desktop, which means at least three quarters of visits need to hit the mark.

• Largest Contentful Paint (LCP): how long until the main content appears. Good is 2.5 seconds or less.
• Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.
• Cumulative Layout Shift (CLS): how much the layout jumps around while the page loads. Good is a score of 0.1 or less. This is the one that makes a visitor tap the wrong button because the page shifted under their finger.

Those three numbers are the targets, but the plain-language test is simpler: on a phone, on mobile data, your homepage should show its main content within about two and a half seconds, respond to taps without a noticeable delay, and stay still while it loads. If it does that, your site is fast enough for almost every small business purpose. Chasing a perfect score beyond that point is a hobby, not a business decision.

Speed also matters for search. Google has said that page experience signals, including Core Web Vitals, are among the things its systems consider when ranking pages. Speed is one signal among many, and a fast site with thin content will not outrank a slower site with the best answer. But when two pages answer a question equally well, the faster one has the edge, and the faster one also converts more of the visitors it does get. Fixing speed is worth doing for the customers first, and the search benefit follows. Our guide to what SEO is explains where speed fits among the other ranking factors.

Test before you change anything

Guessing wastes time. A site can feel slow because of one huge photo, or because of a slow server, or because of a chat widget, and each cause has a different fix. Measure first, write the numbers down, and measure again after each change so you know what actually helped.

PageSpeed Insights is the place to start. It is a free Google tool at pagespeed.web.dev. Enter your homepage address and run the test, then do the same for your most important service page. Look at the mobile results first, because that is how most of your customers will visit. If your site has enough traffic, the top of the report shows real-user data, which is the most honest picture of what visitors experience. Below that, the lab test lists specific problems in rough order of impact, with the estimated time each one could save. Read that list before you change anything. It tells you whether your problem is images, scripts, the server, or something else entirely.

Google Search Console has a Core Web Vitals report that groups your pages by status across the whole site, so you can see whether the problem is one page or every page. If you have not set it up yet, our guide to setting up Google Search Console covers it step by step. WebPageTest is a free tool worth using when you want a second opinion: it tests from different locations and connection speeds, which matters in Canada, where a visitor in rural Ontario or northern British Columbia may be on a far slower connection than a visitor in downtown Toronto.

Run each test twice and look at the trend rather than a single number. Speed scores move a little from run to run as networks and servers vary, so a one-point change means nothing. What matters is the direction after a fix, and the real-user numbers at the top of the PageSpeed Insights report. Also test on a real phone, on data, with your own hands. Tools are useful, but tapping through your own site the way a customer would will show you the delays and the layout jumps that a score hides.

Fix 1: Shrink your images

Images are usually the heaviest part of a page, so they are the best place to start, and the fix is almost always free. A photo straight off a phone camera can be 4 or 5 megabytes. Shown at the size of a postcard on a web page, it should be closer to 100 kilobytes. When a homepage has five photos like that, the visitor is downloading 20 megabytes before they see anything, which is slow on any connection and painful on mobile data.

Resize before you upload, instead of relying on the page to shrink a huge image. A banner image on a website rarely needs to be wider than the screen it appears on, so a width of around 1600 pixels is plenty for a full-width banner, and far less for smaller images. Then compress it. Free tools such as Squoosh, or the built-in compression in WordPress, Shopify, Squarespace, and Wix, can shrink a photo by 60 to 80 percent with no visible loss of quality. Where your platform supports it, use a modern format such as WebP, which is smaller than JPG or PNG at the same visual quality. Many compression plugins convert to WebP automatically, so this often comes free with the first fix.

Load images the smart way. Images further down the page do not need to load straight away, so let the browser load them only when the visitor scrolls near them. In HTML that is one attribute, loading="lazy", and most modern platforms add it automatically. Do not lazy load the main hero image, though. The hero is the first thing a visitor sees, and delaying it makes the whole page feel slow. The opposite rule applies there: make sure the hero image is easy for the browser to find early, which usually means putting it in the page HTML rather than loading it through a script.

Set width and height for every image, or reserve the space some other way. When the browser does not know how big an image will be, the page loads the text first and then jumps when the image arrives. That jump is the layout shift that frustrates visitors and hurts your CLS score. A reserved space keeps the page still. This one change often fixes a failing CLS score on its own, and it takes minutes.

Fix 2: Remove what you do not use

After images, the most common slowdown on a small business site is everything that was added over time and forgotten. Every WordPress plugin or Shopify app adds code that loads on your site, whether you are actively using it or not. Every chat widget, popup, slider, tracking pixel, review badge, and booking embed loads its own JavaScript, and that code has to be downloaded, parsed, and run before the page feels responsive.

Go through your installed plugins and apps and remove anything you added once and forgot about. A plugin you installed for a Christmas promotion two years ago is still slowing down every page today. The same applies to page-builder elements you no longer use and to old forms, popups, and announcement bars. This is one of the fastest wins available and it costs nothing. If your site is on WordPress, also check whether you have two plugins doing the same job, such as two SEO plugins or two contact form plugins, and keep only one.

Be honest about third-party scripts. A chat widget is useful if customers actually use it to ask questions, but many small businesses install one, get almost no chats, and pay for it in speed on every single page load. If the widget earns its place, keep it, but consider loading it only after the visitor has been on the page for a while, or only on the contact page. The same test applies to social media feeds, review widgets, and tracking tags. Each one should earn its place by bringing enquiries or sales. If it does not, remove it and watch your scores improve.

Sliders deserve a special mention. A homepage slider with five large photos looks impressive in a design meeting and performs badly in real life. Most visitors see only the first slide, if they see it at all, yet the browser downloads every slide before the page is ready. A single strong image with a clear headline and one next step loads faster, reads better, and converts better than a rotating carousel. If your homepage still has a slider, replacing it with one static hero is usually the highest-impact speed fix you can make in an afternoon.

Fix 3: Sort out your hosting

If the page waits a long time before anything appears at all, the problem is usually the server, not the page. That waiting time is called time to first byte, and it is the first thing PageSpeed Insights reports. No amount of image compression will fix a server that takes two seconds to respond, because the browser is waiting for the server before it can start on anything else.

Cheap shared hosting is the usual cause. On a crowded shared server, your site shares resources with hundreds of other sites, and a busy neighbour can slow you down. The server may also be far away: a host with data centres only in the United States or overseas adds travel time for every Canadian visitor. Our guide to how much web hosting costs in Canada covers what to compare when choosing a host, including server location and the difference between shared, managed, and static hosting.

For many small business sites, the fastest setup is a static site: pages that are built ahead of time and served from a global network, with no database to wait on. That is how this site is built. There is no database query, no page assembly on every visit, and no server-side code to slow the first response. If your site is on WordPress or another system that builds every page on demand, ask your host whether server-side caching is available, or talk to your developer about it. The right answer depends on your site and your budget, but a host that takes a long time to answer is a problem worth fixing at the source, not patching around.

Fix 4: Turn on caching and use a CDN

Caching tells returning visitors' browsers to keep files such as images, CSS, and JavaScript rather than downloading them again on every visit. For a customer who visits your site three times before calling, that is the difference between a fast second visit and a slow one every time. Most hosting providers have a one-click caching option in their dashboard, and on WordPress a plugin such as WP Rocket handles it. Server-side caching is similar: it keeps a ready-made copy of your pages so the server does not rebuild them for every visit.

A content delivery network, or CDN, stores copies of your files on servers in many locations, so visitors download them from somewhere nearby instead of from one distant server. Even for a business that serves only one Canadian city, a CDN can cut load times, because your visitors are not all in the same place and their routes to your server vary. Many hosts include a CDN in their plans, and free tiers exist for small sites. Check that your server also uses Brotli or Gzip compression. Most modern hosts enable it by default, but it is worth confirming, because compression shrinks every file the server sends, and it is usually a setting rather than a project.

Fix 5: Trim fonts and code

Fonts are a quiet slowdown. Every font family, weight, and style you load is a separate file, and a site that loads four weights of two fonts is downloading eight files before the text looks right. Limit yourself to one or two font families and the weights you actually use, and host the fonts with your site where possible rather than loading them from a third party on every visit. A visitor should not wait for a decorative font before they can read your phone number.

Code is the same story at a smaller scale. Minifying CSS and JavaScript, which means removing the spaces and comments that humans need but browsers do not, shrinks the files the browser must download. Removing unused CSS has a bigger effect on sites built with page builders, which often load styling for every widget on every page even when a page uses only a few. Most of this is developer work, but it is worth asking about if your PageSpeed report flags unused CSS or JavaScript as a large saving. Defer the code that is not needed straight away, so the browser can show the page first and run the extras afterwards. The goal is simple: load only what each page needs, and load the visible part first.

Fix 6: Rethink video and sliders

An autoplay background video is the single heaviest thing you can put on a homepage. A short video can be several megabytes, and on a phone it plays whether the visitor asked for it or not, using their data and delaying everything else. If the video is essential to the story, keep it, but do not autoplay it on mobile. Show a still image with a play button instead, and let the visitor choose to watch. The same applies to embedded maps, social feeds, and booking widgets on the homepage: each one loads its own code, and each one should earn its place on the first screen rather than being there by habit.

What needs a developer, and what to do first

Most of the fixes above are things a business owner can do in an afternoon: resize and compress images, delete unused plugins, turn on caching, replace a slider with a single hero image, and test the result. The fixes below are worth handing to a developer, because they need code changes and a mistake can break the site.

Start with the order in this guide, and work in this order of priority. Test and write down your numbers first, so you can compare later. Shrink your images, starting with the homepage. Fix the first screen: make sure the hero image loads early and is not lazy loaded, and that the main headline and call to action are visible without waiting. Remove what you do not use: plugins, apps, widgets, and tags. Set image sizes so the page does not jump. Then talk to your host or developer if the page still waits a long time before anything appears, because that points to hosting or server setup rather than the page itself. Test again and compare with your starting numbers.

When you do hire help, ask for a fixed scope and a fixed price in CAD, with the starting and ending scores in writing. A speed project should be judged by the real-user numbers in PageSpeed Insights and by what customers experience on a phone, not by a single lab score on a single day. Be cautious of anyone who promises a perfect score or a specific ranking improvement. Speed helps rankings and conversions, but nobody can guarantee either one, and a developer who promises them is selling a number, not a result. Our pricing page explains how our projects are structured, and our guide to what to ask a web designer before hiring covers the questions that separate a good hire from an expensive lesson.

Keep it fast over time

Speed is not a one-time fix. Every new photo, plugin, and widget adds weight, and a site that is fast today can drift back to slow over a year of small additions. A simple routine keeps it fast without much effort.

Every time you upload an image, resize and compress it first, and set its size. That is the whole routine for uploads, and it takes a minute once it becomes a habit. Once a quarter, check your plugins and scripts and remove anything that is no longer used, and run PageSpeed Insights on your homepage and your top service page to see whether anything has slipped. Once a year, or whenever you change hosts or redesign, run the full test again and compare it with the numbers you wrote down at the start. If a redesign is on the horizon, make speed part of the brief from the beginning: a fast site is far easier to build than to retrofit, and it is cheaper to specify than to fix afterwards. If you are considering a new site, our guide to how long it takes to build a website covers the timeline and the decisions that shape it.

A fast website is not a technical luxury. It is a customer service decision. Every second a visitor waits is a second they could spend calling a competitor whose site loaded first. The fixes in this guide are not exotic, and most of them cost nothing but an afternoon. Measure first, fix the biggest win, measure again, and keep the routine going. That is how a small business website stays fast.

How Webloped fits in

We are a web design and AI automation company based in Cambridge, Ontario. We build fast websites for Canadian small businesses: pages that are built ahead of time, served from a global network, and light on the code and widgets that slow most sites down. Our services page outlines what we do, and our pricing page explains how projects are structured. If your website is slow and you would rather have someone else sort it out, send us a message and we will look at your speed test results and tell you honestly what would help, even if the fix is something you can do yourself. You can also reach us by email at contact@webloped.ca.

Frequently asked questions

How fast should my website load?

Your main content should appear within about 2.5 seconds on a phone, the page should respond to taps within 200 milliseconds, and the layout should stay still while it loads. Those are Google's thresholds for a good Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift, measured across at least 75 percent of visits. If your site meets those three numbers, it is fast enough for almost every small business purpose.

How do I check my website speed for free?

Use Google's PageSpeed Insights tool at pagespeed.web.dev. Enter your address, run the test, and look at the mobile results first, especially the real-user data at the top if your site has enough traffic. The report lists specific problems in rough order of impact, with the estimated time each fix could save. Google Search Console also has a Core Web Vitals report that shows the status of your pages across the whole site.

What slows down a small business website the most?

Oversized images, too many plugins and scripts, slow shared hosting, heavy page builders, sliders, chat widgets, and tracking tags loaded on every page. For most small sites, images are the single biggest cause, and resizing and compressing them is the fastest free fix. After images, the next biggest wins are usually removing unused plugins and widgets, and fixing slow hosting when the server takes a long time to respond.

Will making my website faster improve my Google ranking?

Speed is one of the signals Google considers, through Core Web Vitals, but it is one signal among many. A faster site will not outrank a page with a better answer, but when two pages answer a question equally well, the faster one has the edge. The bigger benefit is usually conversions: a fast site keeps more of the visitors it already gets, which is worth more than a small ranking change.