News

INP Replaced FID in Core Web Vitals: What It Means for Your Site

November 8, 2026 4 min read
INP Replaced FID in Core Web Vitals: What It Means for Your Site

In March 2024, Google replaced First Input Delay, known as FID, with Interaction to Next Paint, known as INP, as one of its three Core Web Vitals. These are the metrics Google uses to describe how a page feels to real visitors. The change raised the bar for responsiveness, and many sites that passed easily under the old metric found they had work to do.

What Changed

Core Web Vitals cover three parts of the visitor experience:

MetricWhat it measuresGood score
Largest Contentful Paint (LCP)How quickly the main content appears2.5 seconds or less
Cumulative Layout Shift (CLS)How much the page jumps around while loading0.1 or less
Interaction to Next Paint (INP)How quickly the page responds to taps, clicks and key presses200 milliseconds or less

FID only measured the delay before the browser started handling a visitor's very first interaction. It ignored how long the response actually took, and it ignored everything after that first tap. INP looks at interactions across the whole visit and reports a value close to the slowest one. A page that feels sluggish when someone opens a menu, adds an item to a cart or types into a form now shows up as slow.

Google measures these scores from real Chrome users, not just lab tests. A page is considered good when at least 75 percent of visits meet the threshold, and an INP above 500 milliseconds is rated poor.

What It Means for a Small Business

The usual cause of a poor INP score is too much JavaScript competing for the browser's attention. Small business sites often collect it over time: a chat widget, a pop-up tool, several tracking tags, a review carousel, an animated slider and a heavy theme. Each one seemed harmless when it was added. Together they can make a phone freeze for a moment every time someone taps.

It is worth keeping this in proportion. Google has said Core Web Vitals are used by its ranking systems, but that relevant, helpful content matters more, and a good score will not make up for a weak page. The bigger reason to care is your visitors. A button that does not seem to respond leads to repeated taps, abandoned forms and lost sales, especially on older phones.

What to Do

  1. Check your real data. Look at the Core Web Vitals report in Google Search Console, or run your key pages through PageSpeed Insights and read the field data section. Low-traffic sites may not have enough data yet, which is normal.
  2. Test on a modest phone. Open your site on a mid-range or older phone, not just your newest one, and try the menu, search, cart and contact form.
  3. Remove what you do not use. Audit third-party scripts. Old tracking tags, abandoned plugins and duplicate analytics tools are common and easy wins.
  4. Delay what is not urgent. Chat widgets and similar tools can often load after the main page is ready, or only when someone asks for them.
  5. Show instant feedback. When an action takes time, such as submitting a form, the button should change right away so visitors know something is happening.
  6. Simplify heavy sections. Large carousels, complex animations and very long product grids are frequent causes of slow interactions on phones.

If you use a hosted website builder or a ready-made theme, the platform handles much of the underlying code, but the add-ons you choose still count. Ask your provider or developer to look at INP specifically, since it usually needs different fixes than loading speed.

Quick Checklist

  • Core Web Vitals report reviewed in Search Console
  • Key pages tested on an older phone
  • Unused scripts, tags and plugins removed
  • Chat and pop-up tools set to load late
  • Buttons and forms show feedback immediately
  • INP aimed at 200 milliseconds or less on key pages