Free Website Audit Report Guide

The AITasker free website audit is built to show the evidence behind the headline score. It combines the audited page HTML, PageSpeed data, conversion signals, SEO basics, accessibility checks, content structure, and model analysis into one report.

Overall Score and Grade

The overall score is normalized to a 0-100 scale and paired with a grade.

Grade	Score range	Meaning
A	80-100	Strong. The page has a healthy base with only targeted improvements.
B	60-79	Good, with important fixes likely to improve conversion or discoverability.
C	40-59	Mixed. Several measured issues are probably limiting the page.
D	20-39	Weak. Priority fixes are needed before the page can perform reliably.
F	0-19	Critical. The page likely has major trust, speed, SEO, or conversion blockers.

Score Breakdown

The report breaks the score into seven dimensions:

Dimension	What it checks
Technical Health	HTTPS, canonical tag, favicon, crawl metadata, HTML availability
Performance	Mobile and desktop Lighthouse score, LCP, CLS, TBT, PageSpeed opportunities
Mobile Readiness	Viewport metadata, render path, mobile performance context
SEO Basics	Title tag, meta description, H1 count, social preview tags, structured data
Accessibility	Image alt coverage and semantic readability signals
CRO	CTA buttons, lead-capture elements, and visible trust proof
Content Quality	Visible word count, heading depth, and page-copy structure

Each drilldown explains what was measured, how to interpret the score, why the area matters, and which signals were captured.

Signal Inventory

The Signal Inventory is the compact evidence table behind the report. It shows the category, signal, value, status, source, and explanation for every measured check.

Use this table when you want to verify a finding. For example, if the report says meta description is missing, the Signal Inventory shows the exact SEO Basics row that produced that conclusion.

Findings

Findings are grouped by category and include:

• Severity
• Source
• Evidence
• Why it matters
• Recommended fix

Measured findings come from deterministic checks against the page and PageSpeed payload. Model-analysis findings are kept when they add useful interpretation, but they are labelled as analysis rather than confirmed measurement.

Recommendations

Recommendations are generated from the findings first, so the action plan traces back to evidence. When a recommendation maps cleanly to an AITasker task type, the report can show a task action. If the mapping is not specific enough, the recommendation remains as guidance instead of showing a generic task button.

Raw Captured Data

The Raw Captured Data section keeps the underlying payload visible:

• Scrape metadata
• Page signals extracted from HTML
• Raw mobile PageSpeed data
• Raw desktop PageSpeed data
• Structured model analysis before normalization

This makes the report auditable. If a top-level score looks surprising, you can inspect the exact data the audit used.

Downloads

When files are generated, downloads include the DOCX report and any CSV evidence exports. The CSV evidence file mirrors the Signal Inventory so teams can sort, filter, and hand off fixes without scraping the report UI.