Common misconceptions around Google Lighthouse
summary
Claims that a high Lighthouse score equals good UX are false: a migration can raise individual metrics while lowering the score; Lighthouse runs as lab data on an emulated Moto G4 or in Chrome DevTools influenced by CPU, extensions and throttling; PageSpeed Insights uses Google datacenters and surfaces real user metrics from the Chrome User Experience Report; the scoring weights and metrics (soon interaction to next paint) change often; CI use with Lighthouse CI, incognito runs, and checking field CRUX percentiles are the actionable steps.
AI-written summary · about
chapters (4)
- 0:00Start
- 22:37Good performance is a tradeoff
- 23:02Use Lighthouse to get a perception of how new release will affect your performance
- 23:55Don't use Lighthouse to measure how your users experience your website
related talks
22mYou’re Probably Using Lighthouse Wrong
40mYou’re probably using Lighthouse wrong bt Filip Rakowski
38mYou’re probably using Lighthouse wrong
42mYou’re probably using Lighthouse wrong
26mDemystifying Lighthouse, CrUX, and Core Web Vitals
27mHow to Measure Performance Effectively?
21mYour Lighthouse Score Doesn’t Matter on 3G
16mFrom beginner to expert in web performance