Seitenreport
Seitenreport
INP Checker
Interaction with Next Paint Free of charge 1 URL

INP CheckerPreliminary technical test

Check if JavaScript, widgets, tag managers, or third-party scripts are likely to weigh on a URL’s interaction.

Technical pre-testing without browser rendering. Own scores of 0–100 mean: higher = less recognized risk signals. No measured LCP, INP or CLS values. TTFB is measured on the server side.

Checking website performance
This check evaluates
External JavaScript files
Known JS weight
Inline script blocks
Third-party script hosts

Ideal for shops, booking routes, forms, product pages and pages with many tracking or widget tags.

Practical example · for illustration

Check inertial filter operation on a product list

Example: After a filter click, the page reacts late and several analysis widgets are integrated. Record the concrete interaction in DevTools. Decompose confirmed long tasks and load unneeded widgets only when needed.

What does not prove the result

Script number and file size are hints. They do not measure execution time and INP; a single small script can also cause slow interaction.

Deepen with PageSpeed Insights and available field data · Google's Definition of Core Web Vitals

Audit scope

What the INP Checker evaluated

External JavaScript files
Known JS weight
Inline script blocks
Third-party script hosts

The pre-check evaluates the retrieved HTML and a limited sample of linked resources. It does not execute JavaScript and does not simulate user interactions. Findings are concrete occasions for an examination in the browser; an inconspicuous result does not exclude performance problems.

Premium extension

From a single check to Core Web Vitals Audit

The audit examines multiple URLs and helps to find recurring technical patterns in templates. This way you can see if a change affects several pages and where you can start the implementation.

Starting a premium audit
FAQ

Questions about INP Checker

Why is INP hard to measure?

INP depends on real interactions, device, main thread and specific events. This tool shows technical candidates.

What are typical INP causes?

Large bundles, synchronous third-party tags, heavy hydration, and long JavaScript tasks are common causes.

Why are there standalone tools in addition to the audit?

Individual tools help with a specific URL or technical problem. The audit compares these signals across multiple URLs and shows recurring patterns.

Is the individual check free of charge?

Yes. The standalone tools check a single URL. For larger crawls, complete tables and CSV export, the premium audit is planned.