> web.dev is operating on some irritating assumptions: > 1. Smaller assets are ideal. > 2. Minimalistic design is necessary. This doesn't sound right to me.

> web.dev is operating on some irritating assumptions: > 1. Smaller assets are ideal. > 2. Minimalistic design is necessary. This doesn't sound right to me. Aren't the three new page metrics mostly targeting what happens when the page initially loads? https://web.dev/vitals/ https://web.dev/vitals/ > Largest Contentful Paint (LCP): measures loading performance. To provide a good user experience, LCP should occur within 2.5 seconds of when the page first starts loading. > First Input Delay (FID): measures interactivity. To provide a good user experience, pages should have a FID of less than 100 milliseconds. > Cumulative Layout Shift (CLS): measures visual stability. To provide a good user experience, pages should maintain a CLS of less than 0.1. The first two are about initial loading. For the last one, you can avoid layout shift by e.g. reserving space for images that are yet to load fully. For example, it sounds like your page could load 100MB of images with the most complex design ever, and it would get a good score as long as the initial viewport of the page displays quickly, is interactive quickly, and doesn't jump around as it's loading. They sound reasonable metrics to me in terms of fighting bloat but with flexibility for web developers (as opposed to AMP). Who gets to decide the metrics is another issue though.