How to Measure Performance Effectively?
summary
Explains how Lighthouse CI (available as a GitHub Action) and PageSpeed Insights give lab audits while the Chrome User Experience Report supplies 28‑day field data, and why lab improvements don’t guarantee real user wins. Calls out Core Web Vitals by name — LCP, FID, CLS — shows that Google uses the 75th percentile mobile for SEO boosts, and gives a surprising metric: average compressed JavaScript on mobile is around 450 KB, which often produces multi‑second LCPs. Shows automating Lighthouse tests and comparing individual metrics over time.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:51Google Lighthouse
- 6:03Good or Bad Result
- 8:41Performance Metrics
- 11:18Largest Contentful Paint
- 13:04First Input Delay
- 14:32Cumulative Layout Shift
- 15:36Lighthouse Audit
- 18:01Lab and Field Data
- 19:20Real World Examples
- 20:04Field Data
- 20:17Chrome User Experience Report
- 21:39Facebook Insights
- 24:50Conclusion
related talks
26mDemystifying Lighthouse, CrUX, and Core Web Vitals
22mYou’re Probably Using Lighthouse Wrong
40mYou’re probably using Lighthouse wrong bt Filip Rakowski
16mFrom beginner to expert in web performance
49mDemystifying web performance tooling and metrics
15mWhat's new in Web Vitals
31mPanel Discussion: Get to Know: Web Performance and Core Web Vitals
15mCore Web Vitals – Measuring Performance Like a Pro