Big Red Jelly site audit

Automated scans of 7 key pages across mobile and desktop, run 2026-09-15.

7 pages scanned
12 issues found
212 HTML elements to fix
60 broken links
Mobile + Desktop form factors tested

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

50 mobile

71 desktop

Accessibility

79 mobile

80 desktop

Best Practices

100 mobile

100 desktop

SEO

94 mobile

94 desktop

Agentic Browsing

2/3 mobile

2/3 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
Page	Perf	A11y	BP	SEO	Agent	Perf	A11y	BP	SEO	Agent
Homepage / Open Homepage on the live site, opens in a new tab	Performance 53 , needs improvement	Accessibility 73 , needs improvement	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement	Performance 79 , needs improvement	Accessibility 73 , needs improvement	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement
Proven Process /proven-process/ Open Proven Process on the live site, opens in a new tab	Performance 49 , poor	Accessibility 73 , needs improvement	Best Practices 100 , good	SEO 100 , good	Agentic Browsing 2 of 3 checks passed , needs improvement	Performance 65 , needs improvement	Accessibility 73 , needs improvement	Best Practices 100 , good	SEO 100 , good	Agentic Browsing 2 of 3 checks passed , needs improvement
Services /services/ Open Services on the live site, opens in a new tab	Performance 49 , poor	Accessibility 73 , needs improvement	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement	Performance 84 , needs improvement	Accessibility 73 , needs improvement	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement
Plans /services/plans/ Open Plans on the live site, opens in a new tab	Performance 54 , needs improvement	Accessibility 73 , needs improvement	Best Practices 100 , good	SEO 100 , good	Agentic Browsing 2 of 3 checks passed , needs improvement	Performance 64 , needs improvement	Accessibility 74 , needs improvement	Best Practices 100 , good	SEO 100 , good	Agentic Browsing 2 of 3 checks passed , needs improvement
Team /about/team/ Open Team on the live site, opens in a new tab	Performance 48 , poor	Accessibility 87 , needs improvement	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement	Performance 87 , needs improvement	Accessibility 91 , good	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement
Why Big Red Jelly /about/why-big-red-jelly/ Open Why Big Red Jelly on the live site, opens in a new tab	Performance 52 , needs improvement	Accessibility 87 , needs improvement	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement	Performance 59 , needs improvement	Accessibility 87 , needs improvement	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement
Resources /resources/ Open Resources on the live site, opens in a new tab	Performance 46 , poor	Accessibility 90 , good	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement	Performance 56 , needs improvement	Accessibility 91 , good	Best Practices 100 , good	SEO 92 , good	Agentic Browsing 2 of 3 checks passed , needs improvement

Most widespread issues

12 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 4 pages 21 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 4 pages 4 elements

See all 12 issues

Link integrity

60 broken links across 860 crawled pages (46 pointing at this site, 14 pointing elsewhere). A further 79 could not be confirmed either way and are listed separately rather than counted as faults.

404 not found https://bigredjelly.com/sales-landing-page/?s=brand+voice 35 places

404 not found https://bigredjelly.com/product/surge-wix/ 8 places

404 not found https://www.clearscope.io/blog/content-refresh-seo 2 places

404 not found https://www.ariesconfectionaries.com/ 2 places

404 not found https://vanbuilders.com/ 2 places

See all link findings

Notes

Site audit, September 15, 2026.

Big Red Jelly site audit

Average scores

Scores by page

Most widespread issues

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

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

`<td>` elements in a large `<table>` do not have table headers.

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

Links do not have a discernible name

Touch targets do not have sufficient size or spacing.

Links rely on color to be distinguishable.

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

Heading elements are not in a sequentially-descending order

Accessibility tree is not well-formed

Link integrity

Notes