
Measuring the real-world impact of Speculation Rules with RUM
Speculation Rules can make page-to-page navigations feel almost instant by allowing the browser to prepare the next page before the visitor actually clicks.
Can't get enough? I'm regularly sharing snack bite tips and advice on LinkedIn as well.

Speculation Rules can make page-to-page navigations feel almost instant by allowing the browser to prepare the next page before the visitor actually clicks.

Shared Compression Dictionaries promise smaller HTML responses and faster navigations. Implementing them on a real website without a CDN turned out to be a lot more educational than expected.

I like the new Speculation Rules API which allows sites to prerender (potential) next navigations. But I'm not a fan of third parties loading right away.

A topic I’ve covered many times already in LinkedIn posts and both in-house and public talks: the performance impact caused by consent management platform (CMP) scripts.

While investigating a site-speed anomaly, I discovered a critical bug that was silently breaking performance monitoring for potentially many WordPress sites.

This is a heads-up when using latest WP Rocket (13.9) on your WP or WooCommerce site. Preconnecting to third parties now comes out of the box, but comes with a sitespeed trade-off.

Everyone’s preloading fonts for faster sites. But did you know it can secretly regress your First Contentful Paint instead? Let’s look at when preloading helps, when it hurts, and the simple rules to follow.

I’ve spent years knee-deep in Lighthouse in my first few pagespeed years. I always assumed that one part was intentional design decision, but after 5 years I learned I was wrong.

This year, Google is hosting Google I/O Connect in Berlin. This is the follow-up of the main event in Mountain View USA. Google Experts and Developers from across Europe, Middle East and Africa will be joining to explore Googles latest products and solutions. with live sessions, hands-on activities, and demos. There’ll be plenty of time to network, too.

This blogpost contains links from my last slide and will be updated to also include the PDF.

Although not part of the set of Core Web Vitals, TTFB is an important page speed metric. However, it poses more challenges for e-commerce sites compared to other types of websites, static sites included. Nevertheless, what is considered a good TTFB for e-commerce?

This is a follow-up post where I elaborate on how to easily detect a broken to identify invalid HTML.

Watch out for invalid HTML elements in yourHTML head. A div, input or img can result in unexpected browser behaviour, slowing down page performance.

"Does anyone have a good hello world demo for a project with INP issues?"

Let's support my previous claims by actually researching the performance impact of using a JS and CSS-only solution for headline text balancing

New to INP or caring about web performance, and living in or nearby the south of The Netherlands? You're in luck. There will be an event next Thursday, where I will talk about INP.

The moment all performance -and maybe SEO- specialists have been waiting for has arrived: Google has announced the INP deadline!

Evenly and aesthetically distributing your text on available lines? Use `text-wrap: balance` instead of JavaScript and improve web performance & INP of your website.

It's a wrap! The organizers of the yearly performance.now() conference managed to raised the bar once again for next year's edition.

Before the performance.now() conference days started, I visited Google headquarters in Amsterdam and also gave a presentation on INP and the LoAF API during a performance meetup.

Here are ways to log the redirect time and TTFB. Just copy & paste it into Chrome's JS Console to see the complete waiting time (including redirect time) when clicking on your own Google + FB Ads, for example.

You quickly want to check for unnecessary redirects to prevent them from impacting your SEO and PageSpeed. But you don't want to use other tools? You can easily do it by using DevTools, in 3 simple steps.

Yesterday's big news was that X is delaying links to its competitors by up to 5 seconds. It was claimed to be resolved, but I can confirm that not only was it occurring before, but with a delay of 2.6 it is still occurring now. Let's dive in.

Whatever you do as a third party, there's an interesting nuance that we ran into with a Matomo implementation. The issue: the website was too quick.

INP will observe the latency of all click, tap, and keyboard interactions that occur throughout the lifespan of a user's visit to a page. The final INP value is the longest interaction observed, ignoring outliers. But what does that mean?

I've selected my most popular LinkedIn post of 2022. It might be convenient of you if you're not following me yet, or just didn't had the chance to read up on all of them.

Do you also just implement third party code without consideration? Here's a use case where it impacted user engagement and specifically the FCP metric by at least 445ms, based on a Webpagetest analysis.

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.

While users would actually see the actual link in the user interface (either their browser or the Twitter app), the actual redirect behaviour works with an extra step via t.co

You think it would be clear to everyone that the Tower of Pisa is shifted. However, it also depends on the point of view and angle. The same applies to CLS as well: different conditions will result in CLS happening at different moments. Let's discuss toolings you can use to track CLS.

HTTP/2 is already around since 2015. Heck, HTTP/3 even got standardized as of June 6th 2022. So why even bother talking about HTTP/1?

We all get that woff2 is smaller than woff, or ditching custom fonts comes with best performance. But what are considerations if you really want to use custom fonts?

If you're concerned about the loading experience of your custom fonts, you might have run into the WebFontLoader. A 10 year old library. Should you still use it today.

If optimizing was only as simple as adding a few attributes. But this time, it really is and it's even easier to use than image preloading.

So, FID is only tracking delay during first interaction and didn't come with real nuances per stack. But what about the new INP metric and WP, Magento or SPA's?

