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.
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?
Wait, what!? Obviously, I could name some great PWA solutions out there, but it wasn't always so. Today's case, migrated in November, is proving that you can build perfectly performant solutions, for real users, the traditional way.
If you reached this blog, then chances are you've heard of Cloudflare. CDN solution might be the first that comes to mind, but their focus is even broader. However, it stops at Core Web Vitals.
A lot has been said and written about Google's AMP. I even implemented AMP in the boilerplate CMS that I use for own cases. But how about AMP and Core Web Vitals?
Alpine is lightweight compared to Bootstrap, jQuery, Vue or React. So, why the complaints, you wonder?
Mid november, Google announced when and how Core Web Vitals will be part of organic ranking. In May, where pages will have a visual indicator of meeting Core Web Vitals. The first tests of Google were already seen.
Only 24% is passing the Core Web Vitals. This means your shop has the chance to not only get some highlighting in the search results, but also outperform your closest competitors. Let's dive into some numbers and toolings.
Things just got real! We already knew about Core Web Vitals. Google now published that your website will be highlighted within the Google search result pages.
Render blocking JS? Use Cloudflare Rocket Loader JS they said! But then Core Web Vitals came around, changing things 😕 However, Cloudflare Rocket Loader already came with a handful of pitfalls:
Earlier I wrote why to use PageSpeed Insights instead of GTmetrix, but this might not be accurate anymore by the end of the month. GTmetrix announced they will be moving to using Core Web Vitals as well.
Webflow was founded in 2012 and is an online visual editor platform allowing users to design, build and launch websites. Does this mean you can't get high PageSpeed scores? And what about the newest Core Web Vitals?
If you want to check the performance of your webshop or website, these are the best free toolings you can use.
The answer to one of my most asked questions (spoiler alert: it's because of SEO and UX).
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.
