Skip to content

Website Page Audit

Short answer

Deep comprehensive audit of ONE page — SEO, accessibility, performance, security and Core Web Vitals in a single report.

What it does not do: It audits one page per run, not the whole site, and its accessibility checks are automated, so on their own they cannot confirm WCAG or EAA compliance.

Example:

Full URL including https://.

Example: https://example.com

What It Does

Loads one page in a real browser and runs up to 133 checks across SEO basics, speed, security, mobile, content, accessibility, links and AI search. You get an overall score, a score for each category and a pass, warning or fail result for every check, with advice on how to fix it.

Why It Matters

Many site problems are easy to miss by eye: a missing canonical tag, a weak security header, an image without alt text, a slow first response. Checking them in one pass shows what to fix first, and running the audit again after a release shows whether anything broke.

How It Works

  1. Enter a page URL and start the audit

  2. We load the page in a headless browser and read its response headers; if rendering fails, we use the plain HTML instead

  3. Run the checks — up to 133, depending on what the page contains

  4. Return the overall score, the category scores and every check with its fix

Sample input + output

INPUT
url: https://rankproof.eu/tools
OUTPUT
✓ title: present (54 chars)            OK
✓ meta description: present (147)      OK
✓ canonical: self-referencing          OK
✓ h1 count: 1                          OK
✓ open graph: complete                 OK
✓ schema.org: 4 blocks                 OK
✓ HTTPS + HSTS                         OK
✓ mobile-responsive                    OK

Score: 92/100 — 0 critical issues

How to read the result

Overall score (92/100 in the sample)
Combines the category scores into one number. A failed check lowers its category more than a warning, and checks that do not apply to the page are left out. The AI search checks are shown separately and do not change it. Use it to compare the same page before and after a change, not to rank different sites.
Categories
Checks are grouped into common SEO issues, speed, server and security, mobile, advanced SEO, accessibility, links and AI search readiness. Each group shows its own score and how many checks passed, warned or failed, so a weak area stands out even when the overall score looks fine.
Passed, warning, failed
Every check ends in one of three results. Failed, marked Critical, means the page clearly breaks a rule — for example no viewport tag or a relative canonical URL. Warning means something is missing or could not be verified, such as the HSTS header. A separate high, medium or low impact label tells you how much each one matters.
Fix these first
Above the full list, the report picks the three problems with the highest impact. Each check opens a panel that explains what it tests, why it matters, what a good result looks like and how to fix it, with a before-and-after code example where one helps.
Measured values
Where a check measures something, the report shows what it found: the first-response time in milliseconds, the canonical URL, the number of images without alt text. Confirm the value on your own page before you change anything.
Speed data
The response time and headers come from our own request to the page. The Core Web Vitals checks use real-visitor data from the Chrome UX Report when the site has enough traffic, and say so when it does not.
WCAG and EAA references
Accessibility findings name the WCAG 2.1 success criterion they test and the European Accessibility Act requirement it belongs to, with links to both. An automated check covers only part of a criterion: a failure is a real defect, a pass is not proof of compliance.
Visual preview
Desktop and mobile screenshots of the page as the audit rendered it. If they show a cookie banner or an error page instead of your content, the results describe that screen, so fix access first and run the audit again.

Who Uses This

  • Agency account manager

    Audit a prospect's homepage and walk them through the failed checks on the first call.

  • Developer

    Audit a page before and after a deploy to catch regressions.

  • In-house SEO

    After a CMS change, audit one page per template and fix the new failures first.

Common problems and how to fix them

  1. The canonical tag is missing or relative

    Add one canonical link to the page's <head> with the full https:// address of the version you want indexed. Google asks for absolute URLs here, so a relative path is reported as a failure; a missing tag is a warning.

    <link rel="canonical" href="https://example.com/guides/page-speed">

  2. No HSTS header

    Once every page works over HTTPS, send the Strict-Transport-Security header on HTTPS responses so browsers stop trying plain HTTP first. Start with a short max-age while you test, then raise it to a year, and add includeSubDomains only when every subdomain serves HTTPS.

    Strict-Transport-Security: max-age=31536000; includeSubDomains

  3. Responses are not compressed

    Turn on Brotli or gzip for HTML, CSS, JavaScript, JSON and SVG in your server or CDN. Text shrinks to a fraction of its size, so pages arrive sooner on slow connections. Afterwards, check in your browser's developer tools that the Content-Encoding response header shows br or gzip.

    # nginx: HTML is compressed once gzip is on
gzip on;
gzip_types text/css application/javascript application/json image/svg+xml;

  4. The first response is slow

    The audit warns when the first byte takes more than 600 ms and fails above 1.2 seconds. Cache whole pages that are the same for every visitor, serve them from a CDN near your visitors, and look for slow database queries or plugins on pages that are built per request.

  5. Images without alt text

    Give each informative image a short alt text that says what it shows or does. Give purely decorative images an empty alt so screen readers skip them, and give an image that is a link alt text naming where the link goes.

    <img src="/signups.png" alt="Bar chart: sign-ups doubled from March to June">
<img src="/divider.svg" alt="">

  6. No viewport tag or no page language

    Without a viewport tag, phones show a shrunken desktop layout; without a lang attribute, screen readers can read the text with the wrong pronunciation. Both are a single line in the page template.

    <html lang="en">
<head>
  <meta name="viewport" content="width=device-width, initial-scale=1">

Frequently Asked Questions

How is the overall score calculated?
Each category gets a score from its own checks, and the overall score combines the categories. Failed checks lower a category more than warnings. The AI-search checks are reported separately and do not change the overall score.
Does it crawl the whole site?
No. It audits one page per run. Run it again for each page you want to check.
Does it handle pages built with JavaScript?
Yes. The page is rendered in a headless browser, so content added by scripts is checked. If rendering fails, the audit uses the raw HTML and some checks may not run.
Can I save or share the report?
Each audit has its own report page. You can share its link, or print it and save it as a PDF from your browser.
How many audits can I run?
As many pages as you need, up to a daily limit per visitor that keeps the audit free.

Sources

The documentation this tool and the explanations on this page are based on.

Free tools on this topic

Guides on this topic

Related Tools in SEO Analysis

View all SEO Analysis tools