Loading...
Loading...
Browse 4 real-world technical and behavioral interview questions about Core web vitals. Review scenarios, edge cases, and architectural best practices.
Async controls when a script downloads, not what it does to the main thread once it executes, so an async tag can still block interaction handling. Prove it with field data attributed to the interaction: INP breaks into input delay, processing and presentation, and each points elsewhere. Then move the work off the critical path.
Split the LCP into TTFB, resource load delay, resource load time and render delay, use field attribution rather than a single lab run to see which part dominates, then fix that part specifically - prioritise the hero image, stop lazy-loading it, and remove render-blocking work.
Split the interaction into input delay, processing time and presentation delay, then attribute a real interaction from the field rather than guessing. Most of the budget is usually spent before your handler runs or after it returns, so yielding and cutting rendering cost beats optimising the handler.
Layout shift is a field problem: it depends on network speed, consent banners, ads and personalisation that a lab run never sees. Collect layout-shift entries from real sessions with their source nodes, then reserve space for whatever moved.