Lighthouse, Headless Chrome, and Puppeteer
summary
Lighthouse runs automated audits (Performance, Accessibility, PWA, Best Practices) from DevTools, the Chrome extension or the CLI, emulates a Nexus 5X on 3G throttling, reports metrics like First Meaningful Paint and Time to Interactive and gives a numeric score (example shown: 63). Adoption shows roughly 100,000 extension users and 250,000 npm installs with 100+ contributors. Puppeteer ships a Chromium build, connects via the remote debugging port, and scripts screenshots, PDFs, device emulation, request interception and page.metrics for CI testing.
AI-written summary · about
chapters (11)
- 0:00Start
- 8:54Adoption
- 9:55The Team
- 16:42Install it
- 16:54Take a screenshot
- 18:41Emulate a device
- 19:16Run code in page
- 21:37Intercept network requests
- 22:40Keyboard input
- 24:24Turn off JS
- 25:56Debugging options
related talks
21mThe Future of Performance Tooling
48mLighthouse for Chrome
56mContinuous Accessibility: Adding Lighthouse to Your CI/CD Pipeline
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
01h 15mPuppeteer can automate that!
35mExploring the Lighthouse
30mModern Web Testing and Automation with Puppeteer
22mYou’re Probably Using Lighthouse Wrong