Can't get enough? I'm regularly sharing snack bite tips and advice on LinkedIn as well.
A platform can take a long time to generate a webpage. But when the content is cached, TTFB and users will benefit, but the first user accessing new contents will pay a penalty. How to prevent this and improve the cache hit ratio?
Rarely can you increase your PageSpeed with a single line of CSS. Today, though, I will share two separate CSS lines of code that will improve pagespeed and performance.
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.
WordPress started a performance team to improve its Core Web Vitals scores. I read their pagespeed optimization spreadsheet and boy do I have an opinion regarding their performance backlog.
Google hasn't been sitting still. Both LCP and CLS have been seeing drastic changes already, so why not changing the FID metric?
I've been sharing charts of Core Web Vitals passing platforms recently, so here's the shared source of truth for the way websites are both built and experienced.
Wordpress recently wrote about the performance impact of jQuery, but it seems like they are choosing to not call out the real pagespeed bottleneck.
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.
