Interaction to Next Paint (INP) becomes a Core Web Vital on March 12. Start making your websites more responsive to user input today.
What is FID?
First Input Delay (FID), measures responsiveness. It measures how long it takes the browser to begin processing the first user interaction on a page.
But, FID is limited...
FID is just measured for taps and key presses, which means that it only considers the very first occurrence. In particular, it measures the difference between the time when the user interacts with the device and the time when the browser is actually able to begin processing event handlers. FID does not include the time spent running the event handlers, nor any work done by the browser afterwards to update the screen. It measures the amount of time the main thread was busy before having the chance to handle an input. This blocking time is usually caused by long JavaScript tasks, as these can’t just be stopped at any time, so the current task must complete before the browser can start processing the input.
Why INP is introduced?
INP aims to capture a more holistic picture of the overall responsiveness of a page throughout its lifetime by measuring end-to-end latency.
What does this mean for Google Search Console?
To help site owners and developers to take the necessary steps and evaluate their pages for the new metric, Search Console will include INP in the Core Web Vitals report later this year. When INP replaces FID on March 12, 2024, the Search Console report will stop showing FID metrics and use INP as the new metric for responsiveness.
What does this mean for site owners?
Prioritizing Core Web Vitals is crucial for website owners, as it significantly impacts both search engine optimization (SEO) and user experience (UX). By focusing on optimizing Core Web Vitals, you can improve your website’s visibility in search engines and create a more user-friendly experience, ultimately contributing to the overall success of your website.
