Meridian Parks Alliance

This sample shows the format of an LFW website audit. Meridian Parks Alliance is fictional; example.org is a reserved example domain. The scores and findings are illustrative.

78 Performance

98 Accessibility

92 SEO

100 Best practices

Scores are out of 100. Accessibility uses LFW’s scoring method; the other categories use Lighthouse. Automated checks do not establish accessibility conformance or comprehensive security.

How these numbers are determined

Performance, SEO, and Best practices are Google Lighthouse category scores, run in a desktop browser profile on 3 pages of your site and averaged. Lighthouse is the same open-source engine behind Chrome's built-in audits and PageSpeed Insights.

Accessibility is our own score, not Lighthouse's. Audited pages are checked with the axe-core engine against WCAG 2.2 AA. Each rule that fails costs points by its impact (critical 10, serious 6, moderate 3, minor 1), scaled gently by how many elements it affects, so one mistake repeated on 200 elements reads as one mistake, not 200. Pages are then averaged.

How fixes move the numbers. Performance is built from timings: how soon content appears, how long the page stays blocked, how much it shifts. Each performance finding below carries Lighthouse's own estimate of potential time savings. These estimates help prioritize work; rerun the audit to measure the actual change. Accessibility is arithmetic: each accessibility finding below states how many points of the score it costs under this scoring method. A new scan verifies the result after a fix.

In a completed audit, each score comes from a recorded measurement. See how Monitor checks your site and scores its findings for the tools, scope, and limits behind these numbers.

Performance

Moderate Serve a smaller homepage image The sample homepage loads an image larger than its display size requires. Illustrative evidence: a 2,400 px image displayed at 800 px, with an estimated transfer saving of 310 KB. Lighthouse estimates up to 420 ms saved once fixed.

How to fix

Generate appropriately sized images and use responsive sources so each device downloads a suitable version. Confirm the result with a fresh performance measurement.

Accessibility

High Give the email field a persistent label The sample volunteer form uses placeholder text without an associated label. Illustrative evidence: the volunteer form’s email input has a placeholder but no programmatically associated label. Fixing this recovers about 2 points of the accessibility score. Sample page: /volunteer/

How to fix

Add a visible label and associate it with the input. Keep the label available after someone begins typing.

<label for="volunteer-email">Email address</label>
<input id="volunteer-email" name="email"
       type="email" autocomplete="email" />

Search visibility

Moderate Use a descriptive title for each page Two sample pages share the same title, making their purpose harder to distinguish in search results and browser tabs.

Seen on 2 pages

/parks/
/volunteer/

Show the affected element

<title>Meridian Parks Alliance</title>

Sample only. No scan of Meridian Parks Alliance or example.org was performed for this preview.