
I was wrong about Google Lighthouse TTFB
I’ve spent years knee-deep in Lighthouse in my first few pagespeed years. I always assumed that one part was intentional design decision, but after 5 years I learned I was wrong.
Can't get enough? I'm regularly sharing snack bite tips and advice on LinkedIn as well.

I’ve spent years knee-deep in Lighthouse in my first few pagespeed years. I always assumed that one part was intentional design decision, but after 5 years I learned I was wrong.

While two completely different things, there actually is a correlation between pagespeed and accessibility.

We've all heard of the 'eliminate render blocking resources' recommendation in Lighthouse. But to understand why it is important to fix this, it first is convenient to know a few basic principles of browsers.

I've seen pagespeed audits where Google Analytics' Average Page Load Time was used to determine bad performing pages and claiming the webshop was missing revenue. However, pagespeed is more nuanced.

So there's that, it has been said. Your Lighthouse score doesn't matter. Let's nuance this a bit.

Wondering why Lighthouse is recommending you to fix this, although you don't see any layout shifts yourself, and why is it warning you only now and not before?

Progressive Web Apps have quite some advantages. The biggest one being a web-product with a native-like feeling. But it is also fast and mobile first, or rather should be. This is the untold story about PWA, impacting your conversion.

First Meaningful Paint is one of the six performance metrics tracked and displayed by Lighthouse. It measures when the primary content of a page is visible, but is more of a guess. It became time for a new metric.

The biggest challenge under the former PageSpeed Insights test has been completely annulled as the PageSpeed Insights uses the Lighthouse engine nowadays.