Find what's hurting your growth. Get the exact fix.

50 specific, actionable fixes for speed, accessibility, security, and SEO.

Not just scores. Not vague suggestions. Specific recommendations you can actually implement.

Everything you should check
before you ship

You know the drill. Before launch, you should check the Lighthouse score. Verify security headers are set. Test Core Web Vitals. Validate schema markup. Scan for accessibility issues. Check caching headers. Test image optimisation.

But you're busy. So you check some of it, cross your fingers, and ship. Then hope nothing's broken when Google recrawls your site.

GuardianScan runs all 50 checks in 45 seconds. Before launch. After deploys. Before that A/B test goes live. Whenever you need to know you haven't broken something.

Modern web standards matter. Google ranks fast sites higher. Accessible sites reach more users. Secure sites build trust. Get these right, and you see it in your traffic and conversions.

Scans live websites via HTTP. Won't catch everything - automated accessibility checks find about 70% of issues, and it can't see your source code or private repos. But it catches the common stuff that costs you rankings and conversions.

If you build websites or care about how yours performs, this will save you time.

What gets scanned

50 automated checks across 6 categories

Modern Standards

Core Web Vitals, modern framework patterns, image optimisation. Checks if you're using current web standards or legacy patterns.

Performance

LCP under 2.5s, TBT under 200ms, CLS under 0.1. Google uses Core Web Vitals as a ranking factor. Slow sites drop in search results.

SEO & AI Search

Meta tags, schema markup, XML sitemaps, semantic HTML. Checks schema.org and semantic structure that AI search engines use to understand your content.

Security

HTTPS config, security headers, CSP policies, SSL certificates. Modern browsers show warnings on insecure sites. Users leave before they see your content.

Accessibility

WCAG 2.2 Level AA compliance, keyboard navigation, screen reader support, colour contrast. 15% of people need accessibility features to use websites. In the UK, inaccessible sites violate the Equality Act 2010.

Code Quality

Total bundle size, render-blocking resources, console errors, image format checks. Developer-focused checks.

Scan. See. Fix.

Enter a URL
Any public website. Yours, a client's, a competitor's. Staging sites with accessible URLs.
We scan it
50 automated checks run in parallel. Takes about 45 seconds for a typical site.
You get a report
Overall score, issues by category, specific fixes. Shareable, exportable reports.

Made for people who build websites

Agencies

Scan before presenting work. Catch issues before the client does - or before their 'technical friend' runs Lighthouse and questions your work. One missed security header can cost you a client. Export professional reports, bill for 'GuardianScan compliance' as a deliverable.

Freelancers

Quick health check before taking on a project. Know what you're dealing with upfront. Scan staging sites pre-launch to catch regressions. Try it free, upgrade for unlimited client work.

In-house teams

Scan after every deploy. Catch regressions before users do. Track performance trends over time. Share reports with stakeholders to show technical health improvements.

What we don't check

We're transparent about our limitations. Here's what GuardianScan can't do.

Source code or private repositories

We scan live websites via HTTP/HTTPS requests. We can't access your codebase, Git repos, or review application logic.

Backend security vulnerabilities

We check security headers and HTTPS configuration, but can't test for SQL injection, authentication flaws, or server-side vulnerabilities.

Business logic bugs

We can't test if your checkout process works or if forms submit correctly. We check technical standards, not functionality.

Full WCAG 2.2 compliance

Automated accessibility checks catch approximately 70% of issues. Manual testing with assistive technologies is still required for complete compliance.

Frequently Asked Questions

Everything you need to know about GuardianScan

What does GuardianScan check?

50+ checks across 6 categories. Performance covers Core Web Vitals (LCP, TBT, CLS). Security checks HTTPS, headers, and CSP policies. Accessibility tests WCAG 2.2 Level AA compliance. SEO checks meta tags, schema markup, and semantic HTML. Modern Standards looks at framework patterns and optimisations. Code Quality covers bundle size and console errors.

How long does a scan take?

About 45 seconds for most sites. The 50 checks run in parallel for speed. Scan duration may vary based on your site's performance and size.

Is there a free tier?

Yes. Free accounts get one complimentary scan delivered as a PDF report to your email. Enter a URL to get a full 50-point report. For unlimited scans, full dashboard access, scan history, and detailed reports, upgrade to Professional.

How much does it cost?

£24/month for Professional (unlimited scans, full dashboard, scan history). Free tier gets one scan delivered as a PDF report via email. Launching 1st November 2025.

What makes this different from Lighthouse?

We run Lighthouse for performance and accessibility scoring, then add security header checks, SEO validation, and framework-specific audits. Lighthouse covers part of the picture. We check everything that matters for modern websites - security, SEO, framework optimisation - in one scan with stored history.

Can it scan private or staging sites?

Yes, as long as the URL is accessible over HTTP/HTTPS. We scan via web requests, so the site needs to be reachable from the internet. We can't analyse source code or private repositories.

What's checked for accessibility?

WCAG 2.2 Level AA compliance including keyboard navigation, screen reader support, colour contrast (4.5:1 minimum), touch targets (48px minimum), and semantic HTML. Automated checks catch about 70% of issues - manual testing still needed for full compliance.

Does it work for AI search optimisation?

Yes. We check schema.org markup and semantic HTML structure that AI search engines use to parse and understand your content.

How often should I scan my site?

Before launch, after major deploys, and whenever something feels off. Many developers run weekly scans to catch issues early. Post-launch, we'll offer automated recurring scans.