Does site speed affect SEO and AI answers?

It does, as one signal among many. Google says Core Web Vitals "are used by our ranking systems" and recommends site owners "achieve good Core Web Vitals for success with Search." It also says good scores don't guarantee top rankings, and that relevance wins: Google shows the most relevant page "even if the page experience is sub-par."

Google's page experience documentation, updated September 22, 2026, makes three points worth knowing:

• There is no speed switch. "There is no single signal." Speed sits inside a wider idea Google calls page experience, and Google adds that "there's more to great page experience than Core Web Vitals scores alone."
• Good scores don't win on their own. A good page experience "doesn't guarantee that your pages will rank at the top of Google Search results."
• It's mostly judged page by page. "Our core ranking systems generally evaluate content on a page-specific basis," though Google says it has "some site-wide assessments."

For a contractor, that means a slow service page that answers the homeowner's question can still outrank a fast page that doesn't. Speed work pays off when your pages are already the right answer and the experience is holding them back.

Not directly. Google says a page needs to be "indexed and eligible to be shown in Google Search with a snippet" to appear as a link in AI Overviews or AI Mode, and that "there are no additional technical requirements." Speed matters there only as it matters in regular search: as part of page experience.

Google's guidance on AI features lists the basics that "continue to be worthwhile," and page experience is one of them: "Providing a great page experience for users." Its guide to generative AI features in Search goes one step further and says a good page experience includes "ensuring your site displays well across all devices, reducing latency."

Read together, Google is saying the same thing for AI features as for search: be indexable, be useful, and don't make visitors wait. There's no separate AI speed score to chase. Our guide to showing up in Google AI Overviews covers what does decide which pages get linked.

OpenAI hasn't said it does. Its crawler documentation doesn't mention page speed or load time. What it says decides eligibility is access: "Sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers," though they "can still appear as navigational links." Letting that crawler in matters far more than shaving a second.

Some marketing blogs claim speed decides whether AI tools cite you. The figures we found behind those claims were secondhand or couldn't be traced to a published study, so we don't repeat them. One point does hold up: a crawler can't use a page it can't fetch. That's a reachability problem, covered below, not a few points on a speed score.

What ChatGPT checks before it names a contractor is mostly other sources about you: your website, BBB, licensing records and review sites. Our guide to showing up in ChatGPT answers explains which ones and how to fix them, and our AI crawler definition explains the settings.

Nothing you should act on, and we'd rather say so than stretch it. Our contractor website study recorded a lab performance score for the sites we crawled in October 2026, but we haven't published a speed comparison, so this guide doesn't make one. What the study does publish is about pages and contact paths.

What the published study does cover is how homeowners get in touch, which our contractor website handbook turns into a checklist.

If we publish a speed comparison later, it will sit on the study page with its method: one collection window, a lab score rather than real-visitor data, and an association, not a cause. Until then, the honest answer rests on what Google and OpenAI say.

Core Web Vitals are Google's three measures of how a page feels to a real visitor: how fast the main content appears (LCP), how quickly the page responds to a tap (INP) and how much the layout jumps (CLS). Google counts a page as good when 75% of real visits meet all three targets, on phones and desktops separately.

Source: Search Console Help, Core Web Vitals report; web.dev, Web Vitals and Largest Contentful Paint. Read November 1, 2026.

The 75% rule comes from web.dev, which says to measure "the 75th percentile of page loads, segmented across mobile and desktop devices." On a contractor site, the phone numbers usually matter most, because that's where most homeowners in a hurry will be.

Because they measure different things. The 0 to 100 score in PageSpeed Insights and Lighthouse comes from one simulated test load, a lab test. Google's Core Web Vitals report in Search Console uses "real world usage data (sometimes called field data)" from Chrome users. So a page can score low in the lab test and still pass on field data.

The lab score is still useful for finding what's slow, as long as you know what it is:

• It's a blend. Lighthouse says its score "is a weighted average of the metric scores." In the current version, Total Blocking Time counts for 30%, LCP and CLS for 25% each, and two loading measures for 10% each.
• It moves between runs. Lighthouse notes that "a lot of the variability in your overall Performance score and metric values is not due to Lighthouse." Ads, network and device all change it. Run it several times before you worry.
• The bands: 90 to 100 is good, 50 to 89 needs improvement and 0 to 49 is poor.

Field data has its own catch for small businesses. Search Console says a group of pages needs "a minimum amount of data to be shown in the report," so a contractor site with modest traffic may show no Core Web Vitals data at all. In that case, use the lab test to find problems and judge fixes by how the site feels on your own phone.

Rarely, for a contractor site. Problems start when the server is so slow or unreliable that requests fail, or when a firewall or setting blocks crawlers outright. Google says that when a site slows down or returns errors, "the limit goes down and Google crawls less." For a site of a few dozen pages, that is seldom the deciding issue.

