Note from 24 September 2020

Looks like #Lighthouse now suggests me to preconnect to the Google Analytics domain…

…which I already do! 🤔

Anything wrong with my HTTP header?

• Older: Note from 23 September 2020
• Newer: Note from 25 September 2020

Related contents with similar topics

1. 

   Karolina Szczur

   Why Lighthouse Performance Score Doesn’t Work

   • Nicolas Hoizey
   • 7 June 2024
   • WebPerf, Lighthouse
   • 2 reactions

   There is some correlation between the [Lighthouse] Performance Score and how well your site will do for real users. Still, lab testing alone doesn’t…

2. Note from 24 April 2024

   • Nicolas Hoizey
   • 24 April 2024
   • image, JPEG XL, Lighthouse, photography, WebPerf
   • 3 reactions

   Should I please Lighthouse with modern image formats, or my visitors with progressive rendering of large images in my photography site? 🤔

   

   Of course, this would be much easier with genaralized JPEG XL support, both modern and allowing progressive… 🤷‍♂️

3. Note from 21 March 2023

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

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

   

4. Note from 21 December 2022

   • Nicolas Hoizey
   • 21 December 2022
   • Google, Lighthouse, WebPerf
   • 15 reactions

   Same page tested on PageSpeed Insights over a few hours the same day, without anything modified, and the desktop scores vary from 19 to 59… 🤷‍♂️

   A lot of businesses rely on this crap to now if their site is "fast" enough for Google SEO! 😭

   

5. Note from 14 October 2022

   • Nicolas Hoizey
   • 14 October 2022
   • CLS, Core Web Vitals, Lighthouse, WebPerf
   • 4 reactions

   width and height attributes on <img> help prevent layout shifts (CLS). Values should be unitless integers.

   But #Lighthouse sees 100% as 100, thanks parseInt()…

   Do you think it should be improved?

   -> https://github.com/GoogleChrome/lighthouse/issues/14449