The report is designed to move from summary to evidence. Start at the top for the business-level story, then use the findings list when you are ready to fix specific issues.
Executive summary
The executive summary explains what PageLens found in plain language. It highlights the most important themes and the likely impact on users, buyers, or reviewers.
Score and categories
The score is a compact health signal across the audit categories PageLens checks. Use it to compare scans over time, but do not treat it as the only thing that matters. A single high-severity issue can be more important than several low-severity notes.
Findings
Findings are the work queue. Each finding includes severity, category, page context, and evidence. High and critical findings should normally be reviewed first.
Useful fields to check:
- the affected URL
- the viewport, if you scanned desktop and mobile
- the evidence or screenshot
- the recommendation
- the category and rule identifier
Persona or preset views
If you chose a preset, the report may emphasize findings through that lens. For example, a launch-readiness report will frame issues differently from a conversion-focused report.
Performance details
Performance metrics show how the scan ran and where time was spent. These are most useful when comparing repeat scans or debugging a worker issue with support.
Turn the report into action
Pick a small batch of high-impact findings, fix them, and re-scan the affected pages. If a finding looks wrong or needs interpretation, open a support ticket and attach the scan.