“Does a slow website hurt me on Google?” Some, and Google says so in writing. But speed also matters to the homeowner standing in her yard with a phone, who can tap back to the search results at any moment while your home page loads. This article puts Google’s speed measures, the Core Web Vitals, into plain words, shows how to test your own site in ten minutes, and goes through what usually slows a contractor’s site down.
What Google actually says about speed and ranking
Google Search Central calls Core Web Vitals “a set of metrics that measure real-world user experience for loading performance, interactivity, and visual stability of the page,” and its page experience guide says plainly: “Core Web Vitals are used by our ranking systems.” The same guide sets the limits. “There is no single signal,” and “Google Search always seeks to show the most relevant content, even if the page experience is sub-par.” It adds that good results in Search Console’s report or third-party tools do not guarantee your pages will rank at the top.
So treat speed as one signal among many on Google, and as part of every visitor’s first impression. A fast page that does not answer the homeowner’s question still loses her; the pages that do answer it are in The Website Pages a Contractor Needs. Make those pages fast and you have both.
The three Core Web Vitals in plain words
| Measure | In plain words | Good | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the biggest thing on the screen, usually your main photo or headline, has appeared | 2.5 seconds or less | Over 4 seconds |
| Interaction to Next Paint (INP) | How long the page takes to react when someone taps, clicks or types | 200 milliseconds or less | Over 500 milliseconds |
| Cumulative Layout Shift (CLS) | How much the page jumps around while it loads | 0.1 or less | Over 0.25 |
The “good” limits are from web.dev, Google’s site for web developers, and the “poor” ones from Search Console’s Core Web Vitals report; anything between is “needs improvement.” Two details matter. A page should meet the limits “at the 75th percentile of page loads, segmented across mobile and desktop devices,” so three visits in four must be good, and phones are judged on their own. And INP counts only clicks, taps and key presses; web.dev notes that hovering, zooming and scrolling are not observed. INP is the successor to an older measure, First Input Delay, so a guide that still talks about FID is out of date.
Test your site in ten minutes
Open PageSpeed Insights, paste in your home page, and look at the mobile result first. It shows two kinds of numbers, and they answer different questions:
Then open the Core Web Vitals report in Search Console. It uses the same real-user data, groups pages that behave alike, and gives each group the status of its worst measure. A small or new site may show no data there. After you fix something, the report’s validation runs a 28-day monitoring session to confirm the fix held.
Test your top service page too, not just the home page; a homeowner who searches for one job may land there first.
The usual culprits on contractor sites
1. The giant hero photo
web.dev’s guide to LCP measures the time until “the largest image or text block” in view is rendered. On a contractor site that is often a full-width photo of a finished job, uploaded straight from a phone. The guide’s fixes: “Serve the optimal image size,” “Use modern image formats,” and “Compress images.” Resize the photo to the largest size it is actually shown at before you upload it. And one rule to check: “Never lazy-load your LCP image, as that will always lead to unnecessary resource load delay.” Lazy loading is for photos further down the page, not the first one.
2. The slider
web.dev’s carousel guide is direct: “Large, above-the-fold carousels often contain the page’s LCP element, and therefore can have a significant impact on LCP,” and many use animations that add layout shift. It calls loading slides with JavaScript “probably the single biggest performance mistake to avoid.” It also doubts the slides get seen: “it’s unlikely that most users will engage with all carousel content,” and users “will ignore carousels that autoplay.” One strong photo and one clear sentence do the slider’s job faster.
3. The chat widget and other embeds
Chat bubbles, review badges, embedded maps and videos all load code from someone else’s server. web.dev’s embed guide warns that “Many popular embeds include over 100 KB of JavaScript, sometimes even going up to 2 MB,” and that they can block rendering, compete for bandwidth and cause layout shifts. Its guide to INP explains the cost to tapping: evaluating scripts during page load can create long tasks on the main thread that delay the browser from responding to the visitor.
The fix is a facade. Chrome’s Lighthouse documentation describes it as “a static element that looks similar to the embedded third-party, but is not functional and therefore much less taxing on the page load,” and lists chat widgets (Intercom, Drift, Help Scout and Facebook Messenger) and video players among the embeds worth deferring. The real widget loads when the visitor clicks. For iframes such as videos and maps, web.dev recommends the loading="lazy" attribute; for a YouTube video it says that can save approximately 500 KB on the first load.
4. The page that jumps
web.dev lists the most common causes of poor CLS as images without dimensions; ads, embeds and iframes without dimensions; content injected after the page starts loading; and web fonts. The first one has a one-line fix: “Always include width and height size attributes on your images and video elements,” or reserve the space with CSS. A promo banner that slides in above your headline, or a review badge that pops in late, pushes everything down just as a visitor reaches for the button.
A one-hour cleanup
- Run PageSpeed Insights on mobile for the home page and your busiest service page. Write down LCP, INP and CLS, or the lab score if there is no field data.
- Find the LCP element the report names. If it is a photo, resize and compress it, and make sure it is not lazy-loaded.
- Replace the slider with one static photo and headline.
- Put the chat widget, maps and videos behind a click, or lazy-load them.
- Give every image and embed a width and height.
- Test again, and check Search Console’s report once a month.
If your site is built on a website builder you cannot change much, the same checklist tells you what to ask its support team for. And while you are on the home page, ask the question speed cannot answer: does it tell a homeowner roughly what the job costs? That is the subject of Your Website Is a Brochure.