Challenging Assumptions About LCP Best Practices
summary
Data show LCP remains the weakest Core Web Vital and images are the most common LCP element, with surveys like Web Almanac saying almost one in five mobile pages lazy‑load their LCP images and Shopify reporting ~67% of sites doing so; resource load delay and element render delay are the dominant subparts. Field collection via Chrome real‑user data or the LCP API beats lab tests (PageSpeed Insights / HTTP Archive Lighthouse runs) for prioritization. Quick wins that actually move numbers include removing JavaScript lazy‑loading for LCP images, adding preload/fetchpriority, and validating with RUM; CrUX and tooling updates are rolling out to expose these subpart breakdowns.
AI-written summary · about
chapters (23)
- 0:00LCP best practices debate
- 1:50Core Web Vitals past and future
- 3:55Why LCP remains critical
- 5:18Understanding LCP subparts
- 9:35Lazy loading LCP images anti-pattern
- 13:14Optimizing resource load time
- 14:41Reducing element render delay
- 16:51Worst LCP subpart poll
- 17:33LCP subpart data collection
- 21:27Analyzing LCP subparts
- 23:56Future LCP optimization steps
- 26:05Chrome UX Report LCP insights
- 27:50Worst LCP subpart revealed
- 28:55Key LCP optimization summary
- 29:17Q&A on lazy loading LCP
- 30:23Chrome UX Report role
- 31:51Optimizing LCP for video
- 32:53LCP thresholds on mobile
- 34:39Prioritizing LCP fixes
- 38:58Excluding cookie banners
- 40:03LCP revenue impact
- 41:49LCP behind login
- 42:53Q&A wrap-up
related talks
46mOptimising Largest Contentful Paint
46mOptimising Largest Contentful Paint
29mA deep dive into optimizing LCP
15mThe business impact of Core Web Vitals
56mQuick Wins for Backend Developers
25mCore Web Vitals under control
30mThe ins and outs of Core Web Vitals
29mCore Web Vitals: Put Your App into Orbit with Best Practices