What Is INP and How Do You Fix It on WordPress, Magento and Laravel?
INP is now a Core Web Vital. Learn what Interaction to Next Paint measures, what causes a poor score and how to fix it on WordPress, Magento and Laravel.
Quick answer: INP (Interaction to Next Paint) is a Core Web Vital that measures how quickly a page responds when someone clicks, taps or types. A good INP is 200 milliseconds or less. To fix a poor INP, cut heavy JavaScript, break up long tasks and delay scripts that aren’t needed right away.
Your page loads fast. The PageSpeed score looks fine. But when a visitor taps “Add to cart” or opens the menu, nothing happens for a moment. That small delay is what INP measures, and it’s now part of how Google judges page experience.
INP replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024. The change caught many sites off guard, because a page that passed FID easily can still fail INP.
In this guide, we explain what INP is, why scores drop, how to measure it, and the practical fixes for WordPress, Magento and Laravel sites.
What Is INP and Why Did It Replace FID?
INP measures the delay between a user’s action, like a click, tap or key press, and the moment the page visibly updates. It looks at interactions across the whole visit and reports one of the slowest, so a single laggy button can pull the score down.
FID only measured the delay before the browser started handling the first interaction. It ignored how long the work took and every interaction after the first one. That’s why it made most sites look better than they felt.
The numbers show the gap clearly. When Google announced the change, about 93% of sites had a good FID on mobile, but only about 65% had a good INP.
INP score
Rating
What users feel
200 ms or less
Good
The page reacts almost instantly
200–500 ms
Needs improvement
A noticeable pause after clicks
Over 500 ms
Poor
The page feels stuck or broken
How Do Sites Score on INP Today?
The HTTP Archive’s 2025 Web Almanac, based on July 2025 data, found:
Metric
Desktop
Mobile
Good INP
97%
77%
Good LCP
74%
62%
Good CLS
72%
81%
Good Core Web Vitals overall
56%
48%
Two things stand out. INP is a much bigger problem on mobile than desktop, and fewer than half of mobile sites pass all three Core Web Vitals.
What Causes a Poor INP Score?
Almost every INP problem comes back to one thing: the browser’s main thread is busy when the user tries to interact. While the main thread is running JavaScript, it can’t respond to a click.
Each interaction has three parts, and a slowdown in any of them hurts INP:
Part of the interaction
What happens
Common cause of delay
Input delay
The browser waits to start handling the click
Long tasks already running on the main thread
Processing time
Event handlers run
Heavy or badly written JavaScript
Presentation delay
The browser updates the screen
Large DOM, complex layouts, big re-renders
The usual suspects on real websites:
- Too many third-party scripts: chat widgets, ad tags, analytics and tracking pixels all compete for the main thread.
- Long tasks: any JavaScript task over 50 ms blocks the page from responding.
- Large DOM size: thousands of elements make every update slower.
- Heavy themes and page builders: they often load scripts on every page, even where they aren’t used.
- Unoptimized event handlers: code that does too much work right after a click.
This is where a website speed optimization plugin helps most. Deferring and delaying non-critical scripts frees up the main thread, so the page can respond when users interact.
How Do You Measure INP on Your Website?
INP is a field metric, which means it’s based on real visitors using your site. That’s important, because a lab test with no clicks can’t show your real INP.
Tool
Data type
What it’s good for
PageSpeed Insights
Field + lab
Quick check of real-user INP for a URL or the whole site
Google Search Console (Core Web Vitals report)
Field
Groups of pages that fail INP across your site
Chrome DevTools (Performance panel)
Lab
Finding the exact long task behind a slow click
Lighthouse (Total Blocking Time)
Lab
A rough lab signal, since TBT often tracks with INP
A simple process:
- Open the Core Web Vitals report in Search Console and find page groups marked “INP issue.”
- Run one example URL through PageSpeed Insights to confirm the field INP score.
- Open that page in Chrome DevTools, record a session and click the slow elements.
- Look for long tasks in the main thread and note which script caused them.
Google reports Core Web Vitals at the 75th percentile, so your INP score reflects the experience of most visitors, not just your fastest ones.
How Do You Fix INP on WordPress, Magento and Laravel?
The basic idea is the same on every platform: run less JavaScript, run it later, and keep each task short. Here’s how that looks in practice.
Fixing INP on WordPress
WordPress sites usually struggle with INP because of plugins and page builders that load scripts everywhere.
- Remove plugins you don’t use and check which ones load scripts on every page.
- Delay third-party scripts like chat, ads and tracking until the user interacts.
- Defer non-critical JavaScript so it doesn’t block the main thread during load.
- Reduce DOM size by simplifying heavy page builder layouts.
A wordpress speed optimization plugin can handle JavaScript deferral, lazy loading and script exclusions without editing theme code.
Fixing INP on Magento 2
Magento stores often have large JavaScript bundles and heavy product, filter and checkout pages.
- Review and remove unused third-party extensions.
- Avoid loading every RequireJS module on every page.
- Simplify layered navigation and mini-cart interactions, which are common slow spots.
- Delay review widgets, live chat and marketing tags.
To automate much of this, look at our tools for magento 2 speed optimization.
Fixing INP on Laravel
Laravel apps often use front-end frameworks or Livewire, so INP issues tend to come from client-side rendering.
- Split large JavaScript bundles so each page loads only what it needs.
- Avoid heavy re-renders after a click. Update only the parts of the page that change.
- Move expensive work off the main thread or into background jobs on the server.
- Keep server responses fast, so updates after an interaction appear quickly.
Our laravel performance optimization package covers asset optimization and script loading for Laravel sites.
Fix
WordPress
Magento 2
Laravel
Delay third-party scripts
Yes
Yes
Yes
Defer non-critical JS
Yes
Yes
Yes
Reduce DOM size
Page builders
Category and product pages
Large components
Split JS bundles
Less common
RequireJS bundles
Vite or Mix bundles
Remove unused add-ons
Plugins
Extensions
Packages
Is Fixing INP Worth the Effort?
Yes. INP is the Core Web Vital that comes closest to what users actually feel. A page can load quickly and still frustrate people if buttons, menus and forms lag after every tap. That frustration shows up in bounce rates, abandoned carts and lost leads.
Start with measurement in Search Console and PageSpeed Insights, find the scripts that block the main thread, and fix the biggest offenders first. On most sites, delaying third-party scripts and deferring non-critical JavaScript gives the quickest improvement.
Key Takeaways
- INP replaced FID as a Core Web Vital on March 12, 2024.
- A good INP is 200 ms or less. Over 500 ms is poor.
- In 2025, 77% of websites had a good INP on mobile, compared with 97% on desktop.
- Most INP problems come from a busy main thread caused by heavy JavaScript.
- Delaying third-party scripts, deferring non-critical JavaScript and reducing DOM size are the most common fixes.
Frequently Asked Questions
1. What is INP in Core Web Vitals? INP, or Interaction to Next Paint, measures how quickly a page visibly responds after a user clicks, taps or presses a key.
2. What is a good INP score? A good INP is 200 milliseconds or less. Between 200 and 500 ms needs improvement, and over 500 ms is poor.
3. When did INP replace FID? INP officially replaced First Input Delay as a Core Web Vital on March 12, 2024.
4. Why is my INP poor when my page loads fast? Load speed and responsiveness are different. A page can load quickly but still have heavy JavaScript running that delays clicks and taps.
5. Does INP affect SEO? INP is one of Google’s Core Web Vitals, which are part of how Google evaluates page experience.
6. Can Lighthouse measure INP? Not directly, because a lab test has no real user interactions. Total Blocking Time in Lighthouse is a useful lab signal that often tracks with INP.
7. Where can I check my site’s INP? Use PageSpeed Insights for a single URL and the Core Web Vitals report in Google Search Console for your whole site.
8. What is the fastest way to improve INP? Delay third-party scripts, defer non-critical JavaScript and break long tasks into smaller ones.
9. Do WordPress plugins hurt INP? They can. Plugins and page builders that load scripts on every page add work to the main thread and slow down interactions.
10. Is INP worse on mobile? Yes. In 2025, 77% of websites had a good INP on mobile, compared with 97% on desktop, according to the HTTP Archive Web Almanac.
0 comments
Log in to leave a comment.
Be the first to comment.