Skip to content

Slow to answer taps on phones

cwv-inp-poorserious
On this page

Why it matters

  • Interaction to Next Paint (INP) measures how long the page takes to show a response after a tap, a click or a key press. Past half a second, the page feels stuck, and visitors tap again or leave.
  • It is one of the three Core Web Vitals, which Google's search ranking systems use.
  • These are real visits, on real phones: slower phones feel heavy scripts most.

How to fix

  • Long tasks on the page's main thread are the usual cause: split heavy JavaScript work into short parts, so the browser can answer between them.
  • Load less JavaScript: third-party scripts, such as chat, analytics and ads, often hold the main thread.
  • Keep event handlers short: make the visible change first, and do the rest after it.
  • A very large page, with many thousands of elements, makes every update slower.

How we detect

  1. With an API key, we ask the Chrome UX Report (CrUX) about the page's URL on phones: the last 28 days of visits in Chrome by users who share usage statistics and sync their browsing history. Chrome on iPhone, apps' web views and other browsers are not counted. When CrUX has no data for the URL, we ask about the whole site (its origin), and the finding says so.
  2. The rule fails when the 75th percentile of Interaction to Next Paint is over 500 milliseconds: Google's limit for poor.
  3. Without a key, or when CrUX has no data for the page or its site, as for many sites with fewer visits, the rule does not apply. A page on a local or private address is never sent to Google.
  4. CrUX covers the last 28 days, so a fix shows in it gradually, over about four weeks.