We loaded 6 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 July 9, 2026. If the site has changed since, this may no longer reflect it.
The bottom line
The biggest gap is mobile speed: visitors wait an average of 6.5 seconds for pages to load, which can drive people away before they see anything, even though your content is already very easy for AI tools to find and read.
Is your site fast enough on a phone?
Slow on phones
48
score
Mobile visitors wait an average of 6.5 seconds for the main content to appear, and this happens on 4 pages. The Our Approach and Homepage pages are slowest to show their main content, and the Sleep Clinic page visibly jumps around as it loads.
The biggest piece of the page takes 10.3s to appear
Until then a visitor on a phone is looking at a mostly empty screen.
▶ Press play - this is the 10.3s a phone visitor waits, in real time.
Frame by frame · 66 captured
Blank
0.0s
Blank
2.7s
First content
4.7s
Filling in
10.2s
Biggest piece
10.3s
Loaded
10.5s
This page takes 10+ seconds before the main content appears, and clicking or scrolling feels sluggish with delays around one second. Too much JavaScript is the cause.
The biggest piece of the page takes 5.3s to appear
Until then a visitor on a phone is looking at a mostly empty screen.
▶ Press play - this is the 5.3s a phone visitor waits, in real time.
Frame by frame · 8 captured
Blank
0.1s
First content
3.3s
Filling in
5.2s
Biggest piece
5.3s
This page is very slow - the main content takes over 5 seconds to appear, and clicking buttons feels sluggish. It also has one issue blocking people with disabilities from using it.
The biggest piece of the page takes 4.9s to appear
Until then a visitor on a phone is looking at a mostly empty screen.
▶ Press play - this is the 4.9s a phone visitor waits, in real time.
Frame by frame · 175 captured
Blank
0.0s
First content
2.9s
Biggest piece
4.9s
Loaded
4.9s
The page takes about 5 seconds to load and often feels unresponsive when you try to use it. The main reason is that it downloads a very large amount of data at once.
The rest of the pages we checked · 1 page
Sleep Apnea condition page/conditions/sleep-apnea
The page is slow to react to taps
Can everyone use your site?
Needs attention
98
score
Low-vision visitors struggle to read text that blends into the background on 2 pages, worst on the Sleep Apnea condition page. Screen reader users can't tell the page's sections apart, so they can't jump to the content they need. Left unfixed, this can lose customers and add legal risk.
Start here
Start with your worst-affected page (Sleep Apnea condition page): raise its text contrast so low-vision visitors can read it. The other 1 page needs the same fix.
Needs attention · 2 pages
Sleep Apnea condition page
/conditions/sleep-apnea
95
score
1 moderate← tap to highlight
People with low vision may struggle to read text across many parts of this condition page because a number of text elements do not have enough contrast against their background.
Low-contrast text · 3 spots
Low-contrast text · 1 spot
Low-contrast text · 4 spots
What to change
→Darken or improve the contrast of the many low-contrast text elements throughout the page.
→Fix the heading order so heading levels increase one step at a time instead of skipping.
Blog: What Causes Sleep Apnea
/blog/what-causes-sleep-apnea
98
score
1 moderate← tap to highlight
People with low vision may find some text on this blog post hard to read because it does not have enough contrast against its background.
Low-contrast text · 1 spot
Low-contrast text · 2 spots
What to change
→Darken or increase contrast of the low-contrast text in a few spots on the page.
→Fix the heading order so heading levels go one step at a time instead of skipping a level.
Lighter issues · 4 pages
98
Homepage /
People who navigate by headings with a screen reader or keyboard may find the homepage's heading structure confusing because some heading levels skip a step.
98
Boulder-Longmont location /boulder-longmont
People who navigate by headings with a screen reader or keyboard may find this location page's structure confusing because one heading skips a level.
98
Our Approach /our-approach
People who navigate by headings with a screen reader or keyboard may find this page's structure confusing because one heading skips a level.
98
Multidisciplinary Sleep Clinic service /services/multidisciplinary-sleep-clinic
People who navigate by headings with a screen reader or keyboard may find this service page's structure confusing because several headings skip levels and one heading has no text in it.
Can AI read and recommend you?
Strong AI visibility
94
score
Your site scores 94 out of 100 for how easily AI tools can read and understand your content. About 99% of your content is visible to them without any extra technical work.
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 · 6 pages
Nearly all of each page's content is already in the HTML and cleanly marked up, so AI assistants read these fine.
Blog: What Causes Sleep Apnea /blog/what-causes-sleep-apnea
96
Our Approach /our-approach
96
Multidisciplinary Sleep Clinic service /services/multidisciplinary-sleep-clinic
97
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 July 9, 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.
