What to Expect on March 12, 2024
On this date, INP will officially replace FID across Google’s tools, including Google Search Console and PageSpeed Insights. FID-related metrics will be removed, and developers will find new documentation focusing on INP optimisation. This transition is designed to give a more accurate view of site responsiveness, ultimately benefiting user experience.
Why Improving INP Matters for Your Site
Case studies from companies like The Economic Times and redBus demonstrate that reducing interaction latency directly impacts engagement and business outcomes. By optimising for INP, your site can benefit from a faster, more responsive user experience, leading to better metrics in Core Web Vitals and potentially improving your search engine ranking.
Conclusion
With INP set to become a Core Web Vital, now is the time to review and optimise your site’s interactivity. Following best practices for INP can ensure your site remains competitive, providing a smooth and engaging user experience. For any questions about INP or Core Web Vitals, check out the Google Search Central announcement.
Interaction to Next Paint (INP)
A new era is among us – INP will replace First Input Delay (FID) as a Core Web Vital on March 12, 2024, signaling a major shift in how Google measures site interactivity. This update means that developers will need to focus on optimising INP to ensure a responsive and engaging user experience. Here’s what to know about this transition, and steps you can take to prepare.
What is INP and Why the Change?
INP captures the delay before a page visually updates in response to user interactions. Unlike FID, which only measures the time to the first response, INP provides a more holistic view of site responsiveness, tracking the entire interaction lifecycle. By adopting INP, Google aims to better represent real-world interactivity and help developers improve the responsiveness of their sites more effectively.
Preparing Your Website for INP
- Evaluate INP Performance: To see how your website performs on INP, use PageSpeed Insights or the Chrome User Experience Report (CrUX), which provide metrics on real user data. For sites already using a Real User Monitoring (RUM) provider, check with your vendor to see if they support INP tracking.
- Optimise Key Areas to Improve INP:
- Long Tasks on Main Thread: Identify and minimise JavaScript tasks that delay responses. Reducing these “long tasks” helps prevent interaction delays.
- Input Processing Delay: Shorten the time it takes for interactions to start processing by managing event listeners and script execution times.
- Reduce DOM Complexity: Large or complex DOMs can increase render time. Aim for a streamlined DOM structure and avoid frequent layout shifts or “layout thrashing.”
- Simplify CSS Selectors: CSS selectors, especially complex ones, can slow down the response to user interactions. Simplifying CSS can improve INP performance.
- Optimise Client-Side Rendering: Be cautious with client-rendered HTML, as it can delay interactivity if not optimised.
Table of Contents
Frequently Asked Questions
-
How is INP calculated?
Interaction to Next Paint (INP) is calculated by measuring the longest interaction delay on a webpage. It captures the time from when a user first interacts with the page (like clicking a button) to when the next visual change occurs on the screen. Google considers the 75th percentile of INP across all page loads to determine a site’s INP score, which ensures a stable, real-world assessment of user experience.
-
What is the difference between FID and INP?
-
How does INP affect SEO?
-
What is the meaning of INP?
-
What does INP stand for in Google?
-
What is INP in Google Search Console?
Digital thoughts, without the fluff.
Practical insights on sustainable design, SEO, and the future of the web.

