Skip to content

Check website speed and SEO

Audit a public page for on-page SEO, from titles, headings and canonical tags to robots.txt, hreflang and structured data, plus Core Web Vitals; our server fetches the URL and stores nothing.

Any public http or https page. Our server fetches it once; nothing is stored.

Processed on our server · the URL is fetched on demand and results are not storedHow it works

How to use Website speed & SEO checker

  1. 1

    Enter a page address

    Type or paste any public URL, with or without https://, and click Check page.

  2. 2

    Read the score

    The summary weighs every check by impact and splits the result into indexing, content, social, technical and speed.

  3. 3

    Open each issue

    Expand a red or amber row to see what was found, why it matters to search engines and the exact change that fixes it.

  4. 4

    Compare speed

    Core Web Vitals load from PageSpeed Insights for mobile; switch to desktop, then fix and re-check until the page passes.

Limits and Pro

Free: 10 page checks and 4 Core Web Vitals tests a minute, pages up to 5 MB of HTML, a 15-second timeout per page and up to 5 redirects followed.

About Website speed & SEO checker

The SEO checker audits one page the way a crawler first sees it: the raw HTML returned by the server, its HTTP headers and its robots.txt. It runs up to 23 checks. Indexing covers the status code, robots meta tags and the X-Robots-Tag header, whether robots.txt lets Googlebot crawl the URL under RFC 9309 longest-match rules, the canonical link, hreflang alternates and the redirect chain. Content covers the title and meta description lengths, a single H1, skipped heading levels, images without alt text, the lang attribute and how much readable text there is. Social and technical checks look at Open Graph and X card tags, JSON-LD syntax and types, HTTPS and the http-to-https redirect, the mobile viewport, character encoding, compression and internal and external links.

Speed has two layers. The server response time and HTML size are measured on every check. Core Web Vitals come from Google's PageSpeed Insights: field data for real Chrome users at the 75th percentile, for the URL or the whole site, plus a Lighthouse lab score. If Google's quota is used up or the test fails, the report says so instead of showing invented numbers.

The checker reads one URL at a time and does not run JavaScript, so content rendered only in the browser is not counted; it does not crawl your site, check backlinks or track rankings.

Privacy

When you click Check page, the address goes to our server, which downloads that page, its robots.txt and the http:// version once to build the report, and sends the address to Google PageSpeed Insights for Core Web Vitals. The report is returned to your browser and nothing is stored or logged; private network addresses are refused.

Features

Up to 23 on-page checks

Indexing, content, social, technical and speed, each with why it matters and how to fix it.

Core Web Vitals

Real-user LCP, INP and CLS plus a Lighthouse lab run from PageSpeed Insights, mobile or desktop.

robots.txt verdict

Shows the exact rule that allows or blocks Googlebot, using RFC 9309 matching.

Website speed & SEO checker: frequently asked questions

How is the SEO score calculated?
Each check has a weight that reflects its impact: a noindex tag or a missing title weighs far more than a missing X card. A pass earns the full weight, an improvement half and a fix nothing, and notes are left out. The score is the share of available points, so 100 means every weighted check passed. It is a to-do list, not a ranking prediction.
What data does the checker send and keep?
Your browser sends the page address to our server. The server fetches that page, its robots.txt and the http:// variant, and asks Google PageSpeed Insights to test the address for Core Web Vitals. Results go straight back to your browser. We keep no copy of the URL, the HTML or the report, and the request is not written to a log.
Why are Core Web Vitals sometimes not shown?
They come from Google PageSpeed Insights, which limits how many tests can run each day and needs to load your page itself. When the quota is used up, the page blocks Google, or the test times out, the report says why. Field data also needs enough Chrome visitors: small sites may show lab results only, or the whole-site figures instead of the single URL.
Does the checker see content added by JavaScript?
No. It analyses the HTML your server sends, without running scripts, which is also what many crawlers and AI assistants read first. If your titles, headings or text only appear after client-side rendering, they will be missing here. Server-side rendering or static generation solves that and usually improves Largest Contentful Paint as well.
Can I check a page on localhost or behind a login?
No. For security the server refuses localhost, private network ranges and addresses that resolve to them, and it can't sign in to anything. Pages behind a login, a paywall or a bot challenge return the login or challenge page instead. Check a public staging URL, or temporarily allow our user agent, ToolsSEOChecker, in your firewall.

Related tools

All developer tools

Open Graph & meta tag previewer

Preview links on Google, Facebook, X, LinkedIn and Slack

Robots.txt & sitemap generator

robots.txt builder and tester, XML sitemaps

What's my IP & DNS lookup

Your public IP address and DNS records for any domain

Uptime monitor

Know when your website goes down