Home / Example reports

See what a useful report looks like.

What needs attention. Why it matters. What to do next.

Illustrative examples, not customer results. All businesses and findings below are fictional. Images are browser captures of a controlled demo, not evidence from a client website.

Free checkReviewed auditMonthly QA

Free automated check / Illustrative sample

Fern & Forage

Public website check / fernandforage.example

Check my website

Two things to fix before your next campaign

The example contact page is too wide for a phone, and its email link is incomplete. Fix the email link first so visitors have a working way to get in touch.

2 medium-priority findings. Automated checks only; no human review or whole-site assurance.

Public pages sampled
3
Internal links checked
7
Browser views captured
6
Example findings
2
What the example covers, including checks without a finding

Illustrative scope: home, about and contact pages; desktop and mobile views. Counts describe this sample, not a live scan.

  • Availability: three sampled pages load; seven internal links return usable responses.
  • Mobile layout: contact page overflow needs attention.
  • Accessibility: no issue illustrated for sampled labels, image alternatives or text contrast. Not an accessibility certification.
  • Contact and forms: incomplete email destination; fields inspected without submitting a form.
  • Browser performance: no lab-performance finding illustrated. Real results depend on the page and test conditions.
  • Security headers: no header finding illustrated. Not a penetration test.

Not tested: sign-in, checkout, form delivery, every page or a completed customer journey. A clean sampled check does not prove a website is defect-free.

01 / Contact links

Email link has an incomplete address

Medium

What is wrong

The destination is mailto:hello@fernandforage, without a complete email domain.

Why it matters

A visitor may not be able to send an enquiry using this link.

Recommended action

Use the business's confirmed email address. Open the updated link in an email app and check the recipient.

Controlled demo contact page showing an incomplete email destination inside a red evidence outline.
Demo capture / Desktop contact page. Red outline marks the incomplete address.
Reproduction and developer handoff
  1. Open the contact page.
  2. Inspect the email link destination.
  3. Compare the recipient with the confirmed business address.

Expected: a complete, valid email destination. Observed in this example: the domain has no suffix.

Retest: confirm the destination and recipient. The free check does not send an email.

02 / Mobile layout

Contact content extends beyond the phone screen

Medium

What is wrong

A 580px contact panel exceeds a 390px viewport. The dotted line marks the screen edge; red shading shows the overflow.

Why it matters

Visitors must scroll sideways to read the full panel.

Recommended action

Remove the fixed minimum width and allow content to wrap. Retest at 360px and 390px with the menu open and closed.

Controlled mobile demo with a dotted 390 pixel screen boundary and red shading over content extending beyond it.
Demo capture / 390px boundary with overflow exposed to the right. Not a normal phone screenshot.
Reproduction and developer handoff
  1. Open the contact page at 390px wide.
  2. Compare the panel's right edge with the screen boundary.
  3. Check for horizontal scrolling.

Expected: content fits without sideways scrolling. Observed in this example: the panel exceeds the viewport.

Retest: page scroll width must not exceed viewport width at both phone sizes.

Paid service / Illustrative report format

Reviewed website audit

Fern & Forage / Contact journey

Discuss an audit

Make enquiry completion reliable

This fictional audit illustrates how a reviewed report connects a defect to a business risk and a clear acceptance test. It is not a record of testing performed for a client.

Example scope: contact journey on desktop and mobile. Actual scope and browsers are agreed before work starts.

AUD-001 / Contact journey

Enquiry submission gives no visible confirmation

High

Business impact

A customer cannot tell whether their message was received and may submit again or abandon the enquiry.

Illustrative observation

After submitting valid details, the form remains visible with no success message. Delivery itself is not established by this visual observation.

Recommended action

Display an accessible success message after a confirmed successful response. On failure, show a useful error and preserve entered details.

Controlled demo enquiry form with the missing confirmation area outlined in red.
Controlled demo of the evidence format, not a real submission or delivery test.
Acceptance test and handoff
  1. Use an agreed test inbox and submit valid details in the agreed browsers.
  2. Confirm one request, a visible success message and receipt in the test inbox.
  3. Simulate a failed response: details remain and a useful error appears.
  4. Confirm keyboard and screen-reader users receive the status update.

Pass condition: unambiguous success and failure, without duplicate sends. Record browser, build and retest date in the delivered audit.

AUD-002 / Mobile contact page

Contact panel requires horizontal scrolling

Medium

The layout risk shown in the free example is reviewed in context: surrounding navigation, keyboard access and real-device behaviour, followed by fix verification across agreed phone sizes.

Acceptance test: enquiry content is readable without sideways scrolling and controls remain reachable.

Paid service / Illustrative monthly update

Monthly QA review

Fern & Forage / Example issue register

Discuss monthly QA

One fix confirmed. Two actions remain.

An example of how recurring QA makes change visible: what is new, what still needs work and what has been retested. These statuses are fictional, not verified customer outcomes.

Tracked examples
3
New
1
Outstanding
1
Resolved
1
New

MON-003 / Campaign link opens a missing page

Priority: medium. The homepage promotion points to an unavailable campaign page.

Action: update the destination or restore the page. Retest from desktop and mobile navigation before the campaign starts.

Outstanding

AUD-001 / Enquiry confirmation still absent

Priority: high. In this fictional update, the form still gives no clear success state.

Action: prioritise the confirmation fix, then repeat the success, failure and delivery acceptance tests.

Resolved

AUD-002 / Mobile contact panel fits

Illustrative retest: content fits at 360px and 390px without horizontal scrolling.

Closure evidence in a delivered report: tested build and browser, retest date, and before/after captures. No real fix is claimed here.