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.

Never knew @____lighthouse had fireworks when you got your page to 100% #webdevelopment #website

Didja know Lighthouse has a diff tool? 🤔 Compare two reports and see all the changes. https://t.co/nr1Gl0v312

➡️The Lighthouse JSON now also includes a top-level `entities` object with data on all detected first and third parties.

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

Lighthouse 10.0 is here!💡🚢 ➡️updated scoring (we'll kind of miss you TTI) ➡️bfcache ➡️complete type declarations ➡️read more: https://t.co/ihKjYKDpWR

PageSpeed Insights has expanded! The lab section now includes the entire Lighthouse report: + Accessibility + Best Practices + SEO Try it now: https://t.co/XTc9oMhF6b

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 👉🏼 https://t.co/DD74phufty

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:

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 👇

Poll📊: Have you used the new Lighthouse for User Flows? (aka Lighthouse analysis of puppeteer-scripted scenarios)

Lighthouse CI has been updated to Lighthouse 9.3.0! Great for continuous perf monitoring. Changelog: https://t.co/bROBzZyvZA Learn how to use LHCI: https://t.co/K8tliTbZzD

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! https://t.co/qAKDrWEPGp

Introducing the new PageSpeed Insights: a more intuitive way to measure performance & improve it using real-world and lab data. Details: https://t.co/wxk98nOWOE Try it: https://t.co/MOHTC8eRvP

Introducing Lighthouse for user flows: drive your page with a Puppeteer script and have Lighthouse measure and audit performance at every step: https://t.co/R7qmEIFNEc

We're trying this out as a more in-depth companion to the usual changelog ( https://t.co/wO13P73wez). Let us know what you'd like to see in these posts in the future!

💡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!) https://t.co/7shZWtcIQI

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 🤏🖼️⚖️

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