\n\t\t\t\t

\n\t\t\t\t\t

\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t

Those involved in optimization in terms of Core Web Vitals<\/a><\/strong>, the decisive elements of a Web site in terms of the user experience on the Web page, know that innovations are always just around the corner.
\nLike, for example,Interaction to Next Paint (INP)<\/strong>.
\nThat is, a central metric that allows you to evaluate the responsiveness of the resource by identifying the latency of interactions throughout the lifecycle of the web page. <\/p>\n

So we can say this: having a low INP<\/strong> means ensuring a good ability to interact with the resource in<\/strong> its entirety, not just in a specific area as the above-the-fold might be.
\nAs well as the Cumulative Layout Shift<\/a><\/strong>, the INP is also about the entire experience. <\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t
What is Interaction to Next Paint (INP)?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
The Interaction to Next Paint metric measures the moment when a user interacts with a page<\/strong> (e.g., clicking a button) and the moment when the browser can display changed pixels<\/strong> on the screen.
\nThis metric is distinguished by its ability to capture the essence of a site’sinteractivity<\/strong>, going beyond simple loading speed<\/span>: because of its characteristics, it takes into account the complexity and variability of human interactions, providing developers with a more accurate tool for evaluating and optimizing the experience provided by site pages. <\/p>\n
This falls squarely within the goals of the Core Web Vitals program, which is the set of specific metrics aimed at evaluating the quality of user experience on a web page.
\nThese indicators were selected and introduced by Google to measure critical dimensions of the user experience-loading, visual stability, and precisely interactivity-with the intent of providing objective and unified metrics to evaluate the performance of a website from the end user’s point of view, and which are thus essential to the overall health of a web page. <\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
INP replaces First Input Delay<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
What is the difference with FID?<\/strong> Aren’t we talking about the same thing?
\nNo because the INP considers all interactions<\/strong> on the page, the First Input Delay<\/strong> considers only the first one.
\nFID only<\/strong> measures the input delay of the first interaction<\/strong>, it does not consider anything else. <\/p>\n
Such as the time it takes to execute events in a given section of the site or the delay in frame submission.
\nIn summary,INP is a superior and more accurate metric<\/span>.
\nProbably also for this reason, in the Core Update Google decided to replace First Input Delay with Interaction To Next Paint<\/strong> permanently from March 12, 2024<\/strong>. <\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t $\"\"$ \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
What is a good INP score?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
To ensure user experiences with good responsiveness a significant threshold to consider is 75 percent of observed page load times in the field, split between mobile and desktop devices:<\/p>\n
\n
An INP value of less than 20ms<\/strong> indicates that your page has excellent<\/strong> responsiveness.<\/li>\n
An INP value between 200 and 50ms<\/strong> indicates that the responsiveness of your page can be improved<\/strong>.<\/li>\n
An INP value greater than 500ms<\/strong> indicates that your page has insufficient<\/strong> responsiveness.<\/li>\n<\/ul>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t $\"\"$ \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
How does the cookie banner affect INP?
Why choose Iubenda?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
One of the key correlations is with JavaScript<\/strong>.
\nOptimizing INP requires identifying and reducing third-party JS, deferring code that does not need to be loaded in advance, reducing unnecessary code, and prioritizing elements and features that users will most likely want to interact with not immediately. <\/p>\n
To all this we obviously add a good performing hosting (we at f.technology have long relied on the unparalleled performance of Kinsta!<\/a><\/strong>).<\/p>\n
Keeping in mind that it is mandatory, according to the regulations introduced by the GDPR, to display on our websites a Cookie Banner that complies with several technical specifications (prior cookie blocking and granular consent to name a few), it is obvious that a cookie banner that is not optimized greatly affects our value of INP!<\/strong><\/p>\n
Consequently, it is beve to rely on a tool that takes into account this new metric and is properly updated: our partner Iubenda<\/strong><\/a>, in this regard, demonstrates the excellence of its service by developing a cookie banner perfectly optimized with the INP, proving to be the fastest tool on the market!<\/strong><\/a> <\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t \n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t