Chrome's field data places this page's Interaction to Next Paint between 200 and 500 milliseconds at the 75th percentile. The page does not pass the Core Web Vitals assessment until INP is 200 milliseconds or less. At this level the page feels slightly sluggish rather than broken, and the cause is usually script running at the moment of interaction: analytics, tag managers, or hydration.
Third-party and framework scripts run during page load, so an early tap lands behind a long task:
<script src="https://tags.example/tag-manager.js"></script>
<script src="/bundle.js"></script>Load non-essential scripts after the page is interactive, split large bundles, and avoid doing layout-heavy work inside input handlers:
<script src="/bundle.js" defer></script>
<script>
addEventListener('load', () => {
const s = document.createElement('script');
s.src = 'https://tags.example/tag-manager.js';
document.head.append(s);
});
</script>The main thread can do one thing at a time. The less script is queued when a user acts, the sooner the browser can respond, and the 75th-percentile interaction is usually one that arrived while something else was running.
This issue can affect your site's search engine rankings and user experience. Addressing it promptly helps ensure optimal performance and visibility in search results.
bseoa automatically checks for this warning during site analysis, along with hundreds of other technical SEO issues.
Choose the license that fits your needs and start getting the deep, actionable insights you deserve.