Page Speed and AEO:
What We Changed and What We Are Testing

Gururaj Pandurangi
Gururaj PandurangiFounder, ThriveStack
Nov 1, 2026 · Updated Nov 9 · 5 min read

Page speed and AEO are linked by correlation so far: pages with a first contentful paint under 0.4 seconds averaged 6.7 ChatGPT citations, against 2.1 over 1.13 seconds. We cut /citedby LCP from 8.65s to 2.92s. Below you get the speeds that look good enough, our CLS fixes and our test plan.

ThriveStack citedbyAI Citations: Where a slow HTML response putsa page at risk of being skippedHTML response time (TTFB) against Google's thresholds. Nobody publishes a hardcutoff for AI crawlers, so treat the band below the bar as an unproven claim.Safest zoneRisk of being skipped grows as response time risesGoodNeeds workPoor: over 1.8s0s1s2s3s4s5s0.8s1.8sReported AI crawler timeout: 1 to 5s (vendor claim, undocumented)Our GA4 research page: 2.4 to 3.5s server responseNo AI companypublishes oneThresholds: web.dev. Timeout claim: vendor guidance (Discovered Labs), unverified.GA4 page: ThriveStack Lighthouse runs, Nov 1, 2026.
Figure 1: How page load speed maps to AI citation risk. Explained in section 01.
Read on

Four numbers frame this page speed and AEO test. In SE Ranking's data, pages with a first contentful paint under 0.4 seconds averaged 6.7 ChatGPT citations against 2.1 for pages over 1.13 seconds, which is only correlation (section 1). LCP on /citedby fell from 8.65s to 2.92s, our largest change (section 2). Pages over the CLS limit fell from 8 to 0 (section 3). The number that matters most for ThriveStack citedby is the last one. After the fixes, visibility rose from 9.4% to 27.6% and retrievals of our domain went from 33 to between 82 and 94 per run, but our prompt list also grew from 32 to 45. On the same 32 prompts, visibility moved from 9.4% to 12.2%, which is still inside our normal range (section 4).

3.2x
more ChatGPT citations, FCP under 0.4s vs over 1.13s (6.7 vs 2.1)
2.92s
/citedby LCP, down from 8.65s
8 to 0
pages over the 0.1 CLS limit
12.2%
visibility on our original 32 prompts after the fixes, up from 9.4% (27.6% on all 45)

A slow page gives an AI crawler a reason to move on. We fixed our own pages first and saved a citation baseline. Now we will publish what happened, good or bad.

Gururaj PandurangiGururaj Pandurangi, FounderThriveStack
ThriveStack citedby Research, Page Speed and AEO (Nov 2026)
01 · Good enough

What page load speed is good enough to get cited by AI?

No AI engine publishes a speed cutoff, so no number guarantees a citation. The public data points one way, though. In SE Ranking's study, pages with a first contentful paint under 0.4 seconds averaged 6.7 ChatGPT citations. Pages over 1.13 seconds averaged 2.1. Treat anything slower than Google's good limits as a risk.

ThriveStack citedbyAI Citations: Where a slow HTML response putsa page at risk of being skippedHTML response time (TTFB) against Google's thresholds. Nobody publishes a hardcutoff for AI crawlers, so treat the band below the bar as an unproven claim.Safest zoneRisk of being skipped grows as response time risesGoodNeeds workPoor: over 1.8s0s1s2s3s4s5s0.8s1.8sReported AI crawler timeout: 1 to 5s (vendor claim, undocumented)Our GA4 research page: 2.4 to 3.5s server responseNo AI companypublishes oneThresholds: web.dev. Timeout claim: vendor guidance (Discovered Labs), unverified.GA4 page: ThriveStack Lighthouse runs, Nov 1, 2026.
Green, amber and red are Google's limits for HTML response time. The dashed band is a vendor claim with no documented limit.
  1. HTML response time. Google calls 0.8 seconds or less good and over 1.8 seconds poor. A crawler waits on this before it reads a single word, so a slow server is the first place a page can lose.
  2. The 1 to 5 second band. Some vendors say AI crawlers give up in 1 to 5 seconds. No AI company publishes a timeout, so we show this as a claim only.
  3. Our slow page. The GA4 research page took 2.4 to 3.5 seconds to respond in our runs. That sits in the red zone, so it is the page we check next.

