We loaded 5 of your pages the way a customer does - on a typical phone, on a normal cellular connection - and checked what decides whether visitors stay, can use the page, and get recommended by AI.
A snapshot of the live site on June 25, 2026. If the site has changed since, this may no longer reflect it.
The bottom line
Accessibility is the biggest gap - 7 issues across 5 pages make it hard for some visitors to use the site, though AI search tools can read nearly all your content.
Is your site fast enough on a phone?
Slow to load
Visitors on phones wait about 3.8 seconds before the main content appears, and the homepage takes over 4 seconds before anything shows. No page sections jump around while loading, which avoids one common source of frustration.
Start here
→Scrolling the homepage(first paint 4.2s)
→Events(biggest piece at 4.1s)
2 more pages have a similar slowdown; 1 page loads fine.
The first pixels take that long to land, so the page feels stalled at the start.
619 KB downloaded first
73/100 speed score
▶ Press play - watch how long it sits empty before anything shows.
Frame by frame · 7 captured
Blank
0.2s
Biggest piece
4.2s
Loaded
4.4s
This page loads slowly - it takes over 4 seconds for content to appear and over 6 seconds for the full page to load. The heavy file size (772KB) is the main culprit, and there's also an accessibility issue that could block some users.
The biggest piece of the page takes 4.1s to appear
Until then a visitor on a phone is looking at a mostly empty screen.
651 KB downloaded first
76/100 speed score
▶ Press play - this is the 4.1s a phone visitor waits, in real time.
Frame by frame · 11 captured
Blank
0.2s
First content
3.9s
Biggest piece
4.1s
Loaded
5.7s
Loaded
5.7s
Layout jump
7.7s
Layout jump
8.4s
Loaded
8.6s
Page takes 4 seconds to show main content - fairly slow, but responsive and smooth once loaded. It has 3 accessibility issues, though AI reads it very well.
The biggest piece of the page takes 3.6s to appear
A bit slower than the under-2.5-second mark that feels instant on a phone.
536 KB downloaded first
79/100 speed score
▶ Press play - this is the 3.6s a phone visitor waits, in real time.
Frame by frame · 13 captured
Blank
0.0s
Biggest piece
3.6s
Loaded
5.3s
Loaded
5.3s
Layout jump
6.9s
Layout jump
8.2s
Loaded
8.3s
The page takes 3-4 seconds to start showing content and 5+ seconds to fully load. One major accessibility issue could block people using assistive technology, though AI assistants read it well.
The biggest piece of the page takes 3.2s to appear
A bit slower than the under-2.5-second mark that feels instant on a phone.
479 KB downloaded first
84/100 speed score
▶ Press play - this is the 3.2s a phone visitor waits, in real time.
Frame by frame · 12 captured
Blank
0.2s
Blank
2.9s
Biggest piece
3.2s
Loaded
4.2s
Loaded
4.2s
The page takes 3-4 seconds to load - that's slow. It's responsive when ready, but has a serious accessibility problem that blocks people with certain disabilities.
The rest of the pages we checked · 1 page
Homepage/
Nothing appears for the first 3.5s
Can everyone use your site?
Several barriers found
Low-vision visitors struggle to read text on 5 pages because the colors blend together, with the Events page the hardest to read. Screen reader and keyboard-only users cannot navigate the page areas because the sections are not clearly labeled. This can mean lost customers and some legal risk.
Start here
Start with your worst-affected page (Events): label its controls clearly so screen reader visitors know what they do. The other 4 pages have their own barriers; see the cards below.
Needs attention · 5 pages
Events
/events/
89
score
4 moderate← tap to highlight
One form field has no label and five links have no readable text, so people using a screen reader or keyboard cannot tell what the field is for or where those links lead.
Unlabeled links · 1 spot
Low-contrast text · 2 spots
Unlabeled links · 1 spot
What to change
→Add a visible label to the unlabeled form field so people know what to type in it.
→Add readable text to the 5 links that currently have none, so it is clear where each one leads.
→Darken the light-colored text in 3 places so it is easier to read.
Homepage
/
96
score
4 moderate← tap to highlight
Some text is too light to read easily, and the footer appears more than once in a conflicting structure, which can disorient people navigating the page with a screen reader.
Low-contrast text · 2 spots
Low-contrast text · 1 spot
What to change
→Darken the light-colored text in 3 places so it stands out against its background.
→Fix the heading order so it steps down one level at a time without skipping.
→Remove the duplicate footer and make sure it is not placed inside another page section.
Scrolling the homepage
/
96
score
4 moderate← tap to highlight
The scrolled view of the homepage has the same issues: some text is hard to read for people with low vision, and the footer structure and heading order can disorient screen reader users.
Low-contrast text · 1 spot
Low-contrast text · 2 spots
What to change
→Darken the light-colored text in 3 places so it stands out against its background.
→Fix the heading order so it steps down one level at a time without skipping.
→Remove the duplicate footer and make sure it is not placed inside another page section.
About page
/about/
96
score
4 moderate← tap to highlight
Some text is too light to read clearly, and section headings skip levels while the footer region is structured in a way that can confuse people navigating by screen reader.
Low-contrast text · 2 spots
Low-contrast text · 1 spot
What to change
→Darken the light-colored text in 3 places so it is readable against its background.
→Fix the heading order so it steps down one level at a time without skipping.
→Remove the duplicate footer region and make sure it is not nested inside another page section.
Apply page
/apply/
97
score
← tap to highlight
Two pieces of text on this page are too light against their background, making them hard to read for people with low vision or in bright conditions.
Low-contrast text · 2 spots
What to change
→Darken the two light-colored text elements so they stand out clearly against their background.
Can AI read and recommend you?
Strong AI visibility
AI assistants and search tools can read 97% of your content without needing to run any code, earning a score of 94 out of 100. Your site is well set up to appear in AI-powered answers.
Can AI reach your site at all?
site-wide
92
access
robots.txt does not block the AI answer crawlers (the ones that cite sources).
A sitemap is published, which gives crawlers a clearer page list to discover.
No llms.txt (an optional, emerging guide for AI tools - low impact today).
The pages we checked allow indexing.
Reading well · 5 pages
Nearly all of each page's content is already in the HTML and cleanly marked up, so AI assistants read these fine.
94
About page /about/
94
Apply page /apply/
94
Events /events/
96
Homepage /
96
Scrolling the homepage /
The single fix behind most of this is making sure your full page content is present the moment the page loads - done well, it speeds the page up for real visitors and makes you readable to AI at the same time. That is the work we do every day at ShakaCode; happy to walk through what we found.
Measured June 25, 2026 on an emulated mid-range phone over the Slow-4G profile Google PageSpeed uses - the conditions a real mobile visitor faces, not a developer's laptop. Speed score is Google's 0-100 mobile scale (90+ is fast, under 50 is slow); layout shift is Google's CLS (above 0.25 is poor); accessibility score is the Google Lighthouse 0-100 scale. Put together by ShakaCode.