Earlier quoted context omitted.
* The web vitals themselves are unquestionably good for the user* Fast pages are good, but Google is using their tools like Page Speed to push you to adopt Google’s ideas of fast, like using WebP for images. So now you might have a bunch of cruft in your page to support multiple image types. Also, as user, I hate lazy loading. I can scroll faster than images load. I’d rather everything load in the beginning, and have…
WebP is good iff it improves rendering times (which it does). That's not google's fault really. Any way you can come up with to optimize images is valid under Core Web Vitals. I really don't think any of it is skewed towards Google's solutions except the testing/measurement methodology. I would love open source data collection across browsers for instance. Lazy-loading can be implemented sloppily, but browser-native…
The problem is that Google Page Speed dings you for not having lazy loading, and people add crappy JavaScript lazy loading that satisfies Google, but makes the user experience worse.
WebP is good iff it improves rendering times (which it does). That's not google's fault really.
The problem has been, until recently, Safari didn't support WebP, so you had to implement a fallback to jpg. More complicated HTML, more images to compress and manage, all for a very marginal improvement.