How to fix cwv inp on Elementor

Steps for Elementor

1. In the WordPress dashboard, go to Elementor → Settings → Performance tab. Enable the 'Improved Asset Loading' (formerly Improved CSS Loading) option and set 'Load Elementor CSS Print Method' to 'Internal Embedding' to reduce render-blocking requests that contribute to long main-thread tasks on interaction.
2. Still in Elementor → Settings → Performance, enable 'Lazy Load Background Images' and turn OFF any Elementor features you are not using (e.g. Motions Effects, Floating Effects, Scroll Snap) under the 'Features' tab — each unused feature removes a JavaScript module that competes for the main thread during user interactions.
3. Go to Elementor → Settings → Experiments and disable any experimental or beta widgets/features that are inactive on your site (e.g. Nested Elements, Container Grid) — experimental code runs JavaScript listeners on every interaction and can inflate INP.
4. Install or configure a WordPress performance plugin (e.g. WP Rocket, LiteSpeed Cache, or Perfmatters) and enable 'Delay JavaScript Execution' (sometimes called 'defer JS on user interaction'). Add Elementor's non-critical scripts (e.g. elementor-frontend.js animations, motion effects) to the delay list so they do not block the main thread before the first user interaction is processed.
5. In your performance plugin's exclusion list, ensure that any Elementor widget scripts tied to interactive elements (forms, accordions, tabs, sliders) are NOT delayed — only delay purely visual/animation scripts. This prevents INP regressions on click/tap targets.
6. After saving all settings, clear all caches (Elementor → Tools → Regenerate Files & Data, then your caching plugin's cache), then re-test INP in Chrome DevTools (Performance panel → Interactions track) or PageSpeed Insights to confirm all interaction delays are under 200 ms.

What is cwv inp?

Interaction to Next Paint (INP) measures how quickly your page visually responds after a visitor taps a button, opens a menu, or types in a search box — from the moment they interact to the moment the screen actually updates. Google considers anything under 200 ms "good," 200–500 ms "needs improvement," and over 500 ms "poor." INP is now a Core Web Vital, meaning it is part of Google's official page-experience signal that feeds directly into rankings. A high INP score almost always means the browser's main thread is busy running JavaScript and simply cannot get around to updating what the visitor sees for a frustrating fraction of a second (or longer).

Google uses Core Web Vitals — including INP — as a ranking signal, so a poor INP score can quietly suppress your pages in search results compared to faster competitors. Beyond rankings, a sluggish-feeling page directly hurts conversions: studies consistently show that every 100 ms of added interaction delay reduces add-to-cart and checkout completion rates. On mobile, where CPU speed is limited and networks are slower, a 500–800 ms INP is especially damaging because mobile shoppers are the majority of ecommerce traffic. There is also an accessibility dimension — users who rely on keyboard navigation or assistive technology are disproportionately harmed by delayed visual feedback, which can create a frustrating or unusable experience.

See the complete Cwv inp guide for every platform and the full background.