SEO & Speed

Free SEO and Core Web Vitals audit

Enter your domain and we run Google's own PageSpeed Insights against it, then fetch your HTML and check the on-page fundamentals. Real measurements, not a simulated score.

We fetch your homepage and query Google's PageSpeed Insights API. Nothing is stored.

Performance scores and Core Web Vitals come directly from the Google PageSpeed Insights API, including field data from the Chrome UX Report where Google has enough traffic for your domain. On-page checks are performed against the HTML actually returned by your server. If a check cannot run, the tool reports that rather than assuming a result.

The guide behind this tool What Core Web Vitals Actually Cost You in Revenue A small ranking factor and a large conversion factor. What LCP, CLS and INP measure, what causes bad scores, and how to fix them in order. Read the guide · 6 min read →

What this tool checks

Ten measurements, pulled from Google's own API and from the HTML your server actually returns.

  • Performance score

    Google PageSpeed Insights runs the same audit it runs on its own site, on mobile by default.

  • Largest Contentful Paint

    How long until the main content renders. Google's threshold is 2.5 seconds; above 4 you lose a large share of mobile visitors.

  • Cumulative Layout Shift

    How much the page jumps while loading. Usually images or ads without reserved space.

  • Real-user field data

    Chrome UX Report measurements from actual visitors over 28 days — the data Google ranks on, not the lab score.

  • Title and description

    Present, unique, and within the length Google displays before truncating.

  • Indexing directives

    Whether a stray noindex or a canonical conflict is quietly removing the page from search.

  • Structured data

    Which Schema.org types are present and whether they parse.

  • robots.txt and sitemap

    Whether crawlers can find your pages and whether a sitemap is declared.

  • Mobile viewport

    Whether the page adapts to phone screens or renders at desktop width.

  • Image alt text

    How many images carry no alt attribute — an accessibility failure and lost image-search traffic.

How to read your result

Fix in this order, because the items are not equally weighted.

  1. Anything blocking indexation first. A stray noindex or a canonical pointing at the wrong URL is worth more than every performance fix combined — the page is invisible until it is resolved.
  2. Then Largest Contentful Paint. This is almost always the hero image: oversized, in the wrong format, and without a priority hint. It is usually an hour of work for the largest single improvement available.
  3. Then layout shift. Add width and height to every image. Trivial, and it fixes most CLS.
  4. Then metadata. A missing description will not hurt your ranking, but Google writing your pitch for you will hurt your click-through.

If the field data and the lab score disagree, believe the field data. It comes from real visitors on real devices; the lab score comes from one simulated run.

What this audit checks, and why each item matters

Core Web Vitals

Largest Contentful Paint, Cumulative Layout Shift and Interaction to Next Paint are confirmed Google ranking signals and, more importantly, they correlate directly with bounce rate. A page that takes four seconds to show its main content loses a large share of mobile visitors before they see anything.

Title and meta description

These are your advertisement in the search results. A missing or duplicated title is one of the most common and most fixable causes of poor click-through on pages that already rank.

Structured data

Schema.org markup is how you tell search engines and AI models what your page is about in unambiguous terms. Without it, you are relying on them to infer correctly.

Crawl directives

robots.txt and canonical tags control what gets indexed. Misconfiguration here can remove an entire site from search, and it happens more often than you would expect — usually a staging directive that shipped to production.

Heading structure

A single, descriptive H1 and a logical heading hierarchy help both search engines and AI answer engines extract the structure of your content. It is also a baseline accessibility requirement.

Frequently asked questions

Is this actually running real checks?

Yes. Performance data comes from Google's PageSpeed Insights API — the same source as the PageSpeed Insights website. On-page checks are run against the HTML your server actually returns. If any check fails to run, the tool tells you instead of showing an assumed result.

Do you store my domain or results?

No. The check runs, the result is returned to your browser, and nothing is retained. You do not need to give us an email address to see the full result.

Why is my score different from PageSpeed Insights?

It should not be — we use the same API. Small differences can occur because lab tests vary between runs, and because field data updates on a rolling 28-day window. If you see a large discrepancy, run both again a few minutes apart.

What should I fix first?

Generally: anything blocking indexation, then Largest Contentful Paint, then layout shift, then metadata. Fixing an accidental noindex is worth more than any performance work. The results panel orders findings by impact.

Other free tools

Tell us what you are trying to grow.

One team. Three offices. Twenty-six languages. Send us the problem and you get a senior answer — not a sales script.

Get a proposal → Message us now

A written proposal within one business day, in your language.