Why is our asynchronous livechat widget loading speed still failing core web vitals even after we deferred the javascript tag?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Why is our asynchronous livechat widget loading speed still failing core web vitals even after we deferred the javascript tag?
2 real searches · 1 real-search pass
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.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Google web.dev third party JavaScript Core Web Vitals INP LCP CLS defer script performance guidance Google ↗
web.dev optimize third party JavaScript facade lazy load chat widgets Core Web Vitals Google ↗
- web.dev/src/site/content/en/blog/optimizing-content-efficiency-loading-third-party-javascript/index.md at main · GoogleChrome/web.dev · github.com
- Can browsers optimize the loading of third-party resources? | Blog | Chrome for Developers · developer.chrome.com
- Optimizing Web Vitals using Lighthouse | Articles | web.dev · web.dev
- Best practices for using third-party embeds | Articles | web.dev · web.dev
- Understanding Core Web Vitals and Google search results | Google Search Central | Documentation | Google for Developers · developers.google.com
- Core Web Vitals report · support.google.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Google web.dev third party JavaScript Core Web Vitals INP LCP CLS defer script performance guidance OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
web.dev optimize third party JavaScript facade lazy load chat widgets Core Web Vitals OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |