Your PageSpeed Insights score is green, your Core Web Vitals pass, and you still cannot tell whether any of that has anything to do with getting cited in ChatGPT, Perplexity, or a Google AI Overview. Most SEO checklists lump page speed and AI visibility into the same pass or fail bucket without explaining whether the two are actually connected. AskEO is an AI-powered audit tool that scores a site's SEO and AEO health in about 30 seconds, pulling Core Web Vitals from Google PageSpeed Insights alongside schema markup, headings, and AI crawler access. Core Web Vitals are Google's three page-experience metrics, Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP), that grade how fast a page loads, how stable it looks while loading, and how quickly it responds to input.
What Are Core Web Vitals, and Why Do They Show Up in an AEO Audit?
Core Web Vitals measure real user experience, not code quality in the abstract. LCP tracks how long the biggest visible element takes to render, CLS tracks how much the layout jumps around while the page loads, and INP tracks the delay between a click or tap and the page responding on screen. Google folds these three metrics into the Page Experience signal it already uses in classic search ranking. An AEO audit checks Core Web Vitals for the same reason a home inspection checks the foundation before the roof: a page that fails on load speed and stability has a ranking problem before it has an AI-visibility problem.
Does Google Use Core Web Vitals to Decide What Goes Into an AI Overview?
Yes, indirectly. Google's AI Overviews and AI Mode draw from the same index and the same ranking systems as classic search results; there is no separate AI index with its own criteria. A page has to be crawlable, indexable, and competitive in normal search first, and Core Web Vitals are one input into that competitiveness. A page with a six-second LCP can still rank for a low-competition query, but on any query where several pages could plausibly answer the question, Google favors the one that loads fast and does not jump around, because that is a measurable proxy for a page people can actually use. If AI Overviews draw from the top organic results, a slow page has a lower chance of being in that pool to begin with.
Do ChatGPT, Perplexity, and Claude Care About Your Page Speed?
Not the way Google does. ChatGPT's GPTBot, Perplexity's PerplexityBot, and Claude's ClaudeBot fetch pages with dedicated crawlers that request the raw HTML and, in most cases, do not run a full browser-style JavaScript render. None of the public documentation from these three companies lists page speed as a ranking or citation signal. What does matter to a fetch-based crawler is whether the page responds inside a reasonable timeout and whether the content exists in the raw HTML rather than being injected client-side after render. A page that is slow because of a heavy client-side framework can end up invisible to these crawlers for a different reason than speed: the crawler never executes the script that would draw the content in, so it never sees it at all.
How to Check Your Core Web Vitals Score
Before assuming speed is or is not your problem, measure it. The process takes a few minutes:
- Open web.dev's Core Web Vitals guide and Google's PageSpeed Insights tool, then enter your page URL.
- Read the Field Data section if it is present, since it reflects real visitor sessions rather than a lab simulation.
- Compare your LCP, CLS, and INP against Google's published good thresholds: under 2.5 seconds for LCP, under 0.1 for CLS, and under 200 milliseconds for INP.
- Open the Opportunities list for the specific fix behind each score, not just the number itself.
- Re-test after every fix, since Core Web Vitals shift with each deploy rather than staying fixed once measured.
Where Speed Actually Helps and Where It Does Not
Laid out side by side, the difference between Google's ranking systems and the AI-engine crawlers is a lot clearer than most checklists make it sound.
| Engine | Uses Core Web Vitals? | What actually matters |
|---|---|---|
| Google Search and AI Overviews | Yes, as a direct ranking input | LCP, CLS, and INP thresholds; the page must first qualify in classic search |
| ChatGPT (GPTBot) | No confirmed signal | Server responds within timeout; content is present in the raw HTML |
| Perplexity (PerplexityBot) | No confirmed signal | Same as above, plus how recently the source page was updated |
| Claude (ClaudeBot) | No confirmed signal | Same fetch-based access requirements as the other two |
Running PageSpeed Insights on one page is quick. Doing it across every page you publish, then separately checking whether GPTBot, PerplexityBot, and ClaudeBot are even allowed to fetch that page, then checking your structured data on top of that, is where most people stop measuring altogether. AskEO runs all three checks in one pass, Core Web Vitals from PageSpeed Insights, AI crawler access from your robots.txt, and structured data from your page's JSON-LD, and returns a single SEO and AEO score with the specific issues found.
See what your own homepage scores on the free and Pro plans.
"I Already Check PageSpeed Insights, Why Do I Need Another Tool?"
That is a fair objection, and PageSpeed Insights is genuinely useful for what it does. But it only measures speed. It does not check whether your robots.txt allows GPTBot and ClaudeBot, whether your FAQ content is marked up so an AI engine can lift it whole, or how your score changes from one month to the next. Running three separate tools and cross-referencing the results by hand is exactly the kind of task that gets skipped after the second month. A combined score is not a replacement for PageSpeed Insights; it is what turns three separate checks into one habit you actually keep.
Run Your Site Through an AskEO Scan
Create a free account and scan your homepage. It takes about 30 seconds, returns your SEO score, AEO score, and Core Web Vitals reading together in one report, and comes with three lifetime audits at no cost and no credit card. Start your free scan.
Frequently Asked Questions
Does page speed affect AI Overviews?
Indirectly, yes. AI Overviews draw from Google's normal search index and ranking systems, and Core Web Vitals are one input into whether a page ranks competitively enough to be pulled into that pool.
Do ChatGPT and Perplexity use Core Web Vitals?
There is no public documentation from OpenAI or Perplexity listing Core Web Vitals as a ranking or citation factor. Their crawlers care more about whether the server responds in time and whether the content is present in the raw HTML.
What are the Core Web Vitals thresholds?
Google's published good thresholds are under 2.5 seconds for Largest Contentful Paint, under 0.1 for Cumulative Layout Shift, and under 200 milliseconds for Interaction to Next Paint.
Can a fast site still fail to get cited by AI search engines?
Yes. Speed alone does not fix a blocked robots.txt, missing FAQ schema, or content that never appears in the raw HTML because it is rendered client-side. Those three issues stop AI crawlers regardless of how fast the page loads.
How often should I re-check my Core Web Vitals score?
Check it after every deploy that touches images, fonts, or third-party scripts, and at least monthly otherwise, since Core Web Vitals shift with content and code changes rather than staying fixed once measured.
Where can I read more about AEO fundamentals?
The AskEO blog covers AI crawler access, schema markup, and audit scoring in more depth than this article does.