The number that matters isn't the one you think
Most business owners test their site by opening it on their own phone, on their own WiFi, at their own desk. It loads fine. Case closed.
But the person deciding whether to call you is standing in a parkade off 104 Street with one bar of LTE, looking for a plumber while water spreads across their kitchen floor. That's the load you should care about. Not your office fibre connection.
Google measures this too, and it feeds into where you rank. The metrics are called Core Web Vitals, and Google gives them scary technical names. Here's what they actually mean in plain terms.
The three numbers, decoded
LCP (Largest Contentful Paint) is how long until the biggest thing on the screen shows up. Usually that's your hero image or a headline. If someone taps your Google listing and stares at a white screen for four seconds, LCP is your problem. Google wants this under 2.5 seconds. Between 2.5 and 4 is shaky. Over 4 is failing.
INP (Interaction to Next Paint) measures what happens after they tap something. They hit "Request a Quote" and nothing moves for half a second. Did it register? They tap again. Now it's fired twice. INP replaced the old FID metric in 2024, and it's stricter because it watches every interaction, not just the first. You want under 200 milliseconds. Over 500 feels broken.
CLS (Cumulative Layout Shift) is the annoying one. The page loads, they go to tap your phone number, and at that exact moment an image finishes loading above it and shoves everything down. Now they've tapped an ad or the wrong link. That jump is layout shift. Google scores it from 0 up, and you want under 0.1. This one costs you real calls because people give up when the page won't hold still.
Test it the way your customers experience it
Go to PageSpeed Insights, paste in your URL, and look at the mobile tab. Not desktop. Mobile.
There are two sections and they mean different things. The top part, "Discover what your real users are experiencing," is field data. That's actual visitors on actual phones over the past 28 days. That's the truth. The bottom part is a lab test on a simulated slow connection, useful for finding the cause but not a report card.
If the field data section is missing or greyed out, your site doesn't get enough traffic for Google to collect it. That's common for a roofing company or a dental office in a smaller Edmonton neighbourhood. In that case the lab score is all you've got, so treat it seriously.
Why slow costs you the job specifically
A local search has almost no patience built into it. When someone searches "furnace repair Sherwood Park" at 6 a.m. because their house is cold, they are going to tap the first two or three results and go with whichever one loads and shows a phone number. If yours takes five seconds, they're already on your competitor's site.
This is different from someone browsing a national brand they already trust. For that customer, waiting is a chore they'll tolerate. For your customer, the next option is one tap away and just as qualified. Speed isn't a nicety here. It decides who gets the call.
What actually moves the number
Most slow local sites are slow for the same handful of reasons. In rough order of impact:
- •Giant images. A photographer uploads a 6000-pixel photo of a finished basement and the browser downloads all of it, then shrinks it to fit a phone. That's the single most common cause of a bad LCP. Resize images before uploading and save them as WebP. This one fix often cuts load time in half.
- •A page builder loading everything. Elementor, Divi, and the heavier WordPress builders pull in scripts and fonts your homepage doesn't use. Every one is a small delay that adds up. Sometimes the honest answer is a lighter theme.
- •Third-party scripts. A chat widget, a booking embed, three tracking pixels, a review carousel. Each one phones home to someone else's server before your page can settle. Audit them and drop the ones nobody looks at.
- •No caching. Without it, your server rebuilds the whole page from scratch for every single visitor. A caching plugin serves a ready-made copy instead. On WordPress this is a fifteen-minute setup that helps immediately.
- •Set dimensions on images. Telling the browser how tall each image will be, before it loads, stops the page from jumping. That's your CLS fixed, and it's mostly free.
You can do most of this yourself in an afternoon if you're comfortable in your site's admin. The images alone are worth the trouble.
Run the mobile test right now, before you close this tab. If your LCP is over four seconds, that's the thing to fix this week. When you want a second set of eyes on what's dragging it down, start here.