Note from 28 June 2021

Rhetorical WebPerf question: is it better to have a low or stable Cumulative Layout Shift? 😅

• Older: Note from 28 June 2021
• Newer: Note from 6 July 2021

Related contents with similar topics

1. 

   Jeremy Wagner

   New field insights for debugging INP

   • Nicolas Hoizey
   • 20 May 2024
   • INP, WebPerf, Core Web Vitals
   • 2 reactions

   Interaction to Next Paint (INP) is a Core Web Vital that measures how responsive a page is to interactions. Due to INP's scope, it can be difficult…

2. Note from 30 October 2023

   • Nicolas Hoizey
   • 30 October 2023
   • CLS, SpeedCurve, WebPerf
   • 2 reactions

   I love (some) boring #SpeedCurve graphs… 😅

   

3. Note from 6 June 2023

   • Nicolas Hoizey
   • 6 June 2023
   • Core Web Vitals, image, LCP, WebPerf
   • 6 reactions

   Apparently, an image whose part above the fold is indeed the largest, but of which only a small part can be seen, can be considered an LCP element, even if another image has a larger part visible... 😭

   You can see this for my photography site in this WebPageTest result:

   https://www.webpagetest.org/vitals.php?test=230606_BiDcN4_4NJ&run=3&cached=0#lcp

   

4. 

   Paul Hebert

   Watch Out for Layout Shifts with ‘ch’ Units

   • Nicolas Hoizey
   • 31 May 2023
   • WebPerf, Core Web Vitals, CLS, CSS
   • 5 reactions

   In our case, we were using ch units to define our page layout. This meant that our post content was equal to 50ch units (or the width of fifty…

5. Note from 16 May 2023

   • Nicolas Hoizey
   • 16 May 2023
   • Core Web Vitals, image, LCP, WebPerf
   • 3 reactions

   Limiting the image density on mobile devices drasticaly improves performance, with no visual loss, so we did it!

   

   I still wish it was much easier than dealing with <picture> and x descriptors for fluid images… 😞

   With a <img maxdensity="2.5" …> attribute for example!

   If you agree, comment:
   https://github.com/whatwg/html/issues/4421