What are the most critical Core Web Vitals fixes for a slow mobile site failing Largest Contentful Paint today when my developer is only available for the next two hours?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What are the most critical Core Web Vitals fixes for a slow mobile site failing Largest Contentful Paint today when my developer is only available for the next two hours?
1 real search · 1 real-search pass
Google web.dev Largest Contentful Paint optimize LCP threshold 2.5 seconds subparts TTFB resource load delay render delay 2026Google ↗
OBSERVEDConsequence
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
Google web.dev Largest Contentful Paint optimize LCP threshold 2.5 seconds subparts TTFB resource load delay render delay 2026 Google ↗
- Run mobile performance test · pagespeed.web.dev
- Lighthouse documentation · developer.chrome.com
- Core Web Vitals report · search.google.com
- Understanding Core Web Vitals and Google search results | Google Search Central | Documentation | Google for Developers · developers.google.com
- Largest Contentful Paint (LCP) | Articles | web.dev · web.dev
- Core Web Vitals report · support.google.com
- Optimize Largest Contentful Paint | Articles | web.dev · ccn.web.tr
- chrome-devtools-mcp/skills/debug-optimize-lcp/SKILL.md at main · ChromeDevTools/chrome-devtools-mcp · github.com