Google has announced that the new Interaction with Next Paint (INP) will become one of the three Core Web Vitals metrics on March 12, 2024. Replaces the old one First input delay metric.
This is the biggest change to web vitals since Google first introduced them as a ranking factor in 2021.
What is the interaction with Next Paint?
The three Core Web Vitals metrics each measure a different aspect of the experience users have on your website. INP evaluates how quickly your website responds to user interactions.
For example, if a visitor clicks a button on your website and the page’s updated content takes a second to display, this represents a poor user experience.
Interaction with Next Paint measures how much time passes between user interaction and the next time the browser can refresh the content on the screen. The more CPU processing required to handle the interaction and display the new content, the worse the INP score.
Does engagement with the following affect Google rankings?
Google has confirmed that the Core Web Vitals are a ranking factor. This means that if your site performs worse in the INP score, it may rank higher than competitors that do well in all three vital web metrics.
For a good score, the INP must be less than 200 milliseconds. A delay of more than 500 milliseconds is considered poor. Your SEO is gradually affected as the INP worsens between the Good and Poor thresholds.
How does Google know how quickly your website responds to user interactions? This data is collected from actual Chrome users as part of the Chrome User Experience Report (CrUX).
How to test interaction with Next Paint on your website
Want to find out how your website is doing with the INP metric and other web vitals? run to Core Web Vitals free trial on your website is a quick way to check. Just enter the URL of a page and wait for the test result.
Actual user interaction data with Next Paint can be found at Vital Web tab The 25-week trend lets you know if the page is getting better or worse over time.
The data shown here comes from Google’s CrUX report.
For a broader view of the different groups of pages on your website, you can also check Core Web Vitals tab in Google Search Console. Here you will see how many pages are affected by INP issues or otherwise not pass the Core Web Vitals assessment.
Unfortunately, the data provided by Google is not very nuanced, and due to the page grouping mechanism, you may not be able to tell which specific pages are affected by slow interaction with the next Paint.
Google CrUX data is also aggregated for 28 days. This means you will have to wait several weeks to see the impact of the optimizations.
For a more detailed view, a dedicated real user Core Web Vitals monitoring tool how DebugBear can help. This way, you get detailed Core Web Vitals across your entire website, updated as soon as a change is made.
How to speed up interactions and improve INP?
To improve INP scores on your website, you need to know what CPU processing is involved in a user interaction. INP can be divided into three components:
Input Lag: Background tasks that prevent the browser from handling an interaction until the tasks have completed Processing Time: Running code that handles user interaction and schedules updates to the user interface Delay presentation: After scheduled UI updates, the browser must update the page layout and present the new content
The performance tab in Chrome DevTools it shows how long page interactions took and what was responsible for CPU processing.
The data in DevTools Performance Tab it can be hard to read, so you’ll usually want a developer involved. But it provides an explanation for every millisecond the browser spends while handling the event.
For example, you may find that:
Third-party code is running in the background and slowing down interactions. The JavaScript code that your website executes in response to an interaction needs to be optimized. You can schedule CPU tasks more efficiently to reduce the amount of time interactions are blocked.
Real user monitoring with DebugBear it will show you which INP component contributes the most to your website’s poor response.
You will also often find that interactions take longer during the initial loading process of the website. This is because when a page starts to load, many small tasks run in the background to set up the page, for example loading ads or initializing a form or chat widget.
DebugBear shows a breakdown of the speed of interactions at different stages and how often interactions occur in those time periods (indicated by the height of the bar).
If your website supports the Long Animation Frames APIyou may also see specific JavaScript scripts and functions that cause slow interactions between your visitors.
How do I know which page interactions are affected by a slow INP?
If you want to optimize your code and test the interactions on your website, you need to know which elements users interact with most often on your website and which interactions tend to cause a slow INP.
This is not data you can get from Google’s CrUX reports, but from a dedicated Core Web Vitals monitoring tool like DebugBear will collect this information for you.
You can filter data by page, device type, and many other factors to better understand how visitors experience your website. DebugBear reports can give you specific advice on how to improve your interaction with Next Paint.
How to control interaction with Next Paint and other Core Web Vitals
A real user monitoring (RUM) solution can help you prepare for the new Interaction to Next Paint metric and help you stay on top of your vital life base over time.
Try DebugBear with one 14 day free trial. Continuously measure your vital web data and see which pages will benefit most from optimizations.
Simply install the DebugBear analysis snippet to learn about your visitor experiences. Avoid the 28-day delay that comes with Google’s vital web data and get detailed reports that you can use to provide a better website experience and rank higher on Google.
[ad_2]
Source link
