Can't get enough? I'm regularly sharing snack bite tips and advice on LinkedIn as well.
There is nothing wrong with the mindset of AMP. However, news publishers felt forced to start using Google's AMP HTML framework for their articles for SEO reasons while you could achieve same pagespeed results without AMP.
If you're looking for PageSpeed Insights, you now get redirected to their new testing environment: The PageSpeed Insights layout has changed as of today.
When doing pagespeed audits, there often is a common pitfall that I see happening across different webshops. If you're using Cloudflare, then this might help you out as well.
It's happening. Wordpress is finally going to focus on performance. But why now, and will it succeed?
You might not be aware yet, but chances are that the e-mail or social media campaigns and ads you're running, are impacting user experience.
You might have noticed that your LCP will often be worse than your FCP. This is quite common, as the header, hamburger menu or (inlined) SVG logo will be rendered sooner than the rest of the page. But what does it mean if your LCP and FCP are almost the same?
A/B testing is often used to come up with better headlines or layout, increasing conversion. However, even today A/B testing isn't always implemented in an optimal way, negatively impacting your business instead.
So there's that, it has been said. Your Lighthouse score doesn't matter. Let's nuance this a bit.
Reddit might not be the first platform you think of when talking about SEO or Core Web Vitals. However, this exact same question got asked on Reddit and led to a surprising reply.
Wether you're reading a LinkedIn or Twitter discussion, there still is confusion around lazyloading images. Especially when it comes to above the fold images, such as hero images. Let's deal with this for once and for all.
You're on stackoverflow or MDN docs and found a code snippet that should help pagespeed. Just copy + paste it and hope it works!
When it comes to Core Web Vitals, there isn't a one-size-fits. And the same actually applies to (Shopware) shops, as each will have some customized functionality. However, rule of thumb are the same when it comes to Core Web Vitals, but also the typical Shopware shop as they are sharing the same boilerplate.
Google I/O is an annual developer conference held by Google. "I/O" stands for input/output, as well as the slogan "Innovation in the Open", where they typically introduce new developments.
November 2020 I (and Google) reported that Core Web Vitals would become a ranking factor. This week Google has announced that this has been delayed for several weeks.
Layout shifts aren't a good look and should be below 10%. And while it might actually attract visitors in some contexts, shifts on a website might lead to page abandonment. But there's more to it.
"Critical CSS is a must-have for a good pagespeed and core web vitals score". I saw this statement passing by recently, and although using critical CSS myself, such claim comes with nuance.
So, you've got a hero image which is actually messing up your LCP metric in Lighthouse or PageSpeed Insights? You might not have heard this before, but making it even bigger will help.
Google Lighthouse has recently had an update. This may also have (negatively) influenced your scores. I briefly paid attention to it in a LinkedIn post, but in this blogpost I will go into it a bit more deeply.
You're on a quest to achieve green results as Core Web Vitals is coming closer. Can PageSpeed Insights be deceived to rank better?
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?
