Most business owners believe their website is fine. They visit it on their laptop, everything loads quickly, and nothing seems broken. They do not know how it performs on a three-year-old Android on a 4G connection in a parking lot, which is the device and context a significant share of their customers are using when they search for services.
Core Web Vitals measure exactly that experience. Because most local business websites perform poorly on mobile, the PageSpeed data in an F! Insights scan is one of the most consistently engaging elements in the report. It names a specific, measurable problem the business owner did not know they had.
In This Article
What Core Web Vitals Actually Measure
| Metric | What It Measures | Good Threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How long it takes for the main content to load | Under 2.5 seconds |
| FID / INP (Interaction to Next Paint) | How quickly the page responds to user input | Under 200 milliseconds |
| CLS (Cumulative Layout Shift) | How much the page layout shifts as it loads | Under 0.1 |
| FCP (First Contentful Paint) | How quickly the first content element appears | Under 1.8 seconds |
| TBT (Total Blocking Time) | How long the main thread is blocked by scripts | Under 200 milliseconds |
Google uses these metrics as ranking signals for both organic search and local search. A business with a slow mobile site is not just losing conversions from visitors who get frustrated and leave. They are also getting a weaker ranking signal from Google.
Why Most Local Business Websites Fail This Test
Local business websites are typically built once by a web designer who optimized for desktop appearance and never revisited for mobile performance. Common problems: uncompressed images 5 to 10 times larger than they need to be, render-blocking JavaScript from plugins and widgets, no browser caching configuration, shared hosting that responds slowly under load, and theme code not written with performance in mind.
To learn more about the full client workflow behind this, visit Client Content Calendar With Funnel Mapping. How to Read a Geogrid and Build a Local SEO Action Plan and Run a Keyword Content Sprint for a Local SEO Client cover adjacent steps in detail.
PageSpeed as a Lead Generation Angle
PageSpeed data converts an abstract claim (“your website could be better”) into a specific, measured number the prospect can verify themselves. A mobile PageSpeed score of 23 is not a matter of opinion. It is a number from Google’s own tool. That objectivity removes the skepticism that kills most cold outreach.
How F! Insights Uses PageSpeed Data
Every F! Insights scan includes a PageSpeed audit of the business’s linked website, run via the Google PageSpeed Insights API. The report shows the mobile score, the desktop score, and the individual Core Web Vitals metrics with a plain-language AI interpretation of what each metric means for the business.
A business with a PageSpeed score below 50 on mobile gets a flagged warning in the report alongside the specific metrics dragging the score down. For context on what these scores mean relative to competitors in the same category, see Local SEO Benchmarks: What Good Actually Looks Like.
Using PageSpeed in Your Outreach
When F! Insights bulk scanning flags a prospect’s PageSpeed score as poor, that number becomes the opening line of your outreach. “Your mobile site scored 23 on Google’s PageSpeed tool. The average in your category is closer to 45. That gap is affecting both your search ranking and the experience of every visitor who finds you on their phone.” For how to structure the full outreach sequence around scan data, see Cold Email Local Businesses: The Data-First Approach.
What Fixing It Actually Involves
- Image compression and format conversion to WebP: often the single highest-impact change for LCP and overall load time
- Eliminating render-blocking JavaScript: significant improvement to FCP and TBT for sites with heavy plugin loads
- Enabling browser caching: reduces load time for returning visitors
- Upgrading hosting plan: particularly relevant for shared hosting where server response time is slow
- Deferring non-critical scripts: reduces TBT on sites with analytics, chat widgets, and third-party embeds
Most of these improvements require a developer, but they are not expensive or complex projects. A technically competent developer can address the most impactful issues in a few hours. The before-and-after PageSpeed scores make the improvement highly visible and easy to demonstrate to the client.