Page speed and Core Web Vitals explained
Page speed describes how quickly a page loads and becomes usable. Core Web Vitals measure real user experience through Largest Contentful Paint (LCP, loading), Interaction to Next Paint (INP, responsiveness), and Cumulative Layout Shift (CLS, visual stability). Google's “good” targets are LCP within 2.5 seconds, INP below 200 milliseconds, and CLS below 0.1. These are field-experience metrics; a single simulated test is diagnostic rather than a substitute for user data. Google's Core Web Vitals guide and web.dev's measurement guidance.
Impact details
Impact: Medium, mainly indirect. Google's ranking systems use Core Web Vitals, and Google recommends good page experience for AI Overviews and AI Mode. Yet relevant content can rank despite weaker experience, and good scores do not guarantee a top result. If requests time out, that is a separate crawl-health problem; Core Web Vitals are not an AI citation formula. This rating reflects a possible Search and user-experience pathway, not measured AI recommendation uplift. Google's page-experience guidance, AI feature guidance, and Core Web Vitals guide.
Proof & consensus details
Proof: Medium. Consensus: Mixed. Google confirms Core Web Vitals participate in Search ranking. Its AI guidance calls for good page experience, but reports no isolated effect of LCP, INP, or CLS on AI citations. Other AI answer platforms are less specific about these metrics. Fast user experience and reliable crawler access are distinct: a page can pass a speed test while returning crawler errors, or fail a metric while indexed. Google's page-experience guidance and AI feature requirements.
Recommendation
Prioritize genuine user problems: slow main-content display, delayed responses to taps or clicks, and shifting layouts. Improve images, critical resources, script work, and reserved space for media as appropriate. Compare mobile and desktop field data before choosing fixes; focus first on important page groups with enough real-user data. Do not chase a perfect score at the expense of helpful content. If the page sometimes times out or returns server errors, investigate that as technical reliability rather than treating it as a Core Web Vitals failure.
AI platforms
For Google AI Overviews and AI Mode, Google explicitly includes page experience in its general AI-feature best practices, while Core Web Vitals are documented Search ranking inputs. This does not establish an AI-only threshold or guaranteed citation benefit. Google's AI guidance and page-experience guidance.
For Bing/Copilot and ChatGPT, the reviewed primary guidance does not provide a comparable LCP/INP/CLS-to-citation rule. Bing emphasizes efficient crawling and rendering, which should not be equated with a Core Web Vitals score. Bing Webmaster Guidelines and OpenAI's publisher FAQ.
Audit instructions
- Test representative pages in PageSpeed Insights on mobile and desktop. Record available field data and lab results, noting when real-user data is insufficient.
- Identify slow main content, unresponsive controls, or shifting elements. Use Search Console or real-user monitoring, where available, to find other affected pages.
- Fix the main issues and retest the same pages and metrics. Review indexing and AI citations separately; a better speed score is not proof of an AI visibility gain.