Free tool · No sign-up · Shareable report
Audit any website in about five seconds
One report covering what search engines read, how secure the connection is, how fast the server answers, and whether the legal pages a business site needs are there. Every problem comes with the fix.
What the audit checks
SEO health
- Meta title and description
- H1-H6 heading structure
- OpenGraph and Twitter cards
- Schema.org structured data
- Canonical, robots and sitemap
- Content in the HTML, not only in JavaScript
Technical security
- SSL certificate: trust, expiry, TLS version
- HTTPS and the http:// redirect
- HSTS, CSP and clickjacking headers
- Insecure (mixed) content
- Cookie flags and version banners
Speed & performance
- Server response time (TTFB)
- HTML payload weight and compression
- Redirect chain
- Render-blocking scripts
- Image formats, lazy loading and dimensions
Trust & legal
- Privacy policy and terms of service
- Cookie policy and refund policy
- Trackers that load without consent
- Ways to contact the business
- Who is behind the site
How the score works
Every check scores between 0 and 1. Yes-or-no checks score 0 or 1, and 0.5 when something is present but not right. Measured values, like server response time and page weight, are scored on the same log-normal curve Google Lighthouse uses, so a slightly slow server loses a little rather than everything. Each category is the weighted average of its checks, and the overall score is the weighted average of the categories:
| Category | Weight | Heaviest checks |
|---|---|---|
| Technical security | 30% | HTTPS, a trusted and unexpired certificate, the http:// redirect, HSTS |
| SEO health | 30% | Not blocked from indexing, a mobile viewport, the meta title, one H1 |
| Speed & performance | 25% | Server response time, render-blocking scripts, compression, HTML weight |
| Trust & legal | 15% | A privacy policy, terms of service, consent before tracking, contact routes |
90 or above is excellent, 80 to 89 good, 50 to 79 needs work, and under 50 poor. If part of a site can't be measured, for example because a firewall answered instead of the site, that category is left out of the average rather than counted as zero, and the report says so.
Questions about the audit
Is the audit really free?
Yes. No account, no card and no email address. You can run a few audits every ten minutes; the limit keeps the tool from being used to hammer other people's sites.
What do you store?
The address you audited and the public findings about it, for 90 days, so the share link keeps working. We don't store who ran the audit: no account, no IP address, no email.
Why does my report say part of the site couldn't be measured?
Many sites sit behind a firewall such as Cloudflare or Akamai that challenges automated visitors. Our auditor says who it is and doesn't try to get past these checks, because whether to let it in is the site owner's decision. The report scores what it could see and says what it couldn't. If it's your site, allow the user agent PipeLineHubAudit in your firewall rules and run it again.
Can I audit a competitor's website?
Yes. The audit reads one public page the way a visitor's browser would, plus robots.txt, the sitemap and a couple of legal page addresses. Any site can opt out by adding "User-agent: PipeLineHubAudit" and "Disallow: /" to its robots.txt, and we honour it.
How is this different from Google Lighthouse or PageSpeed Insights?
Lighthouse loads the page in a browser and measures how it renders: largest paint, layout shift, interactivity. This audit reads what the server sends (the HTML, the headers and the certificate), which is what search engines, security scanners and payment providers' reviewers look at first. They answer different questions, and the scoring here borrows Lighthouse's method for measured values.
How is it different from the free website check?
The free website check is a ten-second plain-English health check for business owners. The audit goes deeper and more technical: every SEO tag, the certificate, the security headers, render-blocking resources, trackers and consent, and the legal pages, in a report you can share.
My site scored under 80. Where do I start?
With the first item under “Critical fixes required”. The list is ordered by severity, and each item says what we found and how to fix it. Most of the heavy ones (HTTPS, a missing viewport, noindex, no privacy policy) are quick changes that move the score a long way.