www.saylesteam.com
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 29, 2026. If the site has changed since, this may no longer reflect it.
Accessibility is the most urgent fix - 16 issues across 5 pages mean screen reader and low-vision visitors cannot fully use your site, while your AI search visibility is already strong at 83 out of 100.
On phones, most pages take about 4.5 seconds to show their main content, long enough that visitors may leave before seeing anything. The homepage takes nearly 10 seconds, and 3 pages shift around as they load, which can cause visitors to tap the wrong thing.
- → Homepage (biggest piece at 9.7s)
- → About (first paint 4.7s)
Most of the page paints early, so the wait is easy to miss - but the biggest piece of the page only lands then.
▶ Press play - this is the 9.7s a phone visitor waits, in real time.
The first pixels take that long to land, so the page feels stalled at the start.
▶ Press play - watch how long it sits empty before anything shows.
The page scores 0.21 on Google's layout-shift scale; a page is fully stable only below 0.10, and yours is above that, so things can still move under your visitor's thumb.
▶ Press play and watch the page jump around as it loads.
The page scores 0.19 on Google's layout-shift scale; a page is fully stable only below 0.10, and yours is above that, so things can still move under your visitor's thumb.
▶ Press play and watch the page jump around as it loads.
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 2.6s a phone visitor waits, in real time.
On the three listing pages, text and links are hard to read for low-vision visitors. Screen reader users cannot tell page sections apart on any page, and a button on About has no readable label. This can cost customers, carry some legal risk, and hurt search visibility.
Start with your worst-affected page (Homepage): fix its accessibility barriers so screen reader and keyboard visitors can use it. The other 4 pages have their own barriers; see the cards below.
Four links on this page are only set apart by color, so visitors who cannot distinguish colors easily have no way to tell which words are clickable.
- →Make the four links visually distinct beyond color alone, such as by underlining them.
- →Enlarge the small tap target so it is easier to press on a touchscreen.
- →Mark out the main content area of the page so navigation tools can jump straight to it.
Two links have no readable label, two pieces of text are too faint to read, and two links are only set apart by color, creating barriers for people with low vision or who use screen readers.
- →Add readable text labels to the two links that currently have none.
- →Darken the two pieces of faint text so they are readable by people with low vision.
- →Make links visually distinct beyond color alone, for example by underlining them.
Two links have no readable label and two pieces of text are too light to read, making parts of this page inaccessible to people using screen readers or those with low vision.
- →Add readable text labels to the two links that currently have none.
- →Darken the faint-colored text so it is readable by people with low vision.
- →Make links visually distinct beyond color alone, for example by underlining them.
Two links have no readable label and some text on this page is too faint to read comfortably, creating barriers for screen reader users and people with low vision.
- →Add readable text labels to the two links that currently have no text.
- →Darken the low-contrast text so it is readable by people with low vision.
- →Make links visually distinct beyond color alone, such as by underlining them.
One button on this page has no readable label, so anyone using a keyboard or screen reader has no way to tell what it does.
- →Add a text label to the unlabeled button so its purpose is clear to all users.
- →Enlarge the small tap target so it is easier to press on a touchscreen.
- →Wrap the page sections in structural zones so navigation tools can move between them.
AI-powered search tools can read 90 percent of your content without any extra work, giving the site a solid score of 83 out of 100. The one gap is that some supporting data does not load until after the page runs, which a few AI tools may miss.
- → Featured Listings (structured data before javascript)
Add schema.org structured data to the HTML the server sends.
- →Add machine-readable structured data to the page HTML so AI can identify the listings.
- →Server-render the page so all listing content is present in the HTML before the browser runs.
- →Add social preview tags so link shares show the correct title, description, and image.
Add schema.org structured data to the HTML the server sends.
- →Add machine-readable structured data to the page HTML.
- →Wrap the primary content in a landmark region so AI knows where the main content is.
- →Add descriptive alt text to the 11 images that currently lack it.
Add schema.org structured data to the HTML the server sends.
- →Add machine-readable structured data to the page HTML.
- →Add social preview tags so link shares show the correct title, description, and image.
Nearly all of each page's content is already in the HTML and cleanly marked up, so AI assistants read these fine.
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 29, 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.