Google has released a new report in Google Search Console to see how you’re doing with INP, Interaction to Next Paint and Core Web Vital metrics. As a reminder, Interaction to Next Paint (INP) will replace First Input Delay (FID) as the metric for Core Web Vitals in March 2024.
Google released this new report today to enable site owners to prepare for the coming change.
How is the report? Here is a screenshot of the report:
INP (Interaction to Next Paint) is a new metric that will replace FID (First Input Delay) as Core Web Vital in March 2024. “Until then, INP is not part of Core Web Vitals. Search Console reports data from INP to help you prepare,” Google explained.
How to access the report. The report can be accessed within Search Console by clicking this link and select a property.
More details Google wrote in their help documentation:
INP (interaction with the following painting): metric that assesses a page’s overall responsiveness to user interactions by looking at how long it takes the page to respond to all click, tap, and keyboard interactions that occur over the lifetime of the visit from a user to a page. The final INP value is the longest interaction observed, ignoring outliers.
INP group shown in the report means that 75% of the hits to a URL in that group had that value or better.
Here are the performance ranges for each state; Note that the INP range says that to be marked as “good” you need to be under 200ms.
What is the interaction with Next Paint? INP is a metric that uses data from the Event Timing API. It evaluates the responsiveness of a web page.
An interaction that causes a page to become unresponsive results in a poor user experience, Google said. INP looks at the latency of all interactions a user has made with the page and reports a single value that all (or nearly all) interactions were below.
Google provided the following example of what a poor versus good response looks like:
On the left, long tasks prevent the opening of the accordion. This causes the user to click multiple times, thinking the experience is broken. When the main thread catches up, it processes delayed inputs, causing the accordion to open and close unexpectedly.
Impact of rankings. Google reiterated that Core Web Vitals does not guarantee a good ranking in Google Search, wrote Martin Splitt, a developer relations engineer at Google.
“A great page experience involves more than just Core Web Vitals. Good statistics from the Core Web Vitals report in Search Console or third-party Core Web Vitals reports do not guarantee a good ranking,” according to Splitt.
A good on-page experience is part of Google’s overall core ranking system. Core Web Vitals, while it may not be a direct ranking signal, is a way to try to understand if you’re getting a good page experience.
However, Google uses other signals as part of its core ranking system to determine what makes a good page experience, outside of Core Web Vitals.
“There are many aspects of the page experience, including some listed here this page” said Danny Sullivan, Google Search Link, on Search Engine Land. “While not all aspects can be directly used to inform ranking, they generally align with search ranking success and deserve attention.”
Why we care So now you can see how Google will judge your pages based on this new core INP metric. You have several months to prepare before it goes live in March 2024. Until then, I wouldn’t freak out about this metric, it’ll probably be a very minor ranking signal, if any. But it’s another performance metric that you can use to try to make your site better for users, so show it to your developers and see if they can improve it, ie if it’s not good now.
Here’s what a good result looks like on Google:
[ad_2]
Source link