The best public number we found comes from SE Ranking, which studied 129,000 domains. The authors call the patterns directional. Stronger sites tend to be faster, so speed may be a sign of quality and not the cause.

ThriveStack citedbyChatGPT Citations: Faster pages averaged more,but the link is correlationAverage ChatGPT citations per page, grouped by first contentful paint (FCP).2.1FCP over 1.13s6.7FCP under 0.4sAverage ChatGPT citations per page3.2xmorecitationsAlso in the same studySpeed Index under 1.14sPerformed reliably wellSpeed Index over 2.2sA steep decline in citationsThe study gives no averages for thesetwo. All of it is correlation.Source: SE Ranking, 129,000 domains, via Search Engine Journal. Read Nov 1, 2026.
SE Ranking grouped pages by first contentful paint. Pages in the faster group averaged about three times the citations.

The same study, as Search Engine Journal reports it, found one odd result. Pages with an interaction delay (INP) of 0.8 to 1.0 seconds averaged 4.5 citations, against 1.6 for pages under 0.4 seconds. The authors suggest very simple pages may signal less depth. We would not read much into that, which is why INP has no line to draw below.

ThriveStack citedbyPage Speed Thresholds: What counts as good forfive metrics, and where our pages sitEach bar is one metric, split at Google's good and poor limits. Outlined marks show ourown live pages. Black ticks show the two SE Ranking FCP cut points.GoodNeeds workPoorZones: Google thresholds, web.devTTFBHTML response0.8s1.8sGA4 page: 2.4 to 3.5sCrawlers wait on this first. No AI study yet, our reading.FCPFirst paint1.8s3.0s0.4s1.13sSE Ranking: under 0.4s averaged 6.7 citations, over 1.13s 2.1.LCPMain content2.5s4.0s/citedby now: 2.92sNo AI citation study. Helps visitors, AI only indirectly.CLSLayout shift0.10.25Worst page now: 0.063No AI citation study. Crawlers do not see layout shift.INPTap response200ms500msOdd result in SE Ranking data, so we draw no line from it.Thresholds: web.dev. FCP citations: SE Ranking, 129,000 domains. Our pages: ThriveStackLighthouse, Oct 31 to Nov 1, 2026. Each mark is one page only.
Google's limits for five metrics, with our own live pages marked. Only FCP has a public AI citation figure.

So what is good enough? Use Google's good limits as your floor, because they are the only thresholds with a published source. Server response and the text in your HTML reach a crawler directly, so fix those first. LCP, CLS and INP mainly help your visitors. Our own pages show the gap: /citedby still sits in the amber zone for LCP at 2.92s.

  1. HTML response (TTFB): 0.8 seconds or less.
  2. First contentful paint (FCP): 1.8 seconds or less by Google's rule. SE Ranking's best-cited group was under 0.4 seconds.
  3. Largest contentful paint (LCP): 2.5 seconds or less.
  4. Cumulative layout shift (CLS): 0.1 or less.
  5. Interaction to Next Paint (INP): 200 milliseconds or less.

Try ThriveStack citedby: Check which of my pages AI can read →

02 · LCP

How did we improve largest contentful paint on our site?

We improved largest contentful paint by removing what blocked the first paint. Each page now inlines only the CSS it uses, loads far less JavaScript and skips heavy hero images. In Lighthouse on mobile, /citedby fell from 8.65s to 2.92s. Four of the five pages we sampled got faster.

ThriveStack citedbyLargest Contentful Paint: our slowest pagefell from 8.65s to 2.92sLCP in seconds, Lighthouse on mobile, live site. After is the average of 2 runs on Nov 1.GoodNeeds workPoor0s2.5s4s6s9sHome page-40%3.71 to 2.21s/citedby-66%8.65 to 2.92sAirlines page-49%3.89 to 2.00sPeec AI alternative-40%3.30 to 1.97sGA4 research page+16%3.30 to 3.83sBeforeAfterSource: ThriveStack Lighthouse runs, Oct 31 and Nov 1, 2026. Zones: web.dev.
Each row is one page, before and after. Green is good, amber needs work and red is poor.
  1. Critical CSS. Pages had to load a 393 KB stylesheet before showing anything. Each page now inlines its own rules and loads the rest without blocking.
  2. Less JavaScript up front. A shared helper was pulling a chart library onto every page. JavaScript preloaded on every page fell from about 400 KB to about 150 KB gzipped.
  3. No hero image. We rebuilt the /citedby hero in HTML and SVG, and shrank its headshots from 685 KB to 6 KB. Total page weight fell from 1,378 KB to 727 KB.

