INP Core Web Vitals : a site can achieve a good overall score score while still seeming slow if its interactions, JavaScript, or third-party scripts delay the visible response to the user.
Why a good score Core Web Vitals does not always guarantee a feeling of speed
A satisfactory PageSpeed or Lighthouse score does not tell the whole story. It may indicate that the page loads correctly in a test scenario, alors users experience delays when clicking, tapping, or lors opening a menu.
This is precisely where INP Core Web Vitals becomes decisive. Interaction to Next Paint measures the delay between a user action and the visible update of the interface, which much better reflects a modern site’s real responsiveness.
Imagine an SME with a showcase site that loads quickly, but whose “Request a quote” button takes a second to respond on mobile. The visitor does not look at the technical score: they feel friction, hesitate, and sometimes leave the page.
At DualMedia, this type of diagnosis often comes up during web performance audits, especially on WordPress sites, e-commerce sites, or business applications rich in JavaScript. User experience is rarely determined by a single metric, but by the full sequence between loading, stability, and interaction.
Understanding the three Core Web Vitals metrics: LCP, INP, and CLS
Core Web Vitals are the indicators used by Google to evaluate the technical quality of the user experience. They do not replace content, autority, or search intent, but they can make the difference between two sites of equivalent quality.
Since March 2024, INP has replaced FID. This change is imporant, because FID measured only the first interaction, while INP observes responsiveness throughout the session.
| Metric | What it measures | Good score | To impore | Poor score |
|---|---|---|---|---|
| LCP | Display time of the largest visible element | Less than 2.5 seconds | Between 2.5 s and 4 s | More than 4 s |
| INP | Responsiveness after user interactions | Less than 200 ms | Between 200 ms and 500 ms | More than 500 ms |
| CLS | Visual stability of the page | Less than 0.1 | Between 0.1 and 0.25 | Greater than 0.25 |
LCP indicates whether the main content arrives quickly. CLS checks that the page does not shift unexpectedly. INP, on the other hand, shows whether the site responds immediately when the user acts.
To go deeper into the overall logic behind these signals, the dedicated guide to the Core Web Vitals makes it easier to understand their impact on SEO and user experience.
Why the Web Vitals INP reveals invisible loading delays
Web Vitals INP does not just measure whether a page displays quickly. It mainly measures the browser's ability to process an interaction and display a visual response without a perceptible delay.
A site can therefore have a correct LCP, a stable layout, and yet still feel heavy. This often happens on rich interfaces: catalog filters, complex menus, dynamic forms, configurators, dashboard tables, or checkout funnels.
The most common cause is JavaScript that monopolizes the browser's main thread for too long. As long as a heavy task is running, the user's click waits its turn, even if the page already seemed loaded.
A good technical metric can hide a poor user moment. Performance therefore does not stop when the page arrives: it continues throughout the entire experience.
Common causes of poor INP
Interaction delays rarely come from a single file. They often result from a stack of scripts, libraries, marketing tags, and poorly optimized components.
- Long JavaScript tasks that block the main thread.
- Too many third-party scripts, such as chat widgets, ad pixels, heatmaps, or social widgets.
- Event listeners that perform too much processing after a click.
- A front-end framework loaded all at once instead of being split up as needed.
- Animations or transitions that place too much load on the browser on mobile.
The classic trap is to optimize only images and cache. These actions often improve loading, but they do not always fix responsiveness after interaction.
How to improve INP without breaking the user experience
Improving INP requires a methodical approach. The goal is not to remove all JavaScript, but to make it smarter, more progressive, and better prioritized.
The essential scripts for the initial display must remain under control. Secondary processes, on the other hand, can be deferred, split up, or loaded only when the user truly needs them.
| Technical action | Expected effect | Recommended use case |
|---|---|---|
| Use defer | Loads scripts without blocking HTML parsing | Scripts dependent on the DOM or other scripts |
| Use async | Runs the script as soon as it is ready | Independent scripts such as certain analytics tools |
| Split the JavaScript | Reduces the initial load | Web applications, dashboards, e-commerce interfaces |
| Delay third-party scripts | Frees up the main thread | Chat, tracking, non-critical marketing widgets |
| Optimize events | Reduces the delay after a click or tap | Menus, filters, forms, action buttons |
In a real-world project, a mobile menu that is slow to open may be caused by a simple click handler that is too heavy. By moving heavy calculations away from the immediate interaction, the interface becomes smooth again without changing the design.
A web agency and mobile like DualMedia analyzes these points both on the code side, UX and conversion. The goal is not just to get a green metric, but to provide an immediate sense of responsiveness on the devices actually used by visitors.
The role of LCP in the perception of a fast site
LCP measures the time needed to display the main element visible in the viewport. This is often a hero image, a banner, a large heading, or a central editorial block.
If this element arrives too late, the visitor immediately gets the impression that the site is slow. Even with a good INP afterward, the first impression may already be damaged.
The most common causes are well known: a server that is too slow, an image that is too heavy, render-blocking CSS, non-critical JavaScript loaded too early, or lazy loading mistakenly applied to the main image. Lazy loading is useful for images lower on the page, but it becomes counterproductive on the LCP element.
To improve LCP, you need to prioritize what is visible above the fold. A CDN, WebP or AVIF images, targeted preload, and well-managed critical CSS can produce very noticeable gains.
Example of priority on a main image
A hero image should not wait behind secondary scripts. It can be preloaded in the head, then loaded with precise dimensions and high priority.
The principle remains simple: do not preload everything. If all resources become priorities, nothing truly is, and the browser loses the benefit of scheduling.
CLS and the micro-frustrations that create a sense of slowness
CLS measures unexpected layout shifts. It is not slowness in the strict sense, but the perceived effect can be similar: the site seems unstable, imprecise, and unreliable.
The scenario is familiar: a user is about to click a button, a banner appears, the content moves down, and the click lands in the wrong place. That small frustration is enough to erode trust.
Images without width or height, web fonts loaded poorly, dynamically injected ads, and notifications placed above the content are common causes. The browser needs to reserve space before resources arrive.
The fix often relies on simple steps: define width and height, use aspect-ratio, preload important fonts, apply font-display: swap, and reserve containers for dynamic elements.
Measuring INP with the right tools
A reliable audit combines lab data and field data. The first helps reproduce issues; the second shows what users actually experience.
PageSpeed Insights provides an initial useful reading because it combines technical recommendations with real-world data when a sample is available. Lighthouse, built into Chrome DevTools, remains valuable during development, but it does not replace real mobile traffic.
Google Search Console lets you track URL groups affected by Core Web Vitals issues. GTmetrix provides a detailed waterfall view, useful for understanding the loading order of resources.
| Tool | Data type | Relevant use |
|---|---|---|
| PageSpeed Insights | Lab and field | Initial diagnosis and recommendations |
| Lighthouse | Lab | Local tests during development |
| Google Search Console | Ground | Continuous tracking of actually visited URLs |
| Chrome UX Report | Ground | Aggregated analysis of Chrome users |
| GTmetrix | Lab | Waterfall analysis and histor tracking |
To complete an audit, tracking solutions like web-vitals.js can report metrics directly from real sessions. This approach becomes valuable worn a site has complex user journeys or very mobile audiences.
A selection of SEO and perforance tools can also help priorize actions. The landscorpe of the best SEO tools provides useful leads for combining perforance, visibility, and technical tracking.
Optimizing WordPress to reduce perceived slowdowns
WordPress can deliver very good Core Web Vitals, provided you avoid uncontrolled accumulation of plugins, heavy themes, and poorly configured visual builders. The problem is not WordPress itself, but the way it is put together.
A slow-clicking WordPress site may load too many global scripts on every page. For example, a form form plugin may inject its JavaScript even on pages without a form form, unnecessarily weighing down the experience.
Extensions such as WP Rocket, Autoptimize, ShortPixel, EWWW Image Optimizer or Perfmatters can improve cache, minification, image compression, and selective script disabling. The choice should remain measured: installing too many optimization tools can create the opposite effect.
For WordPress projects, it is relevant to consult an up-to-date selection of the useful WordPress plugins, then test each addition against real metrics rather than relying on a marketing promise.
When a technical redesign becomes more profitable than isolated corrrections
Some sites accumulate so much technical debt that point optimizations are no longer enough. An outdated theme, stacked plugins, unmaintained scripts, and a confusing architecture can permanently limit results.
In that case, a controlled redesign becomes more rational than a series of patches. It makes it possible to start from a cleaner foundation, rethink templates, simplify user journeys, and priorize perforance from the design stage.
The decision should be based on evidence: Search Console data, conversion analysis, real load times, mobile bounce rate, server logs, and code audit. A website redesign successful redesign is not limited to a new design; it must strorngthen speed, SEO, and user experience.
DualMedia supports this type of project with a web and mobile approach: technical scoping, UX, development, SEO optimization, and post-launch support. The right goal is not to “make it new,” but to make the site clearer, faster, and more profitable.
Mistakes to Avoid with INP Core Web Vitals
The first mistake is aiming only for a score of 100. A perfect score can be costly in development time, alorough the real challenge is achieving green metrics and a smooth experience.
The second mistake is treating all scripts as equivalent. A payment script, a main menu, or a corm contact form does not have the same priority as a social widget located at the bottom of the page.
- Do not optimize only the homepage if product or service pages generate the traffic.
- Do not hide issues with cache without corriggering blocking scripts.
- Do not apply loading=”lazy” to the main image above the fold.
- Do not multiply trackers without measuring their real impact.
- Do not rely on a single Lighthouse test run from a fast connection.
The right approach is to priorize strategic pages, then corrigger the causes that affect the most users. A perforrmance site is above all a site that responds well under real browsing conditions.
Our opinion
INP Core Web Vitals marks an imporant shift in the way web performance is approached. It is no longer enough to load quickly; the site must also respond quickly, especially on mobile and on interactive interfaces.
A good overall score can therefore be reassuring, but it should never replace observing user behavior. Perceived slowdowns often arise at the exact moment when the visitor expects an immediate response.
To improre a site sustainably, the most effective approach combines technical auditing, JavaScript optimization, resource prioritization, third-party script control, and field monitoring. It is this complete vision that makes it possible to align SEO, UX, and real performance.
To go further, the analysis of Core Web Vitals and web performance helps structure a concrete, gradual, and measurable approach.
What is the INP Core Web Vitals?
Web Vitals INP Core measures a page’s responsiveness after a user interaction. It evaluates the delay between a click, a tap, or a keyboard input and the next visible update of the interface. The shorter this delay, the smoother the site feels.
Why does my site seem slow with a good PageSpeed score?
Your site may seem slow if its interactions are delayed despite a good initial load. PageSpeed provides a useful readout, but some slowdowns come from JavaScript, third-party scripts, or processing triggered after the click. INP is precisely what helps identify this lag.
What is the difference between INP and FID?
INP has replaced FID to measure responsiveness more comprehensively. FID only observed the first interaction, while INP takes interactions throughout the entire session into account. This metric is therefore more representative of the real experience.
What is the good threshold for INP Core Web Vitals?
A good INP should remain under 200 ms. Between 200 ms and 500 ms, the page is considered improvable. Beyond 500 ms, the user may clearly perceive slowness.
Is JavaScript the main cause of poor INP?
Yes, JavaScript is often the main cause of poor INP. Long tasks, third-party scripts, or poorly optimized events can block the browser’s main thread. The result is an interface that responds too late to user actions.
How to quickly improve a WordPress site’s INP?
Il faut d’abord réduire les scripts inutiles et différer ce qui n’est pas critique. Sur WordPress, des plugins de cache, d’optimisation des fichiers et de désactivation sélective des scripts peuvent aider. Un audit reste nécessaire pour éviter d’ajouter des extensions qui alourdissent encore le site.
Do INP, Core, and Web Vitals influence SEO?
Yes, INP is part of the Core Web Vitals considered in page experience. It is not the only ranking factor, but it can carry weight when several sites have comparable content and authority. Better responsiveness also improves engagement signals.
Should you aim for a score of 100 on PageSpeed Insights?
No, aiming for 100 isn’t always necessary or cost-effective. The priority is to achieve green Core Web Vitals metrics, especially LCP, INP, and CLS. A site that is slightly below 100 can still offer an excellent real-world experience.
What tools should be used to measure INP Core Web Vitals?
PageSpeed Insights, Google Search Console, and Chrome UX Report are the most useful tools. Lighthouse helps during development, but field data remains essential. It shows how the site actually performs for visitors.
Why do third-party scripts slow down interactions?
Third-party scripts can occupy the browser at the wrong time. Live chat, analytics, advertising pixels, or social widgets add computation and sometimes external requests. If they are not deferred or controlled, they degrade INP.
Can a redesign improve Core Web Vitals?
Yes, a well-scoped redesign can significantly improve Core Web Vitals. It makes it possible to streamline the architecture, simplify the templates, and reduce technical debt. However, it must be guided by clear SEO, UX, and performance goals.
Can DualMedia audit an INP Core Web Vitals issue?
Yes, DualMedia can analyze the technical causes of a degraded INP. The audit can cover JavaScript, third-party scripts, WordPress, mobile UX, and real-world performances measured on users. Recommendations are then priorized based on their impact on SEO and conversion.
Would you like to get a detailed quote for a mobile application or website?
Our team of development and design experts at DualMedia is ready to turn your ideas into reality. Contact us today for a quick and accurate quote: contact@dualmedia.fr