A real example, explained
What your website check results really mean.
A useful report helps you decide what to review. It does not turn a website into a single pass or fail.
By Gold Oak Digital. This guide uses a dated observation from our own homepage to explain why a high speed score can sit alongside a finding worth checking.
Our own website · desktop lab test
Fast loading. A heading structure to review.
In the saved Google Lighthouse desktop test of goldoakdigital.co.uk at , the scanner received these results:
Review heading order
The automated check flagged heading order. Review whether headings describe a sensible structure.
These findings answer different questions. The performance score describes that lab run’s loading measurements. The heading observation asks for a closer look at how the page is organised.
This is a dated example, not a live score or a claim that the homepage still returns the same results. Later changes, caching and different test conditions can change observations. The example does not establish full accessibility or a fault in every visitor’s experience.
Turn an observation into a sensible next step
- Check the evidence. Note the source page, time and test type. A homepage lab result does not describe every page on the website.
- Confirm the finding on the live page. For heading order, ask your maintainer to inspect the headings and whether they form a sensible structure for the content. An automated observation needs that context.
- Agree a focused change if one is needed. Adjust the relevant page structure without treating a small finding as a reason to rebuild the whole website.
- Retest and keep a record. Compare the affected check and inspect the page manually. A changed score by itself does not prove that every accessibility or usability issue is resolved.
What if a check is unavailable?
A provider may be busy, the request may time out, or the captured page may not contain enough evidence. The scanner labels that result as unavailable or unverified. It does not turn the missing result into a fault, a zero score or a pass.
A phone snapshot may also be labelled limited. It captures the homepage at two emulated widths with a bounded set of assets. It is a starting point for looking at the live site on a phone, rather than a complete device or customer-journey test.
Three checks a business owner can still do manually
- Send your own test enquiry. On your own website, submit a realistic enquiry and confirm it arrives in the correct inbox. A form appearing in the page code does not prove delivery.
- Try the main journey on a phone. Open the menu, find a service and follow its contact route. Check that the wording, controls and content make sense.
- Check business accuracy. Confirm your contact details, service information and prices are current. The scanner does not know your business’s intended content.
Use the priorities as a shortlist
“What to fix first” groups up to three supported review topics and gives a suggested order, explanation and next step. It is not a severity score or a calculation of lost enquiries. An empty shortlist is not a full website pass.
If you want help, request a quote from your result page. We’ll review the evidence and agree scope and price before work starts. Focused improvements, a website rebuild and ongoing support are separate options.
See what your own website returns.
View the available observations without signing up. Request an emailed report or a reply only if you want one.
Run my free website check →