Lighthouse 10.0 is out.

• updated scoring (we'll kind of miss you TTI. ok not really)
• bfcache compatibility audit
• user flows general availability
• complete type declarations
…and 495 commits of goodness.

https://developer.chrome.com/blog/lighthouse-10-0/

What's new in Lighthouse 10 - Chrome Developers

Lighthouse 10 is here with new scoring and audits.

Chrome Developers
@paul_irish Congrats Paul + team, looks like a fantastic release! Looking forward to Mar 29th when it hits stable! 😍

@paul_irish Great article!

Is there more description on why TTI is being removed?

The article seems to imply "we're removing it because 13 million sites scored badly with TTI enabled", which I'm sure isn't the real technical reason...

@jesstelford A lil bit more here https://github.com/GoogleChrome/lighthouse/blob/main/docs/v8-perf-faq.md#whats-the-story-with-tti

TTI marks a point in time (seems useful), but that calculation means it can be overly sensitive to a rogue long task. TBT meanwhile handles that and the typical situations much better, so we consider it a far more robust metric for main thread availability.

lighthouse/v8-perf-faq.md at main · GoogleChrome/lighthouse

Automated auditing, performance metrics, and best practices for the web. - lighthouse/v8-perf-faq.md at main · GoogleChrome/lighthouse

GitHub
@paul_irish Fantastic, that makes much more sense to me now 🎉

@paul_irish TTI 🥲

I get why LH has switched to TBT given TTI’s potential instability though