How to fix cwv inp on Wix

Steps for Wix

1. Open the Wix Editor. In the left panel, go to Add Apps → Manage Apps and remove any app whose functionality you no longer actively use — every Wix app can add JavaScript weight.
2. In the Wix Editor, select any embedded HTML/custom code widgets (via Settings → Custom Code or via Velo) and check whether their scripts can be moved to load 'After body start' or set to load on interaction rather than on page load.
3. Go to Settings → Custom Code (in the Dashboard). For third-party scripts (chat, analytics, pixels), set the 'Load' timing to 'Load when page is ready' or 'Load after user interaction' if that option is available for your script.
4. In Velo (Wix's dev environment), review any `$w.onReady()` code that runs large synchronous operations. Break heavy logic into smaller async steps using `async/await` and `setTimeout` to avoid blocking the main thread.
5. Use PageSpeed Insights with your live Wix URL and the Chrome DevTools Performance panel to identify which specific interactions have the highest INP.

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.