Why a slow website costs you calls, and how to fix it

What a slow site costs you

A person searching for a locksmith, a plumber or a dentist with a toothache has several options a thumb tap away. If your page sits on a white screen while the next one is already showing a phone number, you have lost that call before they saw your name. You will never see those people in your numbers. They just do not call.

Speed matters to Google too. Its ranking systems look at page experience, including a set of measurements called Core Web Vitals. Google has been clear that helpful, relevant content still matters more, so a fast but thin page will not beat a slower page that answers the search much better. Between two otherwise similar pages, though, being slow and jumpy does you no favors.

A slow page also wastes ad money. If you pay for a click and the page is still loading when the visitor gives up, you paid for nothing. Google Ads looks at landing page experience as part of how it rates your ads, and a page that crawls on a phone is a poor experience by any measure.

How Google measures page speed

Core Web Vitals break speed into things a visitor actually feels. Google publishes a good threshold for each one, and its free tools grade your pages against them. You do not need to memorize the thresholds. You need to know which pages fail and why.

• Largest Contentful Paint: how long until the main thing on the screen, usually your headline or main photo, finishes loading.
• Interaction to Next Paint: how quickly the page responds when someone taps a button or opens the menu.
• Cumulative Layout Shift: how much the page jumps around while it loads, the thing that makes people tap the wrong button.

How to test your own site

Start with PageSpeed Insights, Google's free testing tool. Run your home page, then your most important service pages, and look at the mobile results first. If your site gets enough visitors, the top of the report shows real-world data collected from Chrome users over recent weeks. That is the data Google actually uses. Below it is a lab test, a simulated page load that is good for finding problems but can swing from one run to the next.

If you have Google Search Console set up, its Core Web Vitals report sorts your pages into good, needs improvement and poor, using that same real-world data. It shows whether a problem affects one page or the whole site.

Then do the low-tech test. Pick up your own phone, turn off Wi-Fi, and open your site from a Google search. Notice how long it takes before you could tap the phone number. That is your customer's experience.

Do not chase a perfect score. The goal is a site that loads quickly on a phone and stays still while it does. A score of 100 on a page nobody calls from is worth nothing.

The usual causes on local business sites

When a small business site is slow, the cause is usually one of a few familiar problems, and often more than one at once.

• Huge photos. A photo straight off a phone or from a photographer is often far larger than the screen needs. This is the most common cause and the easiest to fix.
• Video backgrounds and sliders. They load a lot of data before the customer sees anything useful.
• Too many plugins and add-ons. Every chat widget, review widget, pop-up tool, social feed and tracking script adds code that has to load.
• Heavy page builders. Some drag-and-drop builders produce bloated pages even when the design looks simple.
• Cheap or crowded hosting. If the server is slow to respond, everything after it is slow too.
• Web fonts. Several font families in several weights add up quickly.
• Content that moves. Banners, cookie notices and images without set dimensions push the page around as they load.

Fixes that make the biggest difference

Most of the improvement comes from a short list of changes. Work through them in this order and retest after each one so you know what helped.

• Resize and compress images, and save them in a modern format like WebP. Load images further down the page only when the visitor scrolls to them.
• Replace a video background with a strong still photo of your real work.
• Audit your plugins and scripts. Remove anything you are not using and question anything you cannot name a reason for. Keep the tracking you actually look at.
• Turn on caching and, if your host offers one, a content delivery network, which serves your files from a server near the visitor.
• Limit fonts to one or two families and only the weights you use.
• Give images and embedded content set sizes so the layout does not shift.
• If the server itself is slow, move to better hosting. No amount of tuning fixes a slow server.

When it makes sense to rebuild

Sometimes the honest answer is that the site sits on a theme or builder that will never be fast. If you have compressed every image, removed every extra plugin and the mobile results are still poor, a clean rebuild can cost less than another year of patching.

If someone else manages your site, ask them for the mobile PageSpeed Insights results for your five most important pages, what is causing the worst problems and what they plan to change. A good web person can answer in plain language. If the answer is that speed does not matter for a business like yours, get a second opinion.

Whatever you decide, recheck speed after any change that adds something to the site: a new widget, a new tracking tag, the homepage video someone suggested. Speed is usually lost a little at a time, one harmless-looking addition after another, and nobody notices until the calls slow down.

Northward builds its sites phones first, and its Hosting & Management plan covers hosting, backups, software updates and uptime monitoring after launch.