
Performance (INP) impact from OneTrust and other CMPs
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.
Can't get enough? I'm regularly sharing snack bite tips and advice on LinkedIn as well.

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.

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

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

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.

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?

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.

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