Note from 28 June 2021

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

• older note:
  Note from 28 June 2021
• newer note:
  Note from 6 July 2021

---

Related contents with similar topics

1. 

   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…

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

   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

3. • Nicolas Hoizey
   • 13 April 2023
   • Core Web Vitals, RUM, SpeedCurve, WebPerf
   • 11 reactions
   • permalink

   I love #SpeedCurve's simple and efficient Core Web Vitals Real User Monitoring, especially when everything is green! 🥳

   

   This is a real e-commerce site, with many real users everyday. After a few months of performance optimisation.

4. 

   Largest Contentul Paint change in Chrome 112 to ignore low-entropy images

   • Nicolas Hoizey
   • 7 April 2023
   • LCP, Core Web Vitals, image, WebPerf
   • 1 reaction

   This may result in LCP times increasing, if a low-content background was being painted very early, or if a low-content placeholder was being used…

5. • Nicolas Hoizey
   • 21 March 2023
   • Core Web Vitals, Google, WebPerf
   • 3 reactions
   • permalink

   Looks like Google likes it when we start improving websites performance! 🚀