What is INP by bot type
INP by bot type shows how Interaction to Next Paint (INP) behaves across different crawler categories - such as Googlebot, Bingbot, and other search or social crawlers.
While INP is primarily a user-centric metric measuring responsiveness to real interactions, this insight helps you understand how interactive readiness differs when pages are rendered or evaluated by bots.
Even though bots don’t click and scroll like humans, they still execute JavaScript, parse event listeners, and evaluate page responsiveness signals. Differences in rendering environments, execution timing, or script prioritization can surface inconsistencies.
If responsiveness differs for certain bots, it may impact:
How rendering quality is evaluated
How efficiently pages are processed and indexed
How JavaScript-heavy experiences are interpreted by search engines
INP by bot type sample
Should you worry
In a healthy scenario, INP remains consistent across major bot types and closely aligns with real-user INP trends.
That means:
Critical JavaScript executes predictably regardless of user agent
Event listeners are registered without delay
Main-thread blocking tasks are minimized
Bots process interactive logic without unusual slowdowns
You don’t need identical INP across all crawlers - but large discrepancies across major search engines deserve investigation.
Healthy signals:
Stable INP across Google and Bing
No extreme outliers for specific bots
Similar responsiveness patterns between bots and real users
Unhealthy signals:
Googlebot INP significantly worse than real users
One crawler consistently showing delayed responsiveness
INP spikes correlated with heavy JavaScript execution
If Googlebot shows worse INP, ask:
Is JavaScript hydration slower for crawler-rendered sessions?
Are scripts conditionally loaded or deprioritized for bots?
Are long tasks blocking the main thread during bot rendering?
Responsiveness gaps often signal deeper JavaScript execution issues rather than visual problems.
Unhealthy INP by bot type
Common causes of unhealthy INP by bot type:
Heavy JavaScript bundles
Large scripts that delay interactivity can impact bot-rendered sessions.Hydration delays
Framework-based apps may hydrate slower depending on rendering strategy.Conditional script loading
Different logic for crawler user agents can unintentionally change execution timing.Main-thread blocking tasks
Long-running JavaScript operations delay interaction readiness.
If one bot consistently reports worse INP, compare execution timelines. Rendering parity is critical - especially for JavaScript-heavy applications.
Resolving unhealthy INP by bot type
Go-to action plan to resolve an unhealthy INP by bot type:
Ask Uxi to analyze your INP by bot type values and suggest improvements.
Use Filters to see if slowdowns align with specific geographies, pages, or device types.
Simulate INP of the suspected insight to see if fixing it will resolve the slow INP by bot type. If yes, this is where the resolution focus should be.
Once you’ve improved INP, set an alert to be the first to know if it starts worsening again.
Try it yourself
Explore how your website performs across different bot types using real crawl data.
If bots experience slower INP than users, your SEO visibility could be quietly affected - even if your Core Web Vitals look healthy on the surface.