How does page speed affect AI search citation?
Page speed's relationship to AI citation is primarily about crawlability, not about impressing an algorithm with fast load times. AI web crawlers visit your site on a schedule, download your page content, and process it. A slow site — particularly one with unoptimized images, render-blocking scripts, or slow server response times — returns incomplete or timed-out content to crawlers. Content they can't read, they can't cite.
The crawlability threshold
Your site doesn't need to be blazing fast to be crawlable — it needs to be fast enough. A Google PageSpeed Insights mobile score above 50 is a reasonable minimum for local business sites. Aim for above 60 for most. Below 50, you're likely seeing issues that affect crawler access alongside user experience. The content of your page matters more than raw speed scores — but a broken or extremely slow page is a GEO dead end.
What commonly slows local business sites
- Uncompressed images: A homepage with 8 full-resolution photos can be 15MB+ — massive for crawlers and users alike. Compress images to under 200KB each and use WebP format where possible.
- Cheap shared hosting: If your server response time is over 800ms, budget hosting is likely the culprit. Moving to a quality host (SiteGround, Cloudways, or similar) is one of the highest-impact speed improvements available.
- Too many WordPress plugins: Each plugin adds code that must load. Audit your plugins and remove any you're not actively using.
- No caching: Page caching serves a pre-built version of your page instead of building it dynamically on every visit. Free caching plugins (W3 Total Cache, WP Super Cache) fix this quickly.
- No CDN: A content delivery network serves your static assets from servers geographically close to the visitor. Cloudflare's free tier handles this well.
What speed score should you target for GEO?
For GEO purposes, the specific number matters less than ensuring:
- Your pages fully load without errors
- Your core content (text, headings, schema) appears in the HTML source and not only after JavaScript execution
- Your server responds within 2 seconds
- You have no critical errors in Google Search Console related to crawl issues
The JavaScript rendering issue
If your site uses JavaScript to load your main content (common with React, Vue, or similar frameworks), some crawlers may not execute JavaScript and may receive an essentially empty page. For local business sites, this is rarely an issue — most are built on WordPress or static HTML. But if your site's main content is loaded via JavaScript, confirm AI crawlers can see it by checking your page's "View Source" (not Inspect) — if your content isn't visible there, crawlers won't see it either.
Key Takeaways
- Page speed affects AI citation through crawlability — crawlers that time out or get incomplete content can't cite it
- A PageSpeed Insights mobile score above 50 is the minimum; above 60 is the target for local business sites
- The most common speed killers: uncompressed images, cheap hosting, too many WordPress plugins, and no caching
- Ensure your core content appears in HTML source — JavaScript-rendered content may be invisible to some AI crawlers
- Check each service page's speed individually — not just your homepage