www.honoluluhighrises.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.
Mobile speed is the biggest gap, as visitors on phones wait up to 9 seconds for key pages like the Buyers guide to appear, pushing many away before they see a listing, while AI visibility at 72 out of 100 is the strongest area.
The typical visitor on a phone waits 3.7 seconds for content to appear, and the Buyers guide takes 9 seconds. Two pages also shift and jump as they load, which frustrates visitors and raises the chance they leave before making contact.
- → Homepage (biggest piece at 2.7s)
- → Condo results (layout jumps (0.20))
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 2.7s a phone visitor waits, in real time.
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.0s a phone visitor waits, in real time.
The page scores 0.20 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.5s a phone visitor waits, in real time.
Screen reader users on 5 pages cannot tell sections apart because some areas have no name, with the Homepage hit hardest. Keyboard-only users also have no clear way to reach the main content. This risks lost customers, some legal exposure, and weaker search visibility.
Start with your worst-affected page (Homepage): raise its text contrast so low-vision visitors can read it. The other 4 pages have their own barriers; see the cards below.
The homepage has no main page heading and some text is too light to read, making it harder for screen reader users to understand the page structure and for people with low vision to read it.
- →Add a clear main heading to the page so screen readers and keyboard users can identify what the page is about
- →Darken the light-colored text in two places so it is easier to read
- →Make the two small tap targets larger or further apart so they are easier to press on a phone
Some text on this page is too light to read easily for people with low vision, small tap targets make buttons difficult to press on mobile, and an embedded section has no label for screen readers.
- →Darken the light-colored text in three places so it stands out more against its background
- →Give the embedded section a label so screen readers can tell visitors what it contains
- →Make the two small tap targets larger or space them further apart so they are easier to press on a phone
Several links on this page have no readable text, so keyboard and screen reader users cannot tell where those links go.
- →Add readable text to the three links that currently have none, so visitors know where each link leads
- →Give the embedded section a label so screen readers can identify what it contains
- →Make the tap target larger so it is easier to press on a phone
Some content areas cannot be jumped to directly with a keyboard, an embedded section has no label for screen readers, and one button or link is too small to tap comfortably on a phone.
- →Give the embedded section a label so screen readers can identify what it contains
- →Make the tap target larger or space it away from nearby controls so it is easier to press
- →Divide the page into labeled regions so keyboard users can jump directly to listings or navigation
An embedded section on this listing page has no label for screen readers, one tap target is too small for comfortable use on a phone, and parts of the page cannot be navigated to directly with a keyboard.
- →Give the embedded section a label so screen readers can tell visitors what it contains
- →Make the tap target larger so it is easier to press on a phone or with a stylus
- →Divide the page into labeled sections so keyboard users can skip directly to the listing details or navigation
Most of the site's text, 86%, can be read by AI tools without any extra steps. The remaining gap is content that only appears after the page finishes loading, which some AI tools may miss entirely.
- → Buyers guide (content before javascript)
- → Condo results (structured data before javascript)
So we cannot confirm what an AI crawler sees here.
- →Fix the server so this page returns readable HTML to AI crawlers.
- →Add schema.org structured data so machines can identify what the page is about.
- →Add social preview tags (title, description, image) for clean link previews.
Add schema.org structured data to the HTML the server sends.
- →Add schema.org structured data so machines can identify what this page is about.
- →Add social preview tags (title, description, image).
- →Add real written content to the page so AI assistants have something meaningful to read and summarize.
The rest only appears after the browser runs the page, where many AI crawlers cannot follow.
- →Server-render this page so its text is in the HTML before JavaScript runs.
- →Add a single h1 heading as the main page heading.
- →Add descriptive alt text to the images that currently lack it.
Add schema.org structured data to the HTML the server sends.
- →Add schema.org structured data so machines can identify this as a property listing.
- →Add descriptive alt text to the images that currently lack it - about 60% are missing it.
- →Add social preview tags (title, description, image).
Add schema.org structured data to the HTML the server sends.
- →Add schema.org structured data so machines can identify this as a team or organization page.
- →Add social preview tags (title, description, image).
- →Give all links descriptive text instead of 'click here' or a bare URL.
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.