Web Development · · 2 min read
INP Is Now a Core Web Vital: Is Your Website Responsive Enough?
Since 12 March 2024, Interaction to Next Paint (INP) has replaced First Input Delay in Google's Core Web Vitals. Here's what it measures and how to fix a slow-feeling site.
In short:
- On 12 March 2024, INP (Interaction to Next Paint) replaced FID as Google’s Core Web Vital for responsiveness.
- INP measures how fast your page visibly reacts when someone taps, clicks or types, across the whole visit.
- Good INP is 200 milliseconds or less. Heavy themes, page builders and too many apps are the usual problems.
A few months ago, Google changed one of the three Core Web Vitals, the metrics it uses to judge page experience. Interaction to Next Paint (INP) officially replaced First Input Delay (FID) on 12 March 2024. Search Console reports now show INP instead of FID.
Many site owners haven’t noticed, but their visitors have. INP measures something every shopper feels: tapping “Add to cart” and waiting for something to happen.
What INP measures
FID only measured the delay before the browser started handling the first interaction on a page. INP looks at all clicks, taps and key presses during a visit and reports the slowest one (with outliers ignored), measuring until the screen actually updates.
- Good: 200 ms or less
- Needs improvement: 200–500 ms
- Poor: over 500 ms
Google assesses this at the 75th percentile of visits, split between mobile and desktop.
Why Pakistani sites often struggle
Most visitors in Pakistan browse on mid-range Android phones. These phones are much slower at running JavaScript than the laptop your developer tests on. A site that feels fine in the office can feel sluggish on a Rs 40,000 phone.
Common causes we find:
- Heavy page builders and themes loading scripts on every page.
- Too many Shopify apps or WordPress plugins: reviews, popups, chat widgets, trackers.
- Large sliders and animations on the homepage.
- Third-party scripts (chat, heatmaps, multiple pixels) loading before the page is usable.
How to improve INP
- Check your data. Look at the Core Web Vitals report in Search Console and test key pages in PageSpeed Insights, which shows real-user INP where enough data exists.
- Remove what you don’t use. Every unused app, plugin and tracking script is a cost.
- Delay non-essential scripts like chat widgets until after the page loads or the user scrolls.
- Simplify interactive elements. Menus, filters and add-to-cart buttons should do the minimum work needed before showing feedback.
- Show instant feedback. A button that changes state immediately feels fast even when the server takes a moment.
Does it affect rankings?
Core Web Vitals are part of Google’s page experience signals, but content relevance matters far more. Fix INP mainly because it affects sales: a slow-feeling store loses buyers at every tap.
PeachTag Team
Led by Zain Ismail, 11+ years in performance marketing. Need help with this? Talk to us.
