Lighthouse analyzes web apps & sites, collecting modern performance metrics and insights on best practices. 📊 And yes, that's 4 underscores, my friends!

Joined February 2017
25 Photos and videos
Lighthouse v11.2 includes an overhaul to the performance category that focuses audit prioritization on estimated impact to the performance metrics. Also included is an upgraded score gauge. On hover, it visualizes how each performance metric affects the overall performance score.
6
87
359
41,771
Lighthouse retweeted
Never knew @____lighthouse had fireworks when you got your page to 100% #webdevelopment #website
1
6
29
3,377
Didja know Lighthouse has a diff tool? 🤔 Compare two reports and see all the changes. googlechrome.github.io/light…
70
191
33,793
In Lighthouse 10.1, we've upgraded reporting of third parties and their impact: ➡️Audit tables are now grouped by party ➡️Detected third parties are tagged with their category (and linked!), so it’s easier to identify their purpose
4
21
82
17,051
➡️The Lighthouse JSON now also includes a top-level `entities` object with data on all detected first and third parties.
1
2
12
2,259
Lighthouse 10.0 is here!💡🚢 ➡️updated scoring (we'll kind of miss you TTI) ➡️bfcache ➡️complete type declarations ➡️read more: developer.chrome.com/blog/li…
13
148
581
135,088
PageSpeed Insights has expanded! The lab section now includes the entire Lighthouse report: Accessibility Best Practices SEO Try it now: pagespeed.web.dev
3
57
234
Lighthouse retweeted
Have you try out the new audit modes in @____lighthouse @ChromeDevTools yet? Use the Timespan mode to identify layout shifts and JavaScript execution time over a time range including interactions. Learn about the Snapshot mode and more 👉🏼 developer.chrome.com/blog/ne…
2
13
67
Now that the May HTTP Archive dataset is out with some URL-level data in the mobile pages table, I thought it would be a good time to repeat some internal analysis I did on the public dataset: colab.research.google.com/dr…
3
9
30
Lighthouse retweeted
12 May 2022
There have been a LOT of recent developments in the world of web performance and Core Web Vitals that are being showcased at Google I/O this week. Here's a rundown of the highlights, so you don't miss anything 👇
7
106
417
Poll📊: Have you used the new Lighthouse for User Flows? (aka Lighthouse analysis of puppeteer-scripted scenarios) web.dev/lighthouse-user-flow…
50% No, but I'm interested!
29% Nope
17% Yeah, I tried it out
4% Yes, been using regularly
102 votes • Final results
4
9
Lighthouse CI has been updated to Lighthouse 9.3.0! Great for continuous perf monitoring. Changelog: goo.gle/lhci9 Learn how to use LHCI: web.dev/lighthouse-ci
12
46
Lighthouse 9.0 is here! 💡🔅🔆⛵ Look for user flow support, a refreshed report, and more helpful accessibility audits. Try it through npm, Chrome Canary, or the new PageSpeed Insights! developer.chrome.com/blog/li…
1
89
237
Lighthouse retweeted
16 Nov 2021
Introducing the new PageSpeed Insights: a more intuitive way to measure performance & improve it using real-world and lab data. Details: bit.ly/new-psi Try it: pagespeed.web.dev
19
242
797
Introducing Lighthouse for user flows: drive your page with a Puppeteer script and have Lighthouse measure and audit performance at every step: web.dev/lighthouse-user-flow…
13
391
1,650
💡What's new in Lighthouse 8.4!💡 New audits to check that: 🖼️ LCP images aren't lazy-loaded 📲 A mobile meta viewport is used (don't wreck your FID!) developer.chrome.com/blog/li…
3
23
80
We're trying this out as a more in-depth companion to the usual changelog (github.com/GoogleChrome/ligh…). Let us know what you'd like to see in these posts in the future!
7
Lighthouse now considers the (sometimes significant) improvements that AVIF image compression can bring when advising on improving image load time! Look for the estimates under "next-gen formats" in the Lighthouse report 🤏🖼️⚖️
1
26
68
Lighthouse retweeted
It's a smaller aspect of the Lighthouse 8 release, but we've been shrinking dependency install size. Features moving into Node core has been key, like full-icu builds by default. Thanks @nodejs :) If you run Lighthouse in a container somewhere, this should help slim things down
1
1
27