One page went the wrong way. The GA4 research page averaged 3.83s against 3.30s before, because its server took 2.4 to 3.5 seconds to respond in these runs. Front-end fixes cannot help with that, so it is our next thing to check. /citedby is also still above Google's 2.5 second threshold in Lighthouse. Our lighter throttled probe puts these same pages at about 0.6 to 1.8s, so treat any one tool as a guide. Real-user reports use a rolling 28 days and will catch up slowly.

Try ThriveStack citedby: See how AI engines cite my brand →

03 · CLS

How did we fix cumulative layout shift?

We fixed cumulative layout shift with fallback fonts sized to match our web fonts, hero glows moved with a transform, and a few line breaks that stay put as fonts load. Pages over the 0.1 limit fell from 8 to 0 on the live site. The home page dropped from 0.293 to 0.021, across the phone widths we tested.

ThriveStack citedbyCumulative Layout Shift: all eight failing pagesnow pass the 0.1 limitWorst CLS across phone widths on the live site, before and after our fixes.GoodNeeds workPoor00.10.25Home page-93%0.293 to 0.021Profound alt.-72%0.225 to 0.063AirOps alt.-89%0.216 to 0.023Searchable alt.-70%0.185 to 0.056Alternatives hub-92%0.168 to 0.014Semrush alt.-82%0.165 to 0.029Otterly alt.-85%0.137 to 0.020AthenaHQ alt.-88%0.113 to 0.014BeforeAfterSource: ThriveStack mobile probes, 4x CPU, slow 4G, worst of 2 to 3 runs. Zones: web.dev.
All eight pages are now under the 0.1 limit at each phone width we tested.

The home page surprised us. Fonts were not the cause. Its hero tabs change every 5 seconds at different heights, which moved a decorative glow by up to 463px. A short test never saw it, and Lighthouse did.

One page got worse before it got better. On the Semrush page at 360px, two fonts arrive about 400ms apart, so a line wrapped and then wrapped back. Our first fix took CLS from 0.165 to 0.269. A line break after the H1 colon and one in the intro, plus keeping the brand name on one line, brought it to 0.029. The good threshold for CLS is 0.1.

Try ThriveStack citedby: Audit my pages for AI visibility →

04 · Citations

What happened to AI citations after the speed fixes?

Not enough to credit the fixes yet. Visibility rose from 9.4% to 27.6% across the probes on November 1, 3 and 4, but our prompt list grew from 32 to 45 at the same time. On the original 32 prompts, visibility moved from 9.4% to 12.2%, which is inside our normal range.

ThriveStack citedbyAI Retrievals: Our count rose from 33 to 82after the speed fixesRetrievals of our domain per probe run, all tracked prompts. Runs on Nov 1, 3 and 4 came after the fixes.After the fixesthrivestack.aisemrush.com0255075100Aug 28Sep 8Sep 15Sep 22Sep 30Oct 6Oct 13Oct 20Oct 27Nov 1Nov 3Nov 43391948214Prompt panel: 32 prompts on Oct 27, 45 on Nov 4.Source: ThriveStack citedby probe data, Aug 28 to Nov 4, 2026.
Retrievals count how often our domain was pulled as a source in a probe run. Runs after the fixes: Nov 1, 3 and 4.

Raw retrievals of our domain rose from 33 on October 27 to 91, 94 and 82 on the three runs after the fixes. Semrush stayed in its usual range, with 24, 20 and 14. But eight of the 13 new prompts name us in every answer, so a bigger panel lifts the total by itself. The fair read is like for like.

