Short answer: Paste your homepage and your busiest service page into Google's free PageSpeed Insights, switch to the mobile tab, and look first at the real-user field data: a page passes Core Web Vitals when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less. If it fails, the usual culprits are oversized images, too many third-party scripts and slow hosting, and the fix starts with whatever loads first on a phone.
Speed costs you calls before it costs you rankings
Most conversations about website speed jump straight to Google rankings. Speed does matter there: Google uses page experience signals, including Core Web Vitals, as part of how it ranks pages. But it is one signal among many, and a slow page with the best answer can still rank.
The more direct cost is people. Someone searching for a plumber, a med spa or a painter on their phone taps your result, waits, sees a blank screen or a button that jumps away as they reach for it, and goes back to the results. You never see that visit as a lost call. It just never becomes one. That is why speed belongs in any honest look at why a site isn't producing leads, and why we check it before we spend a dollar on ads pointing at a page.
The good news is that you can check where you stand in about five minutes, for free, with Google's own tool.
The five-minute check with PageSpeed Insights
PageSpeed Insights is Google's free speed report. You don't need an account or any access to your website to use it.
- Go to pagespeed.web.dev and paste in your homepage address.
- Make sure the Mobile tab is selected. Most local searches happen on phones, and mobile scores are almost always worse than desktop.
- Read the top section first, the one that reports what your real users are experiencing. Note whether it says the Core Web Vitals assessment passed or failed, and the three numbers under it.
- Then scroll to the lab section with the 0 to 100 performance score and its list of diagnostics.
- Repeat for the page that matters most for leads: your top service page, or whatever page your ads send people to.
Write down the three Core Web Vitals numbers for each page. Those are your baseline, and they are what you will compare against after any fix.
Field data and lab data measure different things
The two halves of the PageSpeed Insights report confuse almost everyone, and mixing them up leads to fixing the wrong thing.
Field data: what real visitors experienced
The top section comes from the Chrome User Experience Report, which collects anonymous timing data from real Chrome users who visited your page over the previous 28 days. Google judges each metric at the 75th percentile, which means the page has to be fast for most visits, not just on a good day. This is the data Google's Core Web Vitals assessment is based on. You can toggle between this exact URL and your whole site (the origin).
If your site doesn't get enough Chrome traffic, this section will say there is no data. That's common for small local businesses, and it doesn't mean anything is broken. Search Console's Core Web Vitals report groups similar pages together and sometimes has data when a single URL doesn't.
Lab data: one simulated visit
The lower section comes from Lighthouse, which loads your page once in a controlled test that simulates a mid-range phone on a slower mobile connection. It produces the 0 to 100 performance score and a list of specific problems. Lab data is useful for diagnosing why a page is slow and for testing a fix right away, because you don't have to wait weeks for real-user data to update.
Two things to keep in mind. The performance score is a lab summary, not the pass or fail result Google uses, so don't chase a perfect 100. And it will move a few points between runs even if nothing changed.
What the three Core Web Vitals numbers mean
Google's Core Web Vitals are three measurements of how a page feels to use. These are Google's published thresholds for a "good" result:
- Largest Contentful Paint (LCP): 2.5 seconds or less. How long it takes for the biggest thing on the screen, usually the hero image or headline, to appear. This is the "is anything happening" moment.
- Interaction to Next Paint (INP): 200 milliseconds or less. How quickly the page responds after someone taps, clicks or types, measured across the whole visit. INP replaced First Input Delay as a Core Web Vital in March 2024, so older guides that mention FID are out of date.
- Cumulative Layout Shift (CLS): 0.1 or less. How much the layout jumps around while loading. This is the button that moves just as your thumb lands on it, which is how a visitor ends up tapping an ad or a pop-up instead of your phone number.
A page passes when all three are in the good range at the 75th percentile. Lab tests can't measure INP directly because nobody is tapping anything, so the lab section shows Total Blocking Time as a stand-in. A high Total Blocking Time usually points to the same problem: too much JavaScript running at once.
The usual reasons a small business site is slow
After looking at a lot of local business websites, the causes repeat. PageSpeed Insights will name most of them in its diagnostics, in more technical words.
- A huge hero image or background video. A photo straight off a camera or phone, uploaded at full size, is often the single biggest thing slowing LCP.
- Sliders and carousels that load five large images when the visitor sees one.
- Third-party widgets. Chat bubbles, review badges, social feeds, booking embeds, heat-mapping tools and old tracking pixels each add scripts. Many sites carry tags for tools nobody has logged into in years.
- Images and embeds without set dimensions, so the page reflows when they arrive and CLS climbs.
- Pop-ups and banners that push content down after the page has already appeared.
- Heavy web fonts, several weights of several families, all loading before text shows.
- Slow hosting or a bloated theme, which delays everything before the first byte arrives.
What to fix first
Work in the order a phone loads the page. The first screen is what decides whether someone stays, so it gets fixed before anything below it.
- Find the LCP element. PageSpeed Insights names it in the diagnostics. If it's an image, resize it to the size it actually displays, compress it, serve a modern format such as WebP or AVIF, and make sure it is not lazy-loaded.
- Remove third-party scripts you don't use. Then delay the ones you do use, such as chat widgets, until after the page has loaded or the visitor interacts.
- Give every image, video and embed fixed dimensions so space is reserved before it loads.
- Lazy-load images and videos below the first screen. For embedded YouTube or Vimeo videos, show a thumbnail that loads the player only when tapped.
- Cut fonts down to the weights you actually use.
- Run PageSpeed Insights again and compare the lab numbers to your baseline. Field data will catch up over the following weeks.
Then do the test no tool can do for you. Pick up your own phone, turn off Wi-Fi, search for your business, open the page and tap the phone number. If anything about that feels slow or fiddly, a customer feels it too. Make sure that tap is also counted as a lead in your analytics; our guide to tracking calls and form fills in GA4 walks through it.
When the fix is a rebuild, not a tune-up
Many speed problems are fixable in place. Some aren't. If the platform loads the same heavy code on every page no matter what you remove, or the theme was built around a full-screen slider and a dozen plugins, you can spend a lot of effort to move from poor to merely slow. That's the point where a rebuild costs less than continued patching. We explain that tradeoff in custom-built vs. website builder.
Speed matters even more on pages that receive paid traffic, because you pay for every click whether the page loads or not. Our guide on landing pages for Google Ads covers what those pages need beyond speed.
Every site we build is hand-coded to ship only what each page needs, and tested on real phones before launch. If your PageSpeed numbers came back red and you want to know whether to fix or rebuild, see how we handle brand and web projects or send us the URL.
Frequently asked questions
What is a good PageSpeed Insights score?
Focus on the Core Web Vitals assessment in the field data rather than the 0 to 100 lab score. A page passes when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less, measured at the 75th percentile of real visits.
Why does PageSpeed Insights say there is no field data for my site?
Field data comes from real Chrome users, and Google only reports it when a page or site has enough visits. Many small local business sites fall below that threshold. Use the lab data to diagnose problems, and check the Core Web Vitals report in Google Search Console, which groups similar pages.
Does website speed affect Google rankings?
Yes, as one of many signals. Core Web Vitals are part of Google's page experience signals, but relevance and quality matter more. The larger cost of a slow site is usually visitors who leave before they call, book or fill out a form.
What replaced First Input Delay in Core Web Vitals?
Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital in March 2024. INP measures how quickly a page responds to taps, clicks and typing across the whole visit, and the good threshold is 200 milliseconds or less.