GitHub Add to your assistant
Menu

perf.field-inp-needs-improvement

InfoSEO audit--field-data

On phones, real visits wait more than 200 ms for the page to answer a tap or a key at the 75th percentile: Interaction to Next Paint (INP) in the Chrome UX Report's last 28 days, for the page's URL or, when it has too few visits, its origin. Google rates it as needing improvement.

What to change

Shorten the work a tap or a key starts: split long JavaScript tasks (await scheduler.yield()), defer scripts in <head>, load other sites' scripts after the page, and keep the viewport meta tag so phones answer a tap at once. The Chrome UX Report covers 28 days, so a fix shows there over the next four weeks; check it now with --lighthouse on the local tool, or PageSpeed Insights, which also names the element.

The documentation on developers.google.com

A finding of this rule on a page carries the exact edits for that page: the markup it quotes, and what to write instead.

When it runs

Runs with --field-data (fieldData), on the command and both MCP servers, and in this site's audits: it reads the Chrome UX Report's real-user data. Info is a best practice: worth doing, rarely urgent, and --no-info leaves it out. Each finding takes 1 point off the page's score.

The severity here is the rule's usual one: a finding can be raised or lowered when the page gives a reason.

Run it, or skip it

Check a page for this rule alone, after a fix for instance:

npx @rivi-software/agentic-seo-check audit https://example.com --field-data --rule perf.field-inp-needs-improvement

Or from an assistant, with the MCP tool seo_audit_page:

{
  "url": "https://example.com",
  "fieldData": true,
  "rules": [
    "perf.field-inp-needs-improvement"
  ]
}

To leave it out of an audit, pass --disable perf.field-inp-needs-improvement on the command, or disableRules: ["perf.field-inp-needs-improvement"] to a tool.

All 17 rules