"Interaction to Next Paint", INP for short, measures the time between a user interaction (click, tab, type) and basically the visual feedback to a user. And it should be below 200ms.

Server side caching means that some form of caching is done server side. And from a pagespeed perspective, it makes most sense to do this for contents that tends to be dynamic. Let's dive into the basics of server side caching a bit more.

In general, people know that I'm not the one to ask which plugins to use for their stack. However, given the fact that I'm a pagespeed and performance enthousiast, I'm sometimes asked which plugins people should be using.

While two completely different things, there actually is a correlation between pagespeed and accessibility.

Even clients that are convinced they should work with me, still want to know how a collaboration and an auditing trajectory is going to look like. This article is giving background information.

We've all heard of the 'eliminate render blocking resources' recommendation in Lighthouse. But to understand why it is important to fix this, it first is convenient to know a few basic principles of browsers.

A platform can take a long time to generate a webpage. But when the content is cached, TTFB and users will benefit, but the first user accessing new contents will pay a penalty. How to prevent this and improve the cache hit ratio?

Rarely can you increase your PageSpeed with a single line of CSS. Today, though, I will share two separate CSS lines of code that will improve pagespeed and performance.

I've seen pagespeed audits where Google Analytics' Average Page Load Time was used to determine bad performing pages and claiming the webshop was missing revenue. However, pagespeed is more nuanced.

WordPress started a performance team to improve its Core Web Vitals scores. I read their pagespeed optimization spreadsheet and boy do I have an opinion regarding their performance backlog.

Google hasn't been sitting still. Both LCP and CLS have been seeing drastic changes already, so why not changing the FID metric?

I've been sharing charts of Core Web Vitals passing platforms recently, so here's the shared source of truth for the way websites are both built and experienced.

Wordpress recently wrote about the performance impact of jQuery, but it seems like they are choosing to not call out the real pagespeed bottleneck.

There is nothing wrong with the mindset of AMP. However, news publishers felt forced to start using Google's AMP HTML framework for their articles for SEO reasons while you could achieve same pagespeed results without AMP.

If you're looking for PageSpeed Insights, you now get redirected to their new testing environment: The PageSpeed Insights layout has changed as of today.

When doing pagespeed audits, there often is a common pitfall that I see happening across different webshops. If you're using Cloudflare, then this might help you out as well.

It's happening. Wordpress is finally going to focus on performance. But why now, and will it succeed?

You might not be aware yet, but chances are that the e-mail or social media campaigns and ads you're running, are impacting user experience.

You might have noticed that your LCP will often be worse than your FCP. This is quite common, as the header, hamburger menu or (inlined) SVG logo will be rendered sooner than the rest of the page. But what does it mean if your LCP and FCP are almost the same?

A/B testing is often used to come up with better headlines or layout, increasing conversion. However, even today A/B testing isn't always implemented in an optimal way, negatively impacting your business instead.

So there's that, it has been said. Your Lighthouse score doesn't matter. Let's nuance this a bit.

Reddit might not be the first platform you think of when talking about SEO or Core Web Vitals. However, this exact same question got asked on Reddit and led to a surprising reply.

Wether you're reading a LinkedIn or Twitter discussion, there still is confusion around lazyloading images. Especially when it comes to above the fold images, such as hero images. Let's deal with this for once and for all.

You're on stackoverflow or MDN docs and found a code snippet that should help pagespeed. Just copy + paste it and hope it works!

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.

Google Lighthouse has recently had an update. This may also have (negatively) influenced your scores. I briefly paid attention to it in a LinkedIn post, but in this blogpost I will go into it a bit more deeply.

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?

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..

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.

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 accessibility.

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.

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.

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).

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.

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.

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)!

Have you been to Magento Live in Amsterdam and did you speak the Google PageSpeed crew about your pagespeed score? I already heard some e-commerce owners, the Google PageSpeed crew might have given you some wrong insights, which I am going to answer instead.

Should you favor skeleton loading over spinner loading, and what would be the difference between building a PWA or server rendered website?

We all use JS, custom fonts, images and maybe even video's within our website or webshop. We can now reduce our load and speed up article- or product pages based on user preferences.

A better perceived performance and thus user experience, will result in higher conversion and thus revenue.

You want your e-commerce to use most supplier-efficient and cost friendly delivering process. At the same time, you want to keep calculations and thus memory outbursts to a minimum.

Before helping an e-commerce company with improving their pagespeed, sometimes I create a proof of concept first. By doing this, stakeholders will get a better grasp of what can be achieved in real life.
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.

You might want to publish your (new) website or webshop on the www-prefix of your domain. This will decrease network latency, when doing it the other way around for your images, making your online business even faster.

With which CMS do you have the greatest chance of a fast or slow website? And which (managed) hosting is best?

Last monday, I visited Wehkamp. They boosted the pagespeed of their productpages after taking part in a Google Speed Race and ending up second.

If you are a professional Web Performance Optimizer (WPO), or if you are simply someone who cares about online performance and pagespeed, chances are that you are doing these performance optimisations wrong.

The biggest challenge under the former PageSpeed Insights test has been completely annulled as the PageSpeed Insights uses the Lighthouse engine nowadays.