Each audit returns a list of findings tagged with 1 of 5 severities: critical, high, medium, low, info. Every finding ships with a 1-sentence fix hint. The 2 highest tiers are what your outreach email should quote first.

What counts as a finding

A finding is a single rule that failed on the page. We run about 60 rules per audit. Each rule sits in 1 of the 5 groups the score is built from. Critical and high findings are the ones a business owner grasps in a sentence. Medium and low ones are for whoever does the work.

Think of it like a dentist's chart. Cavities (critical) get the call. Plaque buildup (medium) gets the next cleaning.

How LemAudit grades severity

The severity table lives in src/config/audit-checks.ts. A few examples:

• 🔴 Critical — no HTTPS, noindex on homepage, broken meta title.
• 🟠 High — LCP over 4s, no H1, missing structured data, blocked robots.
• 🟡 Medium — missing alt text, redirect chain over 3 hops, unoptimised images.
• 🔵 Low — duplicate meta description, missing favicon, no Open Graph image.
• ℹ️ Info — security headers like CSP not set.

Each finding card on the lead detail page shows the rule name, the value that failed, the limit it should meet, and a fix hint. The outreach email writer takes the top 3 critical and high findings and builds the email around them.

Worked example

A used-car dealer site returned 4 critical findings: no HTTPS, missing meta description, robots.txt blocking the sitemap, and a 1.2MB hero image. The agency's first outreach email led with the HTTPS one because it reads as a trust risk to a buyer. Reply rate that week: 22%, vs the agency's 9% baseline on generic cold mail.

When this isn't right

The audit only sees what the public page returns. JavaScript-only content, gated docs, and tracking-blocker bypasses can produce false positives. Treat any single audit as evidence, not proof — confirm with browser devtools before claiming "your site is broken" in a sales call.