Instant Performance-Audit
Enter a URL. We score Core Web Vitals, accessibility, best practices and SEO — in seconds, in your browser. The full competitor + AI-visibility report follows within 24 hours if you want it.
Enter a URL, scored in seconds.
From a raw URL to an honest number.
Fetch the page
We load your URL via Google PageSpeed Insights — the same measurement Google uses for ranking.
Core Web Vitals
LCP, CLS and TBT scored against Google’s mobile thresholds.
Full report
On request within 24 h: competitor comparison + a prioritised action plan.
The machine measurement is step 1. The plan is step 2.
Enter a URL. We score Core Web Vitals, accessibility, best practices and SEO — in seconds, in your browser. The full competitor + AI-visibility report follows within 24 hours if you want it.
Core Web Vitals are not a nice-to-have. They are the entry threshold.
The Performance audit measures your website with Google PageSpeed Insights — the same measurement Google itself uses for ranking. You see four scores (Performance, Accessibility, Best Practices, SEO) and the three Core Web Vitals: LCP (main-content load time), CLS (visual stability) and TBT (script blocking time).
Google's ranking model now weights mobile speed as a primary signal, not a tiebreaker. A page with LCP above 2.5 seconds starts organic search with a handicap — regardless of how good its content is. On legacy stacks this is rarely an optimisation problem; it is an architecture problem: database queries, plugin layers and render-blocking are built in.
The instant check here is the machine measurement. On request, the full senior-reviewed report follows within 24 hours: competitor comparison, page-type analysis and a prioritised action plan.
What is a good Lighthouse performance score?
90 or higher counts as green. Values between 50 and 89 signal real problems; below 50 is critical. Our new builds on Astro and Vercel consistently deliver 95–100, because pre-rendered HTML ships without a runtime database query.
What LCP value does ranking require?
Google rates LCP under 2.5 seconds as good, 2.5–4.0 seconds as needs improvement, above 4.0 seconds as poor. Measurement is mobile — where most searches happen. Modern stacks reach under 1.0 second.
Why does the score differ from my own test?
PageSpeed Insights combines lab data (a simulated mid-range mobile device) with field data from real Chrome users where available. Your desktop browser with a warm cache is always faster than the measurement environment — what matters is the mobile lab measurement, because that is how Google evaluates.
Can Core Web Vitals be fixed on a legacy stack?
Partially — caching plugins and image optimisation often recover 10–20 points. The structural ceiling remains: an architecture that renders pages from a database at runtime rarely holds today’s thresholds permanently. That is why we measure first and recommend second — sometimes optimisation is enough, sometimes migration is the honest answer.