LIVE|INP|v.1

Core Web Vitals Monitoring

Pass INP on every interaction

Always-on monitoring of Interaction to Next Paint, the metric that replaced FID in March 2024. Sentry catches main-thread blocking, runaway third-party JS, and DOM bloat before users hit the 200ms p75 wall. Cortex handles the fix.

sentry.inp.live● 2 min ago
03:30:00GET https://capconvert.com/
03:30:00PSI: mobile + desktop · CrUX 28-day p75
03:30:01Parsing 9 INP rules...
03:30:02 PASS mobile_field_inp (162ms ≤ 200ms · FAST)
03:30:03 PASS desktop_field_inp (84ms ≤ 200ms · FAST)
03:30:04 PASS mobile_lab_tbt (148ms ≤ 200ms)
03:30:05 PASS main_thread_work (2.1s ≤ 3s)
03:30:06 PASS js_execution_time (1.4s ≤ 2s)
03:30:07 WARN third_party_main_thread (612ms > 500ms)
03:30:08 PASS dom_size_acceptable (842 ≤ 1500)
03:30:09 PASS unused_javascript_low (18% ≤ 30%)
03:30:10 PASS uses_passive_event_listeners
03:30:11 Score 8/9 · Grade A · optimized
Page Speed

Continuous Interactivity Monitoring

Continuous audits of mobile + desktop INP against Google's 200ms threshold and the documented diagnostics that explain why interactions are slow. Each rule maps to a primary web.dev INP doc. Sentry catches what fails. Cortex fixes it.

RULE · 1

mobile_field_inp

Mobile field INP ≤ 200ms (p75)

CrUX 28-day p75 INP on phone form factor under Google's 200ms 'Good' threshold. INP replaced FID as a Core Web Vital on March 12, 2024 and is the metric Google uses for the mobile interactivity signal.

RULE · 2

desktop_field_inp

Desktop field INP ≤ 200ms (p75)

CrUX 28-day p75 INP on desktop under Google's 200ms 'Good' threshold. Desktop interactivity matters for cart flows, dashboards, and any interaction-heavy page.

RULE · 3

mobile_lab_tbt

Mobile lab TBT ≤ 200ms

Lighthouse Total Blocking Time on mobile under 200ms. TBT is the lab proxy for INP - Lighthouse can't measure INP directly without real interactions, so TBT stands in.

RULE · 4

main_thread_work

Main-thread work ≤ 3s

Lighthouse mainthread-work-breakdown total under 3 seconds. Every millisecond of main-thread work past 50ms is a long task that delays the next interaction's paint.

RULE · 5

js_execution_time

JavaScript execution ≤ 2s

Lighthouse bootup-time audit shows total JS execution under 2 seconds on the throttled mobile profile. Long bootup time is the single biggest INP contributor on JavaScript-heavy sites.

RULE · 6

third_party_main_thread

Third-party main-thread ≤ 500ms

Third-party scripts (ad tags, analytics, chat widgets, A/B tools) consume less than 500ms of main-thread time. Third parties are the #2 INP contributor after first-party JS.

RULE · 7

dom_size_acceptable

DOM size ≤ 1500 elements

Total DOM tree under 1500 elements. Event-handler work scales linearly with DOM size - large DOMs make even simple interactions expensive.

RULE · 8

unused_javascript_low

Unused JavaScript ≤ 30%

Lighthouse unused-javascript audit shows less than 30% of total JS bytes go unused on page load. Unused JS is parse + compile + execute cost paid for nothing - and a known INP regression source.

RULE · 9

uses_passive_event_listeners

Passive event listeners on scroll/touch

Touch and wheel event listeners are registered as `passive: true`. Non-passive listeners block scroll-driven rendering and inflate INP for any scroll-triggered interaction.

Page Speed

Free INP Checker

Paste your homepage URL. Sentry runs PSI for mobile + desktop, pulls 28-day CrUX field INP, and inspects Lighthouse's main-thread, third-party, DOM-size, bootup-time, unused-JS, and event-listener diagnostics. No signup, instant results, always free.

Comprehensive auditInstant resultsCompletely free
Instant

Audit in under a minute

Sentry fetches your site, runs every INP rule, and renders the full result page before your next sip of coffee.

Actionable

Every failure gets a fix

Each failed rule ships with a prescription paragraph. Hand it to engineering and the gap is closed before lunch.

Ongoing

Locked in for the long haul

Add your site to the daily Sentry sweep with one click. New regressions get caught the next morning.

9 rules in the INP Sentry. Daily 3:30 AM ET sweep.

Optimize Interactivity

Stop Guessing. Start Seeing. Get Cortex.

One brain. Thirty-six pairs of eyes. Sentries monitor every visibility signal that decides whether search engines, AI engines, and ad platforms show you. Cortex reads what they see, weighs it against a unified corpus of platform documentation, and acts. Every move follows a defined decision protocol: action stated, reason given, impact named.

250
Ranking signals
30
Sentries
60
Platforms
Daily
Always-on
llms.txtai-citationsai-crawlersbrand-pulsetitle-tagsmeta-descstructuredsitemapcore-vitalspage-speedaccessibilitydomain-agehttpsaboutauthorsbacklinksmentionsreviewsinternalgbpnapyelptrusthelpfultopicalfirst-handcronavboostfreshnesshreflangimage-seopage-qualitycanniballlm-outputtrackingssl-tlsCORTEXdecision engine