On the 32 prompts in both runs, visibility went from 9.4% to 12.2% (35 of 288 answers), and answers citing our domain went from 9.4% to 11.1% (32 of 288). Three prompts were already at 100% before the fixes and still are. From October 6 to 27, visibility on each engine ranged from 3.1% to 12.5%, so 12.2% is not a signal yet.

Timing matters too. The first probe after the fixes ran on November 1, the day the last fixes shipped, so engines had little time to recrawl. We will keep probing weekly and report a verdict in December. Updated November 9, 2026.

Try ThriveStack citedby: Track my AI citations weekly →

05 · The link

Does page speed affect SEO the same way it affects AI answers?

Page speed does not affect SEO and AI answers the same way, and the evidence for AI is correlation so far (see section 1). Stronger sites also tend to be faster, which can explain part of the gap in SE Ranking's study.

ThriveStack citedbyAI Crawlers: Only the HTML path is read,so only part of speed work reaches themWhat a crawler that reads HTML and runs no scripts goes through, step by step.1Crawler asksfor your pageIt sends a request2Server answersresponse time (TTFB)Slow may mean timeout3Crawler readsthe HTML textNo scripts are run4Page can becited in an answerIf the text answers itConfirmedLikelyBrowser only: crawlers skip all of thisBlocking CSSJavaScript bundlesPainting the pageLCPCLSVisitors feel these. AI answers feel them only indirectly, through rankings and links.IndirectCrawlers read HTML only: Vercel and MERJ, Dec 2024. Likely and indirect are our own reading.
Only the solid boxes are confirmed for AI crawlers. The dashed and dotted parts are our reading.

The mechanism needs care too. Vercel found that none of the major AI crawlers run JavaScript, so a crawler never paints your page or sees a layout shift. See the quote near the top of this page. Our reading is that LCP and CLS help people, and they help AI answers only indirectly, through things like rankings and links. Server response time and text in the HTML reach the crawler directly.

Try ThriveStack citedby: Find my citation gaps →

06 · Learnings

Where should core web vitals work sit in an AEO plan?

Core web vitals work should sit after the basics of an AEO plan, and before polish. Make sure your answers are in the server-rendered HTML first, because a crawler can only quote what it can read. Then fix page load speed, because visitors and rankings benefit either way, whatever the citation result turns out to be.

  1. Find what really shifts. Our home page problem appeared only in a long test. Run Lighthouse as well as a short probe.
  2. Test more than one phone width. The Semrush problem appeared at 360px and nowhere else.
  3. Measure on the live site. One of our checks hit a redirecting host and reported the fix as missing.
  4. Check the server too. A slow response undid our front-end gains on one page.
  5. Baseline before you ship. We had citation data from October 27, which is what makes a fair test possible now.

Try ThriveStack citedby: Get my AI visibility fix list →

07 · Next

How will we measure AI search visibility after the fixes?

We will measure AI search visibility with the same weekly prompts on the same engines, for four weeks after the fixes. We will track retrievals, citations and visibility, and compare them to the competitors in those answers. If the fixes did nothing we can detect, we will publish that too.

ThriveStack citedbyTest Plan: We will judge the speed fixeson four weeks of probesA single week can move this much on its own, so one probe proves little.1OCT 27Baseline33 retrievals9.4% on ChatGPTBefore the fixes2OCT 31Fixes liveLCP on Oct 31CLS on Nov 1Next: pricing text3NOV 3 ONWeekly probesSame promptsSame enginesCompare to rivals4DECVerdictFour weeks inPublish the resultGood or badThriveStack citedby Research
Steps 1 and 2 are done, and probes ran on Nov 1, 3 and 4. Later dates are our plan.

This test has a limit we cannot remove. The speed work shipped alongside new content on the same pages, including a richer Gemini page and a new UTM guide. Pricing text changes are coming as well. So a rise could have several causes, and we will say so when we report it.

Try ThriveStack citedby: Set up my citation baseline →

08 · Checklist

What page speed checklist should you run before you ask AI to cite you?

Run these 14 checks in order. Start with the five crawler checks, because AI bots read your server HTML and do not run JavaScript. Then check the page is fast enough for AI to cite it: clear Google's good limits for FCP, LCP, CLS and INP, and aim for FCP under 0.4 seconds. Last, save a citation baseline and probe weekly. Tick each box as you pass it.

