@____lighthousei
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
Lighthouse analyzes web apps & sites, collecting modern performance metrics and insights on best practices. 📊 And yes, that's 4 underscores, my friends!
Github, your browser, your CLI
Joined February 2017
- Tweets83
- Following21
- Followers14.4K
- Likes16
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.
Didja know Lighthouse has a diff tool? 🤔 Compare two reports and see all the changes.
googlechrome.github.io/light…
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: developer.chrome.com/blog/li…
PageSpeed Insights has expanded! The lab section now includes the entire Lighthouse report:
+ Accessibility
+ Best Practices
+ SEO
Try it now: pagespeed.web.dev
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…
Lighthouse retweeted
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…
Lighthouse retweeted
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) 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 resultsLighthouse 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
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…
Lighthouse retweeted
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
The new PageSpeed Insights
We made the UI more intuitive by clearly differentiating between data derived from a synthetic environment + data collected in the field. We also clearly communicate how the CWV is calculated.
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…
💡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…
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!
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 🤏🖼️⚖️
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