efedorenko

Author here. The article was published 2 years ago, and when I started working on the tool the spec for OkLCH didn't even come out yet (late Dec 2020). Today I'd choose OkLCH over LCH as it solves a few problems with it.

> …the test is only concerned with the one page you are testing

I use a Lighthouse score for troubleshooting, but at the end of the article there is a chart of the change in Core Web Vitals, which tracks performance of _all_ pages indexed by Google over time.

> "…nearly everything it suggests you do will make that second page load slower…"

This is just not true for _any_ of the suggestions in the article. I guess you can make this argument for breaking down one CSS bundle into four, but their content was picked based on analytics of where people go more often. We make 1 extra request but load much less cruft, and it applies to any page of the website.

The Lighthouse score is just a detailed and useful metric for troubleshooting, but not the only one we monitor. I included a chart from our Core Web Vitals in the end, which monitors the performance of all pages indexed by Google and uses actual usage data from a wide sample of users (Chrome User Experience Report).

Hi, author here. Accessibility score went from 87 to 96. The second screenshot with a score of 86 was a preliminary result after introducing the fake widget. (Best Practices went from 86 to 100.)

That was one of the things that confused the hell out of me as well.

There is a point when super quiet environment with other people becomes uncomfortable. We often keep music on quietly even if there are just a couple people in the office.

Colors and images were used long before text to convey information. Then they were used together with text (see first books). Using just text without colors and images is a relatively new invention caused by technical limitations, and it didn't last long.