Pagespeed findings

    • ± 3 minutes

    Digital accessibility week in the Netherlands

    This isn't sexy at all, but someone has to do it as your customers (or maybe even your very own relatives) could be subject to this temporary or even permanently.

    • ± 5 minutes

    Cloudflare Rocket Loader and Core Web Vitals

    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:

    • ± 2 minutes

    GTmetrix pagespeed: outdated and going to use Core Web Vitals

    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.

    • ± 4 minutes

    Webflow pagspeed and Core Web Vitals

    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?

    • ± 2 minutes

    Why isn't HTTP/2 improving the pagespeed score

    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?"

    • ± 3 minutes

    Accessible Wordpress themes for WCAG 2.1 websites

    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.

    • ± 4 minutes

    7 steps for building web accessible hamburger menu's

    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.

    • ± 1 minute

    WCAG 2.1 translated by Accessibility Foundation

    Being a recommendation since June 5th, 2018, the Web Content Accessibility Guidelines 2.1 got translated to Dutch and published by Accessibility Foundation.

    • ± 8 minutes

    Does 5G make my sitespeed issues go away?

    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.

    • ± 2 minutes

    How faster internet resulted in slower sites and webshops

    During the years 2011 through 2019, 4g coverage spread from 5% to 79% of the world. During that same time period, the median average JavaScript transfer size to mobile devices increased by 611%, from 52kb to 372.9 KB.

    • ± 1 minute

    Native image lazyloading support

    Browsers are always trying to optimize as well. Some browsers already support lazyloading of images and iframes, using the loading attribute.

    • ± 4 minutes

    Preloading with care

    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.

    • ± 3 minutes

    Fast, accessible and data-saving websites

    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.

    • ± 3 minutes

    Encrypting DNS query bad for performance?

    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?

    • ± 3 minutes

    Slides of Tweakers frontend performance talk

    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.

    • ± 3 minutes

    Web push notifications and acceptance rate

    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.