The page reacts slowly to taps and clicks: INP 350 ms on 2 pages

Short answer

On the listed pages, Interaction to Next Paint from real Chrome users is above 200 milliseconds (over 500 ms is poor): after a tap, click or key press, the page takes too long to show a response. Find the slow interactions, break up long JavaScript tasks and remove or defer third-party scripts.

perf.inp · Priority: P1–P3, by crawler type

What it means

Interaction to Next Paint measures how fast the page responds to input; up to 200 ms is good. Break up long JavaScript tasks, defer third-party scripts and avoid heavy work in click handlers.

Why it matters for AI search

INP is the Core Web Vital for responsiveness. It looks at the interactions during a visit and reports one of the slowest. A page that freezes after a tap feels broken, and people tap again or leave.

INP exists only in real-user data. The audit takes it from the Chrome UX Report through PageSpeed Insights (mobile, the 75th percentile over the last 28 days), for the page or else for the whole site. A lab run has no real interactions, so for pages without this data the audit reports Total Blocking Time instead. The finding is P2 when any page is in the poor range.

How to fix it

  1. Find the slow interactions. In Chrome DevTools, the Performance panel shows INP live while you click around; on the live site, the web-vitals library can report it from real visitors.
  2. Break long tasks into smaller ones and let the browser paint between them, for example with scheduler.yield() or setTimeout, as in the example.
  3. In event handlers, update the screen first and run the rest, such as analytics, saving or heavy calculations, after the next paint.
  4. Remove or defer third-party scripts such as chat widgets, A/B testing and tag managers that run on every interaction, and avoid re-rendering large parts of the page on each input.
  5. Run the site audit again from your account. Real-user data can take up to four weeks to reflect a fix.

Example

button.addEventListener("click", async () => {
  showSpinner();          // visible feedback first
  await yieldToMain();    // let the browser paint
  saveAndTrack();         // the slow part after
});

function yieldToMain() {
  if (globalThis.scheduler?.yield) return scheduler.yield();
  return new Promise(r => setTimeout(r, 0));
}

How to confirm the fix

After the change, press "Check again" on the report: it lists what was fixed and how the score changed.

Check my page →

All findings and how the score works