Instant noodle soup is not the best example, but would you trust shellfish that would've been in boiling water for just 100 milliseconds? Well that's where I had to change things to give users a trustworthy feeling.
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.
With website visitors from around the globe and having to convert currencies when doing a quotation, I figured embedding a currency converter instead.
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?
That sounds like clickbait, or at least too good to be true, right? That's what I thought. No rocket science and overengineering over here.
Alpine is lightweight compared to Bootstrap, jQuery, Vue or React. So, why the complaints, you wonder?
Before, we learned that content-visibility is likely to improve the pagespeed and performance of your website. But considering all caveats, how should you approach content-visibility implementation yourself?
Content-visibility is a new CSS property that boosts your rendering performance, according to Google. But is that really so and are there any caveats, or in other words, should you start using it already?
There are JavaScript and CSS solutions out there to break words. However, they often don't break words in an organic way. Today, I am sharing a piece of code which I use to break words the way I want, maintaining SEO value at the same time.
I wrote about the Backlinko results in November 2019 on LinkedIn, tagging Brian as well. But it looks like Brian already put some effort into the pagespeed of his website. As a result, he is now passing Core Web Vitals.
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.
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.
Did you know that a dark mode could save 63% power usage on mobile devices? More important from UX perspective is that you can also introduce a dark mode to make your site more pleasant for all kinds of users.
You might be using Bootstrap, or maybe even never considered outlines. Or deliberately removed them, leaving your users in the dark. However, outlines or focus indicators can still be fancy and helpful at the same time, without impacting
You don't want to ruin the look of your website or webshop by some random ugly borders. These borders are called outlines and happen to aid some users as if you are walking in the dark with no lights. So, don't just remove them!
If you are already into web accessibility, so-called jump-to or skiplinks might not be new to you. Here is an introduction on skiplinks and some additional food for thought.
