www.canvasmedical.com
We loaded 7 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 10, 2026. If the site has changed since, this may no longer reflect it.
The biggest opportunity is mobile speed: the main content typically takes 3.2 seconds to appear on phones, slowest on the Platform, Homepage, and Primary Care pages, while the site is already in decent shape for AI search visibility.
On phones, the main content takes about 3.2 seconds to appear on average, which feels slow to visitors. The worst pages are Platform (3.9 seconds), the Homepage (3.5 seconds), and the Primary Care page (3.3 seconds); nothing jumps around while loading, which is good.
- → Platform (first paint 3.4s)
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 3.9s a phone visitor waits, in real time.
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 3.3s a phone visitor waits, in real time.
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 3.5s a phone visitor waits, in real time.
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 3.9s a phone visitor waits, in real time.
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 2.9s a phone visitor waits, in real time.
Screen reader users hit 12 problems across 7 pages, worst on the Homepage, including images with no description so they cannot tell what is shown. Keyboard-only users also meet unlabeled page parts they cannot identify. This risks lost customers, some legal risk, and weaker search visibility.
Start with your worst-affected page (Homepage): add text descriptions to its images so screen reader visitors know what they show. The other 6 pages have their own barriers; see the cards below.
A photo on the homepage has no description for screen reader users, and a nearby link doesn't say where it leads, so blind or low-vision visitors can lose track of what's on the page and where links go.
- →Add a text description to the photo that is missing one
- →Give the unlabeled link clear text describing where it goes
- →Clean up the list markup so lists only contain list items directly
Two images on this page have no description, so people using screen readers can't tell what they show, and one clickable element is too small to tap reliably for touch or motor-impaired visitors.
- →Add alternative text to the two images that are missing it
- →Make the small tap target bigger or add more spacing around it
On the pricing page, one button or link is nested inside another clickable element, which can confuse keyboard and screen reader users about what happens when they interact with it.
- →Move the nested clickable element so one control isn't placed inside another
- →Make the small tap target bigger or add more spacing around it
- →Add a single main heading (page title) that screen reader users can use to orient
One clickable element is too small to tap accurately for touch or motor-impaired visitors, and the page content isn't organized into clear sections, making it harder for screen reader users to navigate.
- →Make the small tap target bigger or add more spacing around it
- →Organize the page into clear structural sections (header, nav, main) for screen readers
A clickable element here is too small for people with limited dexterity or on touchscreens to tap reliably, and the surrounding content isn't grouped into clear sections for screen reader users to navigate by.
- →Make the small tap target bigger or add more spacing around it
- →Group the page content into clear sections (header, nav, main) for screen readers
One button or link on this page is too small to tap accurately for touch or motor-impaired visitors, and several images repeat their captions as alt text, making screen readers announce the same words twice.
- →Make the small tap target bigger or add more spacing around it
- →Organize the page into clear structural sections for screen reader navigation
- →Remove caption text duplicated in image alt text so screen readers don't repeat it
One clickable element on this page is too small or sits too close to others, making it hard for people with limited dexterity or using a touchscreen to tap accurately.
- →Make the small tap target bigger or add more spacing around it
Your site scores 76 out of 100 for how easily AI tools like ChatGPT and Google's AI Overviews can read and summarize it, with 77% of content available without extra steps. The main gap is that some key details only appear after the page finishes loading, which those tools may miss.
- → Homepage (structured data before javascript)
Add schema.org structured data to the HTML the server sends.
- →Add structured data to the HTML the server sends, so AI tools can understand the page
- →Add a canonical URL so crawlers aren't confused by duplicate page addresses
- →Add descriptive alt text to the 149 images that are missing it
Add schema.org structured data to the HTML the server sends.
- →Add structured data to the HTML the server sends, so AI tools can understand the page
- →Add a canonical URL so crawlers aren't confused by duplicate page addresses
- →Add descriptive alt text to the 103 images that are missing it
Add schema.org structured data to the HTML the server sends.
- →Add structured data to the HTML the server sends, so AI tools can understand the page
- →Add a canonical URL so crawlers aren't confused by duplicate page addresses
- →Add descriptive alt text to the 124 images that are missing it
Add schema.org structured data to the HTML the server sends.
- →Add structured data to the HTML the server sends, so AI tools can understand the page
- →Add a canonical URL so crawlers aren't confused by duplicate page addresses
- →Add descriptive alt text to the 118 images that are missing it
Add schema.org structured data to the HTML the server sends.
- →Add structured data to the HTML the server sends, so AI tools can understand the page
- →Add a single main heading (h1) to the page
- →Add descriptive alt text to the 102 images that are missing it
Add schema.org structured data to the HTML the server sends.
- →Add structured data to the HTML the server sends, so AI tools can understand the page
- →Add a canonical URL so crawlers aren't confused by duplicate page addresses
- →Add descriptive alt text to the 107 images that are missing it
Add schema.org structured data to the HTML the server sends.
- →Add structured data to the HTML the server sends, so AI tools can understand the page
- →Add a canonical URL so crawlers aren't confused by duplicate page addresses
- →Add descriptive alt text to the 97 images that are missing it
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 10, 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.