Website Audit: PageSpeed, Core Web Vitals & WCAG Accessibility

Audit every page of a website in one run: Google PageSpeed Insights (Lighthouse) scores and real-user Core Web Vitals, plus a full WCAG 2.2 accessibility audit that lists each failing element with its fix, WCAG success criterion and EN 301 549 clause. You get a dataset with one item per page and a client-ready report (HTML and PDF).

Give it page URLs or a sitemap. For each page it:

• asks Google's official PageSpeed Insights API for the Lighthouse scores (performance, accessibility, best practices, SEO), lab timings (LCP, CLS, TBT, FCP, Speed Index, server response) and real-user Core Web Vitals from the Chrome UX Report (LCP, INP, CLS, with Google's fast/average/slow verdict);
• opens the page in Chrome and runs axe-core with the WCAG 2.2, 2.1 or 2.0 A/AA rules, returning every failing element with the rule, impact (critical, serious, moderate, minor), how to fix it, the WCAG success criteria and the EN 301 549 clauses used for the European Accessibility Act;
• adds a site-wide summary: average scores, Core Web Vitals verdicts, and the accessibility failures that appear on the most pages.

Why this one

PageSpeed tools report Lighthouse's accessibility score. That score comes from a subset of checks and doesn't tell you which elements fail or how to fix them. This Actor runs the full axe-core WCAG rule set on every page (the engine behind most accessibility testing tools, also used by our Website Audit browser extension for Chrome and Edge) next to the speed audit. Agencies, developers and site owners get both findings, per element, in one run and one report.

Input

Field	What it does
Pages	Page URLs to audit.
Sitemaps	sitemap.xml, a sitemap index or .xml.gz; their pages are added after the ones above.
Maximum pages	Stops after this many pages (default 50).
Speed / Device	PageSpeed Insights on mobile, desktop or both.
Accessibility / WCAG version	The full WCAG audit, against WCAG 2.2 AA (default), 2.1 AA or 2.0 AA.
Include axe best practices	Also reports axe-core's best-practice rules, which go beyond WCAG.
Elements listed per issue	How many failing elements each issue lists (counts always include all).
PDF report	Saves the report as a PDF too.
Report title, Your brand name, Your logo	White-label client report: your title, name and logo at the top of the report.
Remove the "Made with Website Audit" line	Leaves out our credit line. No extra charge.
Compare with the previous audit / History name	Remembers each page's last audit in your own Apify storage and shows what is new and what was fixed since then, plus performance score changes. Run it on a schedule to track progress; the first run is the baseline.
Your PageSpeed Insights API key	Optional; speed checks use our key by default.

Example input:

{
  "sitemaps": ["https://example.com/sitemap.xml"],
  "maxPages": 100,
  "strategy": "both",
  "standard": "wcag22aa"
}

Output

One dataset item per page (the Overview view shows the scores and issue counts as a table):

{
  "url": "https://example.com/pricing",
  "title": "Pricing",
  "speed": {
    "mobile": {
      "performance": 87, "accessibility": 95, "bestPractices": 100, "seo": 92,
      "lab": { "lcpMs": 2346, "cls": 0.012, "tbtMs": 120, "fcpMs": 1235, "speedIndexMs": 3456, "ttfbMs": 210 },
      "field": { "scope": "page", "overall": "FAST", "lcpMs": 2100, "inpMs": 180, "cls": 0.05 }
    }
  },
  "accessibility": {
    "standard": "WCAG 2.2 AA",
    "counts": { "critical": 2, "serious": 4, "moderate": 0, "minor": 0, "needsReview": 1, "elements": 46 },
    "issues": [
      {
        "ruleId": "image-alt", "kind": "violation", "impact": "critical",
        "help": "Images must have alternative text",
        "wcag": ["1.1.1"], "level": "A", "en301549": ["9.1.1.1"], "elements": 33,
        "nodes": [{ "target": "#logo", "html": "<img id=\"logo\" src=\"/logo.png\">", "summary": "Fix any of the following: Element does not have an alt attribute ..." }]
      }
    ]
  },
  "errors": []
}

In the run's key-value store:

• REPORT: the report as an HTML page, ready to send or print;
• REPORT.pdf: the same report as a PDF (when PDF report is on);
• OUTPUT: the summary as JSON (averages, Core Web Vitals verdicts, the most common failures).

Pricing

Pay per event:

• Page audited: charged once per page that returned results, whichever checks you turned on. Pages that fail to load (for example HTTP 404) are listed with the error and not charged.
• PDF report: charged once per run when the PDF is saved.
• A small start fee per run, set by Apify.

The Maximum cost per run you set in Apify is respected: the run stops before going over it.

Good to know

• Automated checks find a subset of WCAG issues. Manual testing is still needed (keyboard use, screen readers, meaning of content). Issues marked check by hand (needs-review) could not be decided automatically. A page without failures is not necessarily accessible, and this audit does not certify compliance.
• Real-user data comes from Google's Chrome UX Report (last 28 days). Pages with too few visits show the whole site's data ("scope": "origin") or none.
• Pages are loaded like a visitor's browser would load them, without logging in. The audit only reads pages; it doesn't change anything.
• Audit only sites you're allowed to test. Very large audits (thousands of pages a day) should use your own free PageSpeed Insights key. On the free Apify plan, runs that use our key for speed checks cover up to 10 pages; paid plans and runs with your own key have no such limit.

FAQ

Can I audit pages behind a login? Not yet; public pages only.

Which axe-core version? 4.14, as in our browser extension.

Can I hand the report to clients as my own? Yes: set your brand name and logo, a report title, and remove the credit line.

Can it show what changed since the last audit? Yes: turn on Compare with the previous audit and run it on a schedule. The report and every dataset item show new, fixed and remaining failures and performance changes.

Can I run it on a schedule? Yes, with Apify Schedules; each run produces its own report.

Support: support+siteaudit@iiclabs.com. If something looks wrong, include the run ID. If the audit helped you, a rating on this page helps others find it.