Free tools Windows power users keep installed
One-click scans. No signup required.
Interaction to Next Paint (INP) is the Core Web Vital that measures how quickly a page responds visually to clicks, taps, and key presses during a visit. A good INP is 200 milliseconds or less at the 75th percentile, evaluated separately for mobile and desktop. In WordPress, improving INP means finding the interaction that is slow in real use, identifying whether JavaScript or rendering is responsible, and then fixing that specific theme, plugin, page-builder, or third-party code.
What INP measures
INP follows qualifying interactions throughout a page visit and reports the slowest observed interaction after some extreme outliers are excluded. It replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024. Unlike FID, which considered only the first interaction, INP evaluates responsiveness across the visit.
Google’s recommended model divides an interaction into three stages:
- Input delay: the time between the user’s action and the start of its event callbacks. A busy main thread can cause this delay.
- Processing duration: the time required for the interaction’s event handlers and related callbacks to finish.
- Presentation delay: the time from callback completion until the browser presents the next frame showing the result.
The total latency is the combination of these stages. A slow menu, filter, form, or add-to-cart control may therefore be delayed before its code starts, slowed by the code itself, or held up while the browser performs style, layout, paint, or other rendering work.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat is a good INP score?
| INP result | Interpretation |
|---|---|
| 200 ms or less | Good responsiveness |
| More than 200 ms through 500 ms | Needs improvement |
| More than 500 ms | Poor responsiveness |
Assess the 75th percentile of page loads, with mobile and desktop reported separately. This percentile asks whether most visitors receive a responsive experience; one fast laboratory run or one slow visit is not enough to characterize a page.
How to check INP on a WordPress site
Start with field data
Open the page in PageSpeed Insights. When the page or origin has enough eligible Chrome User Experience Report (CrUX) data, the report shows real-user INP and its mobile or desktop assessment. Field data is the right starting point because it reflects visitors’ devices, networks, browsers, and behavior.
CrUX usually tells you whether responsiveness is healthy, but it may not identify the exact interaction or element that produced the slow result. A real-user monitoring (RUM) service, or a carefully implemented first-party measurement system, can capture the affected URL, interaction, and timing details needed for diagnosis.
Reproduce important interactions in a lab
Use browser performance tools to record representative flows on the affected template. Test while the page is loading and again after it has settled. Include:
- navigation menus and mobile drawers
- site search and autocomplete
- filters, sorting, and accordions
- contact, login, and checkout forms
- add-to-cart, quantity, and variation controls
- cookie banners, chat widgets, video embeds, and other third-party UI
Performance recordings expose long main-thread tasks and help separate input delay, callback processing, and presentation delay. An interaction inside an iframe can contribute to INP, so determine which frame owns the slow control before changing WordPress code.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A WordPress workflow for improving INP
1. Identify the responsible page and interaction
Segment field results by device type and page template. A poor result on a product page’s variation selector requires a different fix from a poor result on the global navigation. Record the exact control, user action, and resulting visual change that are slow.
2. Inspect the actual WordPress output
Review the theme, child theme, page-builder output, plugin assets, analytics, advertising tags, chat tools, embeds, and custom scripts loaded on the affected page. Use the performance recording and the page source or script list to attribute the delay before disabling or replacing anything. WordPress application of these browser-level techniques is a technical inference; no universal WordPress plugin or setting is established as an INP solution.
3. Reduce input delay
Keep the main thread available when users are likely to interact. Remove unnecessary scripts from the affected template, defer nonessential initialization, and break large synchronous tasks into smaller units where that preserves behavior. A script that runs during page load can make a later tap wait even if the tap’s own handler is short.
4. Reduce event-processing time
Keep interaction callbacks narrowly focused. Move analytics, logging, recalculation, and other nonessential work out of the immediate response path when possible. Avoid repeating expensive queries or computations for every keystroke; use appropriate debouncing or incremental work without making controls inaccessible or visibly stale.
5. Reduce presentation delay
Limit the amount of HTML a click or key press creates or updates. Review code that forces repeated style calculations or layout, and avoid broad DOM updates when a smaller change will produce the same result. Google’s guidance also identifies content-visibility as a possible way to reduce rendering work in suitable cases, but it requires careful application so hidden content remains discoverable and usable.
6. Retest, deploy, and watch field data
After each meaningful change, repeat the same interaction recording under comparable conditions and check that functionality, keyboard access, focus behavior, and screen-reader output still work. A better synthetic trace does not prove that real-user INP improved. Continue monitoring field data after deployment and compare the relevant mobile and desktop percentiles.
Quick Recap
Diagnosing a poor interaction
| What the trace shows | Likely focus | WordPress examples |
|---|---|---|
| Long wait before the callback starts | Input delay and main-thread contention | Large theme or page-builder bundles, eager analytics, ads, or initialization scripts |
| Callback occupies the main thread | Processing duration | Heavy filtering, repeated DOM work, synchronous calculations, or oversized event handlers |
| Callback ends but the next frame is late | Presentation delay | Large DOM mutations, expensive style or layout work, and broad re-rendering |
| Slow control belongs to an embedded frame | Iframe-owned work | Checkout, video, chat, advertising, or other third-party embeds |
Common mistakes to avoid
- Chasing a PageSpeed score: a higher synthetic score is not evidence that real visitors’ INP improved.
- Installing several “speed” plugins without a diagnosis: extra optimization layers can conflict, alter interaction behavior, or leave the responsible script untouched.
- Testing only the first click: INP includes interactions throughout the visit, including controls used after the page has settled.
- Ignoring mobile: slower mobile hardware often exposes main-thread and rendering costs that desktop testing hides.
- Removing a feature blindly: disabling a plugin or script may improve a trace while breaking checkout, accessibility, consent, or other required behavior.
Practical verification checklist
- Field INP is reviewed at the 75th percentile for mobile and desktop.
- The affected URL or template and the slow interaction are recorded.
- The performance trace identifies input delay, processing duration, or presentation delay.
- The responsible theme, plugin, page-builder component, or third-party frame is attributed.
- The change is tested during loading and after the page settles.
- Keyboard, touch, focus, screen-reader, consent, and transaction behavior remain correct.
- Field data is monitored after release rather than relying on one lab result.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches
