pilotweststudios.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 30, 2026. If the site has changed since, this may no longer reflect it.
The biggest gap is accessibility: 9 issues across 5 pages make text hard to read for low-vision and screen reader visitors, even though the site already loads fast and smoothly on phones.
Pages load in about 2 seconds on a phone, and nothing makes visitors wait or jump around while it loads. This part of the site is working well.
Low-vision visitors and screen reader users have trouble reading text that blends into the background on 9 spots across 5 pages, worst on the Custom ERP Software page. This can cost the business customers, bring some legal risk, and weaken search visibility.
Start with your worst-affected page (Services: Custom ERP Software): raise its text contrast so low-vision visitors can read it. The other 4 pages need the same fix.
People with low vision face 28 places on this services page where text is too similar in color to the background to read comfortably, and the page lacks a language declaration that screen readers need to speak the content correctly.
- →Darken the text in 28 places where it is too similar in color to the background for comfortable reading.
- →Declare the page language so screen readers can read the services content in English.
- →Fix the heading order and add page-region labels so keyboard users can navigate between sections of this services page.
The homepage has text that blends into the background in 67 places - by far the most of any page on the site - making large portions of the page difficult to read for visitors with low vision or anyone viewing on a bright screen.
- →Review and darken text in the 67 places where contrast falls short - this page has more contrast issues than any other.
- →Add a language tag to the page so screen readers know to read homepage content in English.
- →Label the homepage sections (header, main content, footer) so keyboard users can navigate directly to each part.
Visitors with low vision encounter text that blends into the background in 15 places on this article, and screen readers may read the page in the wrong language because the page does not declare it is written in English.
- →Darken the text in the 15 spots where it is too similar to the background so low-vision readers can distinguish it.
- →Add a language label to the page so screen readers know to read this article in English.
- →Fix the heading order and mark the article body as the main content area so keyboard users can navigate directly to it.
Visitors with low vision encounter 18 places where text is hard to distinguish from the background, and screen readers may speak this case study in the wrong language because no language is declared.
- →Increase the contrast of text in the 18 spots where it is too close in color to the background.
- →Add a language declaration so screen readers read this case study aloud in English.
- →Correct the heading levels and add a main-content region so keyboard users can skip straight to the case study.
A few text areas are hard to read for people with low vision, and screen reader users moving through headings or sections find this calculator confusing because most of the page isn't grouped into clear sections.
- →Darken the few low-contrast text areas so they're easier to read
- →Fix the heading order so it doesn't skip levels, which confuses screen reader navigation
- →Group the calculator's content into clear sections so people can jump straight to it
AI tools and search assistants can already read all of your website's content, putting the score at 72 out of 100. The main improvement is presenting page descriptions earlier, before other code loads, so AI tools can summarize pages faster and more accurately.
- → Blog: Custom ERP System (description before javascript)
Add a meta description in the HTML the server sends.
- →Add a short description tag that's present before the page finishes loading
- →Add structured data so AI tools can understand the page content automatically
- →Add social preview tags (title, description, image) for clean link previews
Add a meta description in the HTML the server sends.
- →Add a short description tag that's present before the page finishes loading
- →Add structured data so AI tools can understand the page content automatically
- →Add social preview tags (title, description, image) for clean link previews
Add a meta description in the HTML the server sends.
- →Add a short description tag that's present before the page finishes loading
- →Add structured data so AI tools can understand the page content automatically
- →Add social preview tags (title, description, image) for clean link previews
Add a meta description in the HTML the server sends.
- →Add a short description tag that's present before the page finishes loading
- →Add structured data so AI tools can understand the page content automatically
- →Add social preview tags (title, description, image) for clean link previews
Add a meta description in the HTML the server sends.
- →Add a short description tag that's present before the page finishes loading
- →Add social preview tags (title, description, image) for clean link previews
- →Add a canonical URL so AI tools know the official address for this page
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 30, 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.