PXP site audit

Automated scans of 1 key page across mobile and desktop, run 2026-11-19.

Automated checks only. These cover part of WCAG — a manual review covers what a machine can't test, such as keyboard operation, focus order and whether alt text is meaningful.

Average scores

Performance
90 mobile
100 desktop
Accessibility
68 mobile
68 desktop
Best Practices
96 mobile
96 desktop
SEO
85 mobile
85 desktop
Agentic Browsing
1/2 mobile
1/2 desktop

Scores by page

Lighthouse category scores, 0–100. 90+   50–89   under 50
Agentic Browsing is scored as a fraction of checks passed rather than out of 100.
Page Mobile Desktop
Perf A11y BP SEO Agent Perf A11y BP SEO Agent
Home / Open Home on the live site, opens in a new tab Performance 90 , good Accessibility 68 , needs improvement Best Practices 96 , good SEO 85 , needs improvement Agentic Browsing 1 of 2 checks passed , needs improvement Performance 100 , good Accessibility 68 , needs improvement Best Practices 96 , good SEO 85 , needs improvement Agentic Browsing 1 of 2 checks passed , needs improvement

Most widespread issues

11 distinct checks fail somewhere on the site. These affect the most pages — fixing them once in a shared template usually clears them everywhere.

Image elements do not have `[alt]` attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

critical 1 page 16 elements

`[aria-*]` attributes do not match their roles

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

critical 1 page 1 element

Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

critical 1 page 1 element

`[aria-*]` attributes do not have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

critical 1 page 1 element

ARIA input fields do not have accessible names

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more abou...

serious 1 page 1 element

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

moderate 1 page 1 element

Heading elements are not in a sequentially-descending order

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn...

moderate 1 page 4 elements

Elements with `role="none"` or `role="presentation"` have conflicts

There are certain cases where the semantic role of an element with `role="none"` or `role="presentation"` does not resolve to none or presentation. To ensure...

minor 1 page 1 element

Browser errors were logged to the console

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagno...

unrated 1 page page-level

Document does not have a meta description

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

unrated 1 page page-level

See all 11 issues

Link integrity

No broken links found across 1 link checked on 1 page. See what was checked

Notes

Site audit, November 19, 2026.