The answer to one of my most asked questions (spoiler alert: it's because of SEO and UX).
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?"
Some (WP) agencies are really into accessibility. However, when you do support accessibility as a developer, but not really pay close attention, there is a big chance you are unknowingly building inaccessible Wordpress websites for your clients.
Accessibility is like privacy: it often isn't the core business of a company. Even menu's become the victim. As a result, some might never be able to reach or interact with your main navigation.
Being a recommendation since June 5th, 2018, the Web Content Accessibility Guidelines 2.1 got translated to Dutch and published by Accessibility Foundation.
Recently, when discussing pagespeed optimizations within a platform migration, I was asked if fiber internet or 5G will make sitespeed issues go away, or just making it worse.
While there are a lot of articles to be found on the subject of pagespeed or improving overall sitespeed, most will come out-of-the-box.
To lazyload or not to lazyload images? From a user and performance perspective, you should lazyload images, but should you use a JS library?
Browsers are always trying to optimize as well. Some browsers already support lazyloading of images and iframes, using the loading attribute.
Resource hints or preloading is hot, I see it more and more in an attempt to (allegedly) improve website/shop performance, by preloading some assets.
Although most of my work is pagespeed-related, I also like to address web accessibility and carbon emission when doing R&D for our website-producing CMS.
DNS over HTTPS, Mozilla and Chrome already started experimenting with this a while back, to encrypt the last part of web traffic that isn't secure yet by default. But what really is the impact on privacy, security, as well as performance?
Last Thursday, I spoke at the sold out Tweakers Developers Summit. I talked about performance with a bit of conversion/UX/SEO/AMP and PWA.
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.
As of April 6, 2020, data-vocabulary.org markup will no longer be eligible for Google rich result features. Nothing new here for webdevelopers and SEO specialist out there. However..
Last Thursday, January 16th, I joined TJ Gamble's livestream to answer some PageSpeed related questions. Critical CSS was one of the subjects. Just before the livestream, I published a code snippet to auto-enable CSS critical Path within Magento 1.
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.
Twitter exploded when Chromium announced it. Chromium is describing it as "Moving towards a faster web", which is a clear signal towards digital agencies and other websites builders. What to expect?
As of version 2.3.3, Magento introduced CSS critical path. Users will experience a faster loading product-page when applied (correctly)!