Google made it official: how fast your site loads is now part of how it ranks. In 2026, with AI Overviews covering a quarter of results pages, site performance also determines whether an AI crawler can read your content at all.
What Core Web Vitals actually measure
Google confirmed Core Web Vitals as a ranking signal in May 2021. Three metrics matter: LCP measures how fast the main content loads, INP measures how quickly the page responds to interaction, and CLS measures how stable the layout is during load.
| Metric | What it measures | Target |
|---|---|---|
| LCP — Largest Contentful Paint | Main content load speed | under 2.5 s |
| INP — Interaction to Next Paint | Page responsiveness to interaction | under 200 ms |
| CLS — Cumulative Layout Shift | Layout stability during load | under 0.1 |
Why performance is also a GEO signal
AI crawlers — including Googlebot, which feeds AI Overviews — time out on slow servers and often skip pages that do not render fast enough. A site that ranks on page one can still be invisible to the AI layer if the performance foundations are wrong.
- Server-rendered HTML: many AI crawlers do not execute JavaScript. Static (SSG) or server-rendered (SSR) pages are readable; client-only SPA content may not be.
- Fast first byte: a TTFB under 200 ms signals a reliable server and fits within crawler time budgets.
- No render-blocking: fonts and scripts that delay the first paint also delay what the crawler indexes.
What 90+ Lighthouse actually requires
A sustained 90+ Lighthouse score in production means the build decisions are structurally sound — it is a proxy that tracks closely with real-world Core Web Vitals field data.
- Remove heavy animation libraries (motion/framer, GSAP) from the critical path — they add 80–100 KB to the JavaScript bundle.
- Preload only the fonts visible above the fold; use font-display:optional for the rest.
- Prefer static generation for content pages; keep server-side rendering for dynamic routes only.
- Set explicit width and height on all images to eliminate layout shift.
- Load third-party scripts (analytics, chat widgets) asynchronously, after the main content paints.
The proof on our own sites
ZAOURI's site (zaouri.com) reaches 90+ Lighthouse performance on mobile in production — not in a lab simulation. The same build discipline powers Marrakech Private (100 Lighthouse SEO) and Marrakech Nightlife (100 SEO, 100 Best Practices). These scores are measured live, not assumed.
FAQ
- Does the Lighthouse score directly affect my Google ranking?
- Not directly. Google uses real-world Core Web Vitals data from the Chrome UX Report (CrUX), not lab scores. But sustained 90+ in Lighthouse tracks closely with good field CWV data, because the same decisions drive both.
- Can an existing slow site be fixed?
- Yes. Retrofitting performance typically takes 4–8 weeks depending on the stack and scope. Sites built on modern frameworks (Next.js, Nuxt) are faster to tune than legacy monoliths.
- Does AI search care about speed separately from Google?
- Perplexity's crawler prioritizes clean, server-rendered HTML. Googlebot uses the same crawl budget logic for AI Overviews as for organic indexing. Speed and crawlability are the same problem.