Ways of Frontend performance auditing with Lighthouse
summary
A pipeline using lighthouse cli and chrome-launcher runs headless audits, emits JSON, and enforces budgets so builds fail when scores drop; manual DevTools reports evolve into automated checks integrated with Jenkins + Travis + GitHub CI and the lighthousebot docker image for PR comments. Custom gatherers and audits plug into Lighthouse’s artifact-driven architecture, results feed mocha-style assertions, and a small pilot expands to company-wide rollout after measurable real-user improvements.
AI-written summary · about
chapters (19)
- 0:00Start
- 2:25Agenda
- 4:53How?
- 5:42Real User Data
- 6:35Manual Tests
- 8:05Automation
- 9:13Increase the reach
- 9:49Following steps
- 12:49Command Line
- 13:49npm package
- 15:22Lighthouse Report
- 18:06Performance budget
- 18:45Want more tests?
- 19:20Architecture
- 20:11Gatherers
- 22:17Custom Config
- 22:45Integration to CI
- 23:13GitHub & Travis
- 27:15References
related talks
22mUsing Lighthouse in the Real World
35mExploring the Lighthouse
14mRun to the light Carol Anne: Auditing with Lighthouse
30mThe Pharos Of PWA, Deconstructing a Lighthouse Audit
21mThe Future of Performance Tooling
22mYou’re Probably Using Lighthouse Wrong
14mAutomate Performance Monitoring for Micro Frontend Apps
48mLighthouse for Chrome