Why it matters
Most page problems are visible in the HTML before anything loads: a missing title, an image without alt text, a script blocking the first paint, a lazy-loaded hero image hurting Largest Contentful Paint. Online audit tools need a public URL, which rules out staging sites and pages behind a login.
This auditor reads pasted HTML in an inert document, so no scripts run and nothing is fetched, and checks around 40 rules drawn from Google's guidance and WCAG. Use it on a draft, a staging page or a template before it goes live.
How it works
- InputThe HTML source of a page
- In your browserChecked for 30 SEO and accessibility basics
- OutputA score, findings and a checklist
Where it fits in a designer's workflow
- Plan
- Design
- Build
- Test
- Launch
By the numbers
Show the numbers as a table
| Page | Title characters | Description characters |
|---|---|---|
| apps.html | 44 | 150 |
| articles.html | 59 | 147 |
| contact.html | 54 | 149 |
| index.html | 53 | 151 |
| privacy.html | 28 | 156 |
| projects.html | 46 | 147 |
| swift.html | 43 | 150 |
| terms.html | 26 | 147 |
| tools.html | 59 | 138 |
| what-i-do.html | 53 | 152 |
How to use it
- Paste the page's HTML (View Source, or the Elements panel for the final page), or open a file.
- Read the score for each area.
- Work through the failing and warning items.
- Download the checklist as Markdown.
FAQ
Is this the same as Lighthouse?
No. Lighthouse loads the page and measures it. This reads the HTML only, so it can't time anything, but it works on any HTML, including drafts.
Does it run my page's scripts?
No. Scripts are disabled and nothing is fetched.
How are the scores worked out?
Each check has a weight. Passing earns its full weight, a warning half, a failure nothing, and the score is the percentage of the total.
Why is the result different after JavaScript runs?
Frameworks often add titles and content in the browser. Paste the HTML from the Elements panel to audit the rendered page.
