Run to the light Carol Anne: Auditing with Lighthouse
summary
Lighthouse audits site performance, accessibility, best practices, SEO and limited security; Chrome DevTools flame charts supplement Lighthouse and pair Lighthouse with WebPageTest for correlation. Example site shows LCP 4.5s, FCP 1.7s, SEO 100 but accessibility failures (missing ARIA roles, poor color contrast) and console errors; target ranges: FCP 0–1.8s, LCP 0–2.5s, Speed Index 0–3.4s. Concrete fixes: change LCP element, reduce unused JS/CSS, remove render-blocking resources, add rel noopener noreferrer, add lang and meta viewport, and use incognito for clean audits.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:46Website audit importance
- 3:07Site performance and compliance
- 5:18Audit purpose and tools
- 7:24SEO and best practices
- 9:12Accessibility and markup
- 9:56Running Lighthouse audit
- 11:20Problems and solutions
- 12:46Accessibility and SEO fixes
- 13:26Key takeaways and closing
related talks
48mLighthouse for Chrome
35mExploring the Lighthouse
56mContinuous Accessibility: Adding Lighthouse to Your CI/CD Pipeline
43mHouse of Light
27mWays of Frontend performance auditing with Lighthouse
30mThe Pharos Of PWA, Deconstructing a Lighthouse Audit
22mYou’re Probably Using Lighthouse Wrong
27mHow to Measure Performance Effectively?