Your INP Score Is the New Bounce Rate
Key takeaways
- INP (Interaction to Next Paint) is the Core Web Vitals metric that measures how snappy your site feels when users tap, click, or type.
- An INP score above 200ms is now a primary ranking risk. Google quietly raised this from a “consideration” to a “ranking input” in 2026.
- It’s not the same as page speed. A fast-loading site can still have terrible INP — and that’s exactly what’s hitting small business sites.
- The usual culprit is too much JavaScript, often from page builders, marketing widgets, and analytics overhead.
For years, “site speed” meant one thing to most small business owners: how long it took the page to show up. If the homepage loaded in under three seconds, you were doing well, and Google would presumably reward you.
That definition is now incomplete. In 2026, Google judges not just how fast a page loads, but how responsive it feels — every tap, every menu click, every form interaction. The metric for this is INP, and it’s quietly become the Core Web Vitals score that’s tripping up the most small business sites.
What INP actually measures
INP — Interaction to Next Paint — measures the delay between when a user does something (taps a button, opens a menu, types in a form) and when the page visibly responds.
If you tap “Menu” and nothing happens for 400ms before the menu actually opens, your INP score for that interaction is 400ms. Google takes the worst few interactions during a typical page visit and uses those to set your site’s INP score for ranking purposes.
| INP score | Status | What users feel |
|---|---|---|
| Under 200ms | Good | Instant. Feels native. |
| 200ms – 500ms | Needs improvement | Noticeable lag. Users hesitate. |
| Over 500ms | Poor | Feels broken. Users tap again, get frustrated. |
Why INP is the new bounce rate
Bounce rate — the old metric for “users who left after one page” — quietly stopped being useful years ago. Modern analytics tools don’t even prominently report it the same way. But the underlying problem it tried to measure (users frustrated and leaving) is real, and INP captures it more precisely than bounce rate ever did.
When users tap something and nothing happens, they don’t think “this site has a high INP.” They think “this site is broken” — and they leave. Often without conversion, often without coming back. INP is the metric that measures the moment before the user gives up.
Page load tells you whether the customer arrived. INP tells you whether they’re frustrated enough to leave.
Why INP is the metric that’s failing now
The other Core Web Vitals metrics — LCP (loading) and CLS (visual stability) — most well-built sites pass. INP is different. INP is failing for sites that pass everything else.
The reason: JavaScript bloat. Modern websites accumulate JavaScript from every direction:
- The WordPress theme.
- The page builder (Elementor, Divi, Beaver Builder, etc.).
- Every plugin.
- Marketing scripts (Google Analytics, Facebook Pixel, Hotjar, chat widgets, retargeting tags).
- Embedded widgets (review feeds, social embeds, booking calendars).
Each of these adds JavaScript that the browser has to execute when the user interacts with the page. The more JavaScript fighting for the same thread, the longer the gap between user action and visible response.
The diagnosis
Two free tools.
1. PageSpeed Insights (pagespeed.web.dev)
Paste your URL, hit go. Look at the Mobile tab, scroll to the “Core Web Vitals Assessment” box, and find the INP number. This is a lab test (simulated, not real users). Useful for spotting problems but not the final word.
2. Google Search Console
The Core Web Vitals report in Search Console shows you actual visitor data — what your real customers on real phones are experiencing. This is what Google ranks by. If Search Console says your INP is bad on the URLs that matter for SEO, that’s the priority.
The fixes (in order of effort)
1. Remove what you don’t need
Open your site and audit every plugin, widget, and script. Are you actually using Hotjar? Do you need both Google Analytics and a Facebook Pixel and Meta Conversions API? Is that chat widget delivering enough leads to justify the speed cost? The single biggest INP improvement for most small business sites is removing tools that aren’t pulling their weight.
2. Defer or lazy-load what stays
Marketing scripts (analytics, pixels) often don’t need to run before the user interacts with the page. Deferring them — telling the browser to wait until after the page is responsive — frees up the main thread for things the user actually cares about.
3. Replace heavy widgets with lightweight versions
Review widgets, social media embeds, booking calendars, video embeds — each of these has heavy and light versions. The heavy version pulls in the full JavaScript framework of the service it represents. The light version is a static placeholder that loads the full version only when needed.
4. Pick a leaner page builder, or build without one
The popular page builders are wonderful for non-developers but tend to produce JavaScript-heavy output. If you’re already on one of the heavy builders, switching is a real project. If you’re considering a redesign anyway, this is the point in the conversation where lighter alternatives (Gutenberg native blocks, Bricks, GeneratePress) deserve a serious look.
5. Audit your code (the developer step)
For sites that have been through multiple owners or designers, the JavaScript in the head section often contains scripts that haven’t been needed in years. A clean audit by a developer can usually find significant cuts.
What INP isn’t going to fix
A few realistic notes.
INP improvements don’t directly produce more revenue the way a better hero image or a clearer call to action might. They reduce friction. They keep users from abandoning. They preserve rankings. The effect is real but indirect.
If your site already converts well and ranks well, INP optimization is a defensive move — protecting what you have. If your site converts poorly or doesn’t rank, INP fixes alone won’t solve it. Content, design, and SEO basics still come first.
The real-world impact
For an East Texas small business site that gets a modest amount of organic traffic — say 500 visits a month from Google — what does fixing INP actually buy you?
- Improved field data over the next 28 days (Search Console refresh cycle).
- Modest ranking improvement, especially in competitive local searches.
- Fewer “I tried to click but nothing happened” frustrations.
- Better conversion rate on forms and CTAs, in the 5–15% range.
- Most importantly: protection against losing rankings you currently have.
For a site driving real revenue, that’s worth the half-day of audit work.
Where people go wrong (and when to call a pro)
The most common INP mistake is treating the score as a “speed problem” and throwing caching at it. Caching makes pages load faster on subsequent visits. It does not improve the snappiness of interactions — that’s an entirely different bottleneck (the main JavaScript thread). If your INP is failing in Search Console and your PageSpeed Insights score is mid-range despite multiple caching plugins, the problem is JavaScript volume, and that’s where a developer who’s looked at a lot of WordPress sites will find the cuts faster than another caching experiment. Worth the audit if your traffic is meaningful and your competition is real.
Frequently Asked Questions
How is INP different from page speed?
Page speed measures how long the page takes to show up. INP measures how snappy interactions feel once you’re on the page. A site can load fast and still feel laggy when you tap things, and vice versa.
Does INP affect rankings?
Yes, as of 2026, INP scores above 200ms are a meaningful ranking signal in competitive searches. For uncontested searches, the effect is smaller. For competitive local terms, it matters.
Can I just disable JavaScript to fix INP?
No — most of your site’s functionality depends on JavaScript. The goal isn’t to remove it but to remove what’s not pulling its weight and defer what isn’t immediately needed.
What’s the single highest-impact change?
For most small business sites: replacing or removing the heavy embedded widgets (chat, video, social feeds, review widgets). These contribute a disproportionate share of the JavaScript that drags INP down.
If your site’s been quietly losing ranking momentum and you’re not sure why, an INP audit is a good place to start. Happy to take a look.