How to Audit Any Website in 15 Minutes (Structure, Images, Links, Headers and History)

Full audits take days. Most of the time you need something smaller: a quick, repeatable pass that catches the obvious problems on a page before it ships, or before you send a client a quote. This is the 15-minute routine we use, built on two free extensions — Web Developer Tools for the page itself and Web Archive Viewer for its history.

Minutes 0–3: Structure and headings

• Outline headings. One H1 that matches the page's purpose? No skipped levels? Headings used for content, not styling?
• View the document outline report. Does the outline read like a table of contents? If not, neither search engines nor screen-reader users can navigate it.
• Disable all styles. With CSS off, the content should still read in a sensible order. Hidden text and odd ordering show up immediately.

Minutes 3–6: Images and media

• Outline images missing alt text and decide which need it (informative) and which should have empty alt (decorative).
• Show image dimensions. Look for oversized images scaled down in the browser — a common, easy performance win.
• Find broken images. Anything broken on launch day reaches every visitor.

Minutes 6–9: Forms and interaction

• Flag inputs without labels — an accessibility failure and a usability one.
• Populate forms with sample data, submit, and check validation messages and the success state.
• Disable JavaScript for the site and reload: does the core content still appear? Does the form at least explain that it needs scripts?

Minutes 9–11: Headers, cookies and links

• Response headers report: caching (cache-control), security (strict-transport-security, content-security-policy, x-content-type-options) and the right content type.
• Cookies: what's set before consent? Are session cookies Secure and HttpOnly?
• Outline external links and spot-check a few. For a long page, run all its links through a bulk dead-link check.

Minutes 11–13: Layout and responsiveness

• Resize to common phone, tablet and laptop widths. Watch for horizontal scrolling, overlapping elements and tap targets that are too small.
• Outline positioned elements to find the sticky header or popup that covers content on small screens.
• Use the ruler to check spacing and alignment against the design.

Minutes 13–15: History check

This is the step most audits skip, and it's often the most revealing. Open Web Archive Viewer on the page and look at its history:

• Has the URL existed before? A long capture history means backlinks and expectations; a brand-new URL replacing an old one needs a redirect.
• What did the previous version say? Compare the last capture with the new page. Missing sections, headings or internal links are classic causes of ranking drops — see historical SEO analysis.
• Is the old site's URL structure covered? For a redesign, list every archived URL on the domain and make sure each one still resolves. Our guide on finding every archived URL explains how.
• Archive the launch version. Use Archive now so you have a timestamped record of what went live.

Turn it into a checklist

For deeper dives into each area, the Web Developer Tools blog has full checklists for accessibility, performance, security and technical SEO.

FAQ