Website Audit Report: Present Findings as a Page, Not a PDF

Turn a Lighthouse report website into a decision page that connects each score to evidence, an owner, and the next action.

In short

Start with the page and device you tested, then show the four Lighthouse category scores.

Put the urgent findings ahead of the score explanation.

For every finding, include the evidence, owner, and next action.

Keep untested pages and checks visible so a short audit is not mistaken for full coverage.

A website audit report should tell a reader what was checked, what was found, why it matters, and what happens next. A row of scores does not finish that job. The report still needs the affected page, evidence from the audit, a priority, an owner, and a retest condition.

We rebuilt the existing guide around a fictional Northstar Bakery audit. The example is not a live scan and does not use a real business. It starts with sample Lighthouse category scores, turns two sample audit flags into launch actions, keeps one editorial note separate, and names the parts that were not checked.

How do you turn a Lighthouse report into a website audit report?

Use one page for the handoff. Put the tested route and device near the top, follow with the decision, and then show findings in action order. The finished example can be downloaded and adapted without copying any fictional score into a real report.

Download the complete fictional audit example

1. Put the report and the visible result side by side

The HTML stays in one document. In NOS Code view, the source and the rendered page are visible together, so the report writer can check whether a changed label, score, or finding appears in the page.

NOS Code view showing the fictional Lighthouse audit HTML and its rendered report
1. The complete fictional audit in Code view, with the rendered report beside the code it.

2. Lead with the decision, not a score verdict

The first screen names the fictional scope and shows four sample category scores. It then asks for two launch-blocking fixes and a retest of the same mobile route. The 58 is not presented as a diagnosis by itself.

Chrome's Lighthouse documentation says each category supplies a score and points to potential issues and improvements. Its performance scoring guide also warns that the score can vary with test conditions. That is why this report keeps the route, device, evidence, and retest instruction beside the numbers.

NOS View mode showing sample Lighthouse scores and a decision at the top of the audit
2. The reader sees scope, scores, and the requested decision on the first screen.

3. Share the report as a read-only page

The current Share panel says that anyone with the link can read the page without signing in and cannot edit it. It also says search indexing is off unless the page is made public on the web. Those settings suit a review link, but they do not turn confidential material into safe public content.

NOS Share panel for the fictional website audit report
3. The Share panel shows the reader permission and the link used for this review.

What should the first screen of a Lighthouse report website show?

Show enough context to stop a score from floating free of the test. The example identifies a fictional home-page mobile snapshot, labels every number as sample data, and puts the requested decision immediately below the scores.

Shared fictional website audit report on a 1280 by 800 desktop screen
4. The shared report fits a desktop screen without shrinking a fixed-width table.

After the summary, each finding answers four questions:

  • What was observed? Quote or name the specific audit evidence.
  • Why is it here? Distinguish a Lighthouse flag from an editorial review note.
  • Who acts? Assign a role or named team, not a vague “we.”
  • What closes it? State the change and the retest or review needed.

How do you prioritize Lighthouse findings?

Do not sort only by the lowest category score. Start with the page's purpose, the evidence inside the failed audits, and the work that blocks the next release or decision. In this fictional example, the hero image and first-render stylesheet are grouped under “Fix first.” The home-page description is labeled “Later” and explicitly marked as an editorial note rather than a Lighthouse failure.

The filter changes only what is visible. It does not delete a finding or claim that the work is done.

Fictional audit filtered to show the two fix first findings
5. “Fix first 2” leaves the two launch actions visible and hides the later editorial note.

Can you import a Lighthouse JSON report?

Lighthouse can save a report as JSON. The fictional page includes a small importer for the four category scores so the summary can be updated without retyping each number. It does not import audit evidence, choose priorities, or write the recommendations. Those decisions still require reading the report and checking the site.

Fictional audit showing a successful import message below valid Lighthouse category JSON
6. A valid four-category snapshot updates the sample and leaves a reminder to review evidence and actions.
Fictional audit showing updated sample Lighthouse scores after a valid import
7. The same browser session shows the imported sample scores at the top of the report.

What happens when the Lighthouse JSON is incomplete?

We removed three categories from the sample input and tried the import again. The page rejected it with “Four category scores are required.” It did not turn missing values into zeroes or present a partial set as complete.

Fictional audit rejecting incomplete Lighthouse JSON with a four category scores required error
8. The tested failure path keeps the missing-category problem visible.

Completed result: the example now covers a successful import, an incomplete-input failure, a priority filter, a mobile share view, and the report's limits. It still does not claim that sample scores or fictional findings came from a live bakery site.

What should remain from the full Lighthouse report?

Keep the original JSON or Lighthouse report with the work record. The short page is a review copy, not a replacement for the detailed audit. For each action, retain the audit name, affected page, evidence, test mode, and the condition for retesting. If a recommendation comes from a human review rather than Lighthouse, label it that way.

Also keep the limits close to the findings. Our example covers one fictional mobile home-page run. It does not cover desktop, checkout, login, or a human accessibility review. The separate website accessibility validator guide explains why an automated result needs a broader review. For recurring search reporting, use the structure in the SEO report template. If the main problem is presenting client work as a responsive page, continue with HTML for client reports.

When not to do this

  • Do not publish credentials, private customer information, unpublished security findings, or internal URLs in a share page.
  • Do not call one Lighthouse run a complete website audit when other routes, devices, flows, or human checks were outside scope.
  • Do not import a score and invent the cause. Read the failed audit evidence before assigning a fix.
  • Do not use a review page when the organization requires a signed document, ticketing record, or controlled security report.

Using NOS for the review page

NOS Workspace was used here to hold the self-contained HTML, compare the code with the visible result, and create the tested read-only link. A writer can revise the existing page instead of sending another attachment. Check the current pricing page if plan limits matter; this guide does not state a price.

Questions people ask

What should a website audit report include?

Include the tested page and device, a short decision summary, findings with evidence, priority, owner and next action, plus a clear list of what was not checked.

Is a Lighthouse score enough for a website audit?

No. A category score is a starting signal. Read the failed audits, record the affected page and evidence, and state what must change and how it will be retested.

Can I import a Lighthouse JSON file into this example?

The downloadable fictional example accepts the four category scores used in its summary. It does not import audit details or choose fixes, owners or priorities for you.

Why did the import reject my JSON?

The tested example requires numeric scores for performance, accessibility, best practices and SEO. If one is missing, it shows an error instead of treating the report as complete.

Can readers edit a NOS share link?

The Share panel tested for this example says people with the link can read without signing in and cannot edit the page. Review the panel before sending because sharing settings can change.

Keep reading