Google's crawl budget guide is written for "large sites (1 million+ unique pages)" and "medium or larger sites (10,000+ unique pages) with very rapidly changing content (daily)." A typical home-service site is nowhere near that. The checks that matter more for a small site:

• Is any crawler blocked? Check robots.txt and any security or CDN setting that blocks bots. Google's AI features guidance lists "ensuring that crawling is allowed in robots.txt, and by any CDN or hosting infrastructure" among the basics.
• Does the server time out or return errors? Search Console's URL Inspection tool shows whether Google could fetch a page.
• Is the content in the page text? Google lists "making sure that important content is available in textual form." Services, towns and your license shouldn't live only in images.

Our technical SEO checklist covers these checks in order.

Start with the pages that bring calls, on a phone: the homepage and your main service pages. Fix what makes the main content late, often oversized photos, then anything that makes the page jump or stall on a tap, such as late-loading chat widgets, pop-ups and stacked tracking scripts. Then check the call button and form still work.

A practical order:

1. Look at the field data first. Open the Core Web Vitals report in Search Console. If your pages are already "good," speed isn't your bottleneck.
2. Shrink and size your photos. In our experience, job photos straight off a phone are often the heaviest thing on a contractor page. Resize them and set their dimensions so the layout doesn't jump.
3. Cut what you don't use. Old plugins, sliders, a second chat tool, scripts from past ad campaigns.
4. Load the extras after the content. Review widgets, maps and chat can load after the main content without hurting anyone.
5. Check hosting. A slow server slows every page. Ask your host about caching and a CDN.
6. Test the call path. After every speed change, tap the call button and send a test form from a phone.

If the site is built on an old theme where every fix is a patch, it may be cheaper to rebuild than to keep tuning. Our website redesign page explains how to decide between fixing, redesigning and rebuilding, and the contractor website handbook puts speed in context with everything else a site needs.

It's worth it when real visitors are waiting: your field data is poor, or the site is visibly slow on a phone. It's rarely worth it to chase a lab score from 70 to 95, or as a way to get named by AI tools. Ask which pages will be fixed and how the change will show.

A fair speed quote names the pages, the problems found and how the result will be measured. Be careful with any pitch that ties a speed score to rankings or AI recommendations. Google says good page experience "doesn't guarantee" top rankings, and no platform has published a speed rule for AI answers.

At Mindflow, we test loading on phones before every website build goes live. If your site loads well but calls are low, look at the call path instead; that's what our conversion work on existing sites covers. Keeping a site fast after launch is part of normal upkeep, which our website maintenance cost guide explains.

Is page speed a Google ranking factor? Yes, in a limited way. Google says Core Web Vitals "are used by our ranking systems," but there is "no single signal," and Google shows the most relevant page even when its page experience is weaker. A fast page that doesn't answer the search won't outrank a slower one that does.

Will a faster site get me into ChatGPT answers? Not by itself. OpenAI's crawler documentation doesn't mention speed. What it does say is that sites that block its search crawler, OAI-SearchBot, won't be shown in ChatGPT search answers, except as navigational links. Accurate, consistent information about your business on your site and the sites ChatGPT checks matters far more.

What's a good PageSpeed score for a contractor site? Lighthouse calls 90 to 100 good, but the score is a single lab test that changes from run to run. Google's own measure is field data from real Chrome visitors: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, at the 75th percentile.

Why does Search Console show no Core Web Vitals data for my site? Search Console only shows a group of pages when there's "a minimum amount of data" from real visitors, to protect their privacy. Many small business sites don't meet it. Use PageSpeed Insights' lab test to find problems, and check the site on your own phone.

Does hosting affect speed? Yes. A slow or overloaded server delays every page before anything else can load, and Google crawls less when a server slows down or errors. Ask your host about caching and a CDN before paying for other speed work. At Mindflow, we help clients set up hosting and a CDN in their own name when we build a site.

All sources read November 1, 2026.

• Google Search Central, Understanding page experience in Google Search results (updated September 22, 2026)
• Google Search Central, Understanding Core Web Vitals and Google search results (updated December 10, 2025)
• Search Console Help, Core Web Vitals report
• web.dev, Web Vitals and Largest Contentful Paint
• Chrome for Developers, Lighthouse performance scoring
• Google Search Central, AI features and your website (updated December 10, 2025)
• Google Search Central, Google's guide to optimizing for generative AI features on Google Search (updated July 10, 2026)
• Google Crawling docs, Crawl budget management for large sites (updated July 22, 2026)
• OpenAI, Overview of OpenAI crawlers
• Mindflow, Contractor website study, sites crawled October 2026

More guides on ChatGPT and Google's AI features are in AI search. Want to know what Google's AI and ChatGPT say about your business today? Book a free AI Visibility Review.