PCC JP site audit

Automated scans of 8 key pages across mobile and desktop, run 2026-08-25.

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
39 mobile
60 desktop
Accessibility
65 mobile
72 desktop
Best Practices
92 mobile
96 desktop
SEO
80 mobile
78 desktop

Scores by page

Lighthouse category scores, 0–100. 90+   50–89   under 50
Page Mobile Desktop
Perf A11y BP SEO Perf A11y BP SEO
Homepage / Open Homepage on the live site, opens in a new tab Performance 47 , poor Accessibility 60 , needs improvement Best Practices 92 , good SEO 77 , needs improvement Performance 50 , needs improvement Accessibility 61 , needs improvement Best Practices 96 , good SEO 77 , needs improvement
Island Villages /villages Open Island Villages on the live site, opens in a new tab Performance 31 , poor Accessibility 61 , needs improvement Best Practices 92 , good SEO 77 , needs improvement Performance 50 , needs improvement Accessibility 69 , needs improvement Best Practices 96 , good SEO 77 , needs improvement
Ha Breath of Life Show /ha-show Open Ha Breath of Life Show on the live site, opens in a new tab Performance 44 , poor Accessibility 65 , needs improvement Best Practices 92 , good SEO 85 , needs improvement Performance 60 , needs improvement Accessibility 70 , needs improvement Best Practices 96 , good SEO 77 , needs improvement
Circle Island Tour /circle-island-tour Open Circle Island Tour on the live site, opens in a new tab Performance 46 , poor Accessibility 66 , needs improvement Best Practices 92 , good SEO 85 , needs improvement Performance 60 , needs improvement Accessibility 72 , needs improvement Best Practices 96 , good SEO 77 , needs improvement
FAQs /faq/hours-of-operation Open FAQs on the live site, opens in a new tab Performance 43 , poor Accessibility 66 , needs improvement Best Practices 92 , good SEO 85 , needs improvement Performance 70 , needs improvement Accessibility 76 , needs improvement Best Practices 96 , good SEO 85 , needs improvement
Super Ambassador Package /packages/all/exclusive-super-ambassador-luau-package Open Super Ambassador Package on the live site, opens in a new tab Performance 32 , poor Accessibility 81 , needs improvement Best Practices 96 , good SEO 69 , needs improvement Performance 58 , needs improvement Accessibility 89 , needs improvement Best Practices 96 , good SEO 69 , needs improvement
Educational Resources /educational-resources Open Educational Resources on the live site, opens in a new tab Performance 35 , poor Accessibility 63 , needs improvement Best Practices 92 , good SEO 85 , needs improvement Performance 68 , needs improvement Accessibility 74 , needs improvement Best Practices 96 , good SEO 85 , needs improvement
Taste Polynesia /taste-polynesia Open Taste Polynesia on the live site, opens in a new tab Performance 31 , poor Accessibility 58 , needs improvement Best Practices 92 , good SEO 77 , needs improvement Performance 65 , needs improvement Accessibility 69 , needs improvement Best Practices 96 , good SEO 77 , needs improvement

Most widespread issues

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

`[role]`s are not contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent elem...

critical 7 pages 30 elements

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 7 pages 9 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 7 pages 9 elements

Form elements do not have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

critical 7 pages 7 elements

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 6 pages 18 elements

Buttons do not have an accessible name

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make b...

critical 1 page 13 elements

Background and foreground colors do not have a sufficient contrast ratio.

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

serious 8 pages 31 elements

Links do not have a discernible name

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to...

serious 8 pages 20 elements

List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper l...

serious 7 pages 24 elements

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

serious 7 pages 15 elements

See all 20 issues

Notes

Site audit, August 25, 2026.