genius.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 biggest gap - 28 high-impact issues across 5 pages block screen reader users and low-vision visitors; mobile speed is fair overall, though two pages load slowly enough to lose visitors.
Most pages load their main content in about 4 seconds on a phone, which is acceptable. Two pages run significantly slower - the Rap genre page takes 8.4 seconds and the Eminem Show album page takes 7.6 seconds, long enough that visitors may leave before the content appears.
- → Genre: Rap (biggest piece at 8.4s)
Until then a visitor on a phone is looking at a mostly empty screen.
▶ Press play - this is the 8.4s a phone visitor waits, in real time.
Until then a visitor on a phone is looking at a mostly empty screen.
▶ Press play - this is the 7.6s a phone visitor waits, in real time.
Screen reader users, keyboard-only users, and low-vision visitors face 28 significant barriers across 5 pages. On the Lyrics: Eminem - Lose Yourself page, low-vision users find the text too faint to read. These gaps mean lost visitors, some legal risk, and weaker search visibility.
Start with your worst-affected page (Lyrics: Eminem - Lose Yourself): label its controls clearly so screen reader visitors know what they do. The other 4 pages have their own barriers; see the cards below.
Eleven buttons have no readable label and 19 links have no text, leaving keyboard and screen reader users unable to tell what these controls do or where they lead.
- →Add a text label to each of the 11 icon buttons so screen reader and keyboard users know what they do
- →Add readable text to the 19 links that currently have no label so users know where they go
- →Add descriptions to the 14 image-like elements so screen readers can tell users what they show
Seven images have no description and one form field has no label, leaving screen reader users unable to identify them, while very low text contrast across 142 spots makes reading difficult for people with low vision.
- →Add a short description to each of the 7 images so screen readers can tell users what they show
- →Add a visible label to the form field so users know what to type into it
- →Darken the light-coloured text throughout the page so people with low vision can read it more easily
Six images have no description and two controls use invalid accessibility markup, which can confuse screen readers and prevent users from understanding what those elements are or do.
- →Add a short description to each of the 6 images so screen readers can identify them
- →Fix the two controls that use invalid accessibility role values so assistive technology handles them correctly
- →Darken the light-coloured text so it is easier to read for people with low vision
Five controls use invalid accessibility markup, 8 links have no readable text, and 17 image-like elements have no description, making screen reader users unable to identify or use large parts of the homepage.
- →Fix the 5 controls that use invalid accessibility role values so assistive technology can interpret them correctly
- →Add descriptions to the 17 image-like elements so screen readers can tell users what they show
- →Add readable text to the 8 links that currently have no label so users know where they lead
Four links have no readable text and the page prevents users from pinching to zoom on a touchscreen, making it harder to use for screen reader users and anyone who needs to enlarge text on mobile.
- →Add readable text to the 4 links that have no label so users know where they lead
- →Allow users to zoom in on the page - the current setting blocks pinch-zoom on mobile devices
- →Make the tap targets larger or spread them further apart so they are easier to press accurately
Only 33 percent of the site's content is visible to AI-powered search tools and answer engines before the page fully loads. The rest appears only after code runs, which many AI tools skip - reducing the site's chances of appearing in AI-driven searches and recommendations.
- → Genre: Rap (content before javascript)
- → Lyrics: Eminem - Lose Yourself (structured data before javascript)
Most AI crawlers do not run JavaScript, so they see almost none of this page.
- →Server-render the page so its full text is in the HTML from the start, not loaded by JavaScript
- →Add schema.org structured data to the server-sent HTML
- →Add social preview tags (Open Graph title, description, and image)
Most AI crawlers do not run JavaScript, so they see almost none of this page.
- →Server-render the page so its full text is in the HTML from the start, not loaded by JavaScript
- →Add schema.org structured data to the server-sent HTML
- →Add a canonical URL to prevent duplicate-address confusion for crawlers
The rest only appears after the browser runs the page, where many AI crawlers cannot follow.
- →Server-render the page so its full text is in the HTML from the start, not loaded by JavaScript
- →Add a short page description in the server-sent HTML
- →Add schema.org structured data to the server-sent HTML
The rest only appears after the browser runs the page, where many AI crawlers cannot follow.
- →Add schema.org structured data to the server-sent HTML
- →Set the html lang attribute so crawlers know the page language
- →Fix the heading structure: use exactly one h1 and make sure heading levels do not skip
The rest only appears after the browser runs the page, where many AI crawlers cannot follow.
- →Fix heading levels so they do not skip (for example, h2 then h3, not h2 then h4)
- →Wrap the main content area in a <main> region so agents know where to focus
- →Add descriptive alt text to the 6 images that currently lack 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 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.