The AI search toolkit · 2.0Technical · Tool 13
Free Core Web Vitals Analyzer
Read LCP, INP and CLS in the right context. Run a Google PageSpeed test or import a report, then separate Lighthouse lab performance and Total Blocking Time from real-user Core Web Vitals.
Analyse performance
Local import · optional Google testExample data is loaded. These are fictional demonstration inputs, not a DigiMSM or client performance result. Use Clear to start your own analysis; editing example values keeps the run labelled as an example.
The interactive tool requires JavaScript. If the form does not appear, check that your WordPress setup allows this fragment’s inline script. The methods and FAQs below remain readable.
Inputs changed. Run the tool again to refresh the result and enable exports.
Your evidence comes first.
Read PageSpeed, Lighthouse and CrUX reports with lab and field data separated. Enter your information or load the labelled example to see the workflow.
No score, scan or platform result is invented while you wait.
A practical workflow
From input to a useful next step.
Choose a live test or saved report
Import PageSpeed Insights, Lighthouse or CrUX JSON for local analysis, or explicitly request a live Google test of a public URL. A live request sends the URL to Google.
Read lab and field sections separately
Review Lighthouse performance, LCP, CLS and TBT in the lab section. Use available 75th-percentile LCP, INP and CLS for the real-user assessment.
Prioritize and verify improvements
Check which metric needs attention, confirm whether the field data is URL-level or origin-level, and compare representative tests before and after implementation.
Know what you are measuring
The method behind the result.
Read PageSpeed, Lighthouse and CrUX reports with lab and field data separated. The scope and limitations below help you interpret the output and decide what to verify next.
Core Web Vitals use real-user context
The good thresholds shown are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1 at the 75th percentile. All three field metrics are needed for this tool’s complete verdict.
TBT is a different diagnostic
Total Blocking Time is a Lighthouse lab metric. It can help investigate main-thread blocking, but it is not INP and is not one of the three Core Web Vitals. The interface keeps its label explicit.
Missing data remains unavailable
Not every report includes field data. PageSpeed has announced plans to discontinue its CrUX payload, so a separate CrUX JSON import is supported. Origin-wide data is labelled and never presented as proof that a specific page passes.
Clear answers
Before you act on the result.
Understand the inputs, what the output can establish and how to use it in a broader audit.
Can I run a live PageSpeed test here?
Yes. Choose Live Google test and confirm the data transfer. The request goes directly to Google’s PageSpeed Insights API. Network access, API availability, quotas and key restrictions can affect whether it completes.
Can I use the analyzer without an API key?
You can always import a saved supported JSON report locally. Live Google requests may work without a key, subject to Google’s availability and quotas. An optional key does not guarantee a successful test.
Is Total Blocking Time a Core Web Vital?
No. TBT is a lab diagnostic. The Core Web Vitals are LCP, INP and CLS. This analyzer displays TBT separately instead of using it as a substitute for INP.
Why does the report say field data is incomplete?
A supported report can lack one or more real-user metrics. Missing data is shown as unavailable, and the tool withholds a complete Core Web Vitals verdict instead of assigning a zero or a pass.
What is the difference between URL and origin data?
URL-level data describes the reported page sample. Origin-level data aggregates the origin and can include many pages. A good origin result does not establish that every individual page has the same experience.
Will a higher Lighthouse score guarantee better rankings?
The score is a lab performance diagnostic, not a ranking forecast. Improve the experience your users actually receive and verify outcomes with appropriate field data and business measurements.
Continue your investigation
The next check is one click away.
JavaScript Rendering Checker
Compare supplied raw and rendered HTML without executing untrusted page code.
Open this tool ↗Schema Markup Generator
Create type-specific JSON-LD with validation and a safe code preview.
Open this tool ↗AI Traffic Loss Calculator
Compare traffic periods and model value gaps without inventing AI attribution.
Open this tool ↗DigiMSM · Website development and performance
Turn a performance report into implementation.
DigiMSM can investigate the loading, interaction and layout issues behind your report, then scope practical changes for your website platform.
Built for DigiMSM · Methods reviewed 14 September 2026 · Free tool; service work is scoped separately.