Page Speed Checklist: 14 checks that decide if AI can read and cite your page

Pass marks are Google's good limits from web.dev. Only the FCP stretch goal comes from AI citation data, and that is correlation. Tick the boxes as you go.

ACan the crawler read it?

Why: AI crawlers read the server HTML and do not run JavaScript.

BIs it fast enough for AI to cite?

No AI engine publishes a speed cutoff. Use Google's good limits as the floor, measured at the 75th percentile. The best-cited pages in SE Ranking's data painted in under 0.4 seconds.

CCan you prove it worked?

Why: one week of AI answers can swing with no change on your site.

Print this page to keep a copy of your ticked list. If you fail checks 1 to 5, fix those before any speed work, because a crawler cannot quote text it cannot read.

Not sure where to start? Your fail count tells you. Zero to two fails in group A means your pages are readable, so move to group B. Three or more means fix the server and the HTML first. Our own run: the GA4 research page still fails check 2 at 2.4 to 3.5 seconds, and /citedby still fails check 7 at 2.92 seconds.

Try ThriveStack citedby: Run my AI visibility audit →

Set your own citation baseline before you ship

ThriveStack citedby runs your prompts on the engines your buyers use each week, so you can see what really moved after a change.

Start free trial →
Frequently asked questions

Page speed and AEO: FAQ

What page speed is good enough to get cited by AI?

No AI engine publishes a cutoff. Aim for Google's good limits: HTML response in 0.8 seconds or less, FCP at 1.8 seconds or less, LCP at 2.5 seconds or less and CLS at 0.1 or less. In SE Ranking's data, the best-cited group had an FCP under 0.4 seconds.

Does page speed affect AI citations?

It may, but the evidence so far is correlation. SE Ranking reports that faster pages averaged more ChatGPT citations. In our own test, visibility on the same 32 prompts moved from 9.4% to 12.2% after the fixes. That is inside our normal weekly range, so we cannot credit speed yet. We will report a verdict in December.

Do AI crawlers care about LCP and CLS?

Not directly. Vercel found that the major AI crawlers do not run JavaScript, so they do not paint a page or see it shift. LCP and CLS mainly help human visitors, which may help AI answers through other signals.

What should I fix first for AEO, speed or content?

Check that your answers are in the server-rendered HTML first. A fast page with its answers hidden behind JavaScript still cannot be quoted. After that, speed work is worth doing for visitors and rankings.

How long does it take to see the effect?

Lab scores change on the day you ship. Google's real-user reports use a rolling 28 days. For AI citations, plan on several weekly probes, because one week can swing widely with no change on your site.

Try ThriveStack citedby: Check my page speed against my citations →

Sources

  1. Vercel and MERJ, “The rise of the AI crawler”. Dec 17, 2024. None of the major AI crawlers rendered JavaScript in this data; Gemini was the exception.
  2. SE Ranking, “How to Optimize for ChatGPT”. Read Nov 1, 2026. Correlational study reporting 6.7 vs 2.1 average citations by FCP.
  3. web.dev, Largest Contentful Paint. Good LCP is 2.5 seconds or less.
  4. web.dev, Cumulative Layout Shift. Good CLS is 0.1 or less.
  5. web.dev, Time to First Byte. Good TTFB is 0.8 seconds or less, poor is over 1.8 seconds.
  6. web.dev, First Contentful Paint. Good FCP is 1.8 seconds or less, poor is over 3.0 seconds.
  7. web.dev, Interaction to Next Paint. Good INP is 200 ms or less, poor is over 500 ms.
  8. Search Engine Journal, “New Data Reveals The Top 20 Factors Influencing ChatGPT Citations”. Read Nov 1, 2026. Reports the SE Ranking study of 129,000 domains, including Speed Index and INP findings.
  9. Discovered Labs, page speed and AI crawlability. Read Nov 1, 2026. Vendor guidance that claims AI crawler timeouts of 1 to 5 seconds. It cites no primary source, so we treat it as a claim.
  10. ThriveStack Lighthouse and mobile probes. Oct 31 to Nov 1, 2026, live site, mobile throttling.
  11. ThriveStack citedby probe data for thrivestack.ai. Weekly probes, Sep 15 to Oct 27, 2026.