Wordpress recently wrote about the performance impact of jQuery, but it seems like they are choosing to not call out the real pagespeed bottleneck.
To reduce page size plus your user's data usage and improve loading speed (depending on your audience) it is best to minify JS and CSS files. Fortunately, many developers or just plugins are already doing this by default. However..
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.
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?
The sad part of third party chat widgets is that it really is up to chat widget providers to improve performance, caring about the performance of their clients' websites and webshops at the same time. But even when they don't, we can make a difference.
I wrote my own chatbot + livechat and this created quite some fuzz on LinkedIn. I even received swear words, luckily just for chatbot testing purposes 😅. But let's talk about the harm of chat bots such as Zopim (Zendesk), and how I visualized this.
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:
Sometimes a LinkedIn post of mine is leading to new questions as well. This time: "How do you get a high PageSpeed score when a site is using HTTP/2?"
Have websites been misusing push notifications? Website owners started to abuse push notifications with user complaints as a result. The idea was great, but now Google itself is stopping it.
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.
As of version 2.3.3, Magento introduced CSS critical path. Users will experience a faster loading product-page when applied (correctly)!
Should you favor skeleton loading over spinner loading, and what would be the difference between building a PWA or server rendered website?