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 26, 2026. If the site has changed since, this may no longer reflect it.
The bottom line
Accessibility is the biggest gap - 5 high-impact issues affect screen reader and keyboard users across 5 pages including the Homepage; mobile speed is fair at 4.3s and all content is fully readable by AI tools.
Is your site fast enough on a phone?
Slower on some pages
Most pages load in about 4 seconds on a phone, which is acceptable but not fast. A few pages - particularly the Eminem album page at 8.4 seconds and the Rap genre page at 5.9 seconds - keep visitors waiting long enough that some will leave before the content appears.
Start here
→Album: The Eminem Show(biggest piece at 8.4s)
→Genre: Rap(first paint 5.9s)
1 more page has a similar slowdown; 2 pages load fine.
The biggest piece of the page takes 8.4s to appear
Until then a visitor on a phone is looking at a mostly empty screen.
2.7 MB downloaded first
55/100 speed score
▶ Press play - this is the 8.4s a phone visitor waits, in real time.
Frame by frame · 13 captured
Blank
0.1s
Blank
2.6s
First content
5.9s
Filling in
6.1s
Filling in
8.4s
Loaded
9.2s
The page loads slowly - it takes about 8-9 seconds for visitors to see the main content. It also has one accessibility issue that blocks some people from using it.
The first pixels take that long to land, so the page feels stalled at the start.
991 KB downloaded first
59/100 speed score
▶ Press play - watch how long it sits empty before anything shows.
Frame by frame · 12 captured
Blank
0.1s
Blank
5.8s
First content
5.8s
Layout jump
6.1s
Biggest piece
6.2s
Loaded
6.3s
The page is very slow - takes 6+ seconds to load due to a large code file. There's also one serious issue that blocks people using accessibility tools.
Screen reader and keyboard-only users hit real barriers on 5 pages, worst on the Homepage. When the page reloads itself, screen reader users are thrown back to the top, and keyboard-only users cannot tell the page areas apart. This means lost customers and some legal risk.
Start here
Start with your worst-affected page (Homepage): stop it from reloading on its own so screen reader and keyboard visitors are not thrown back to the top. The other 4 pages need the same fix.
Needs attention · 5 pages
Homepage
/
71
score
1 high-impact3 moderate1 low
The homepage automatically reloads after a short period, which can cut off slow readers mid-page, and its main content area appears more than once in a mis-nested layout that confuses screen reader navigation.
No spot is highlighted because this problem lives in how the whole page is built, not in one place you can see on the screen.
What to change
→Remove the automatic page reload so visitors can read the homepage at their own pace.
→Fix the page structure so there is one main content area at the correct level, not inside another landmark.
→Fill in or remove the empty heading so screen readers do not announce a heading with nothing to say.
Album: The Eminem Show
/albums/Eminem/The-eminem-show
71
score
1 high-impact3 moderate1 low
The album page automatically reloads after a short time, which disrupts slow readers and screen reader users, and its main content area is duplicated and mis-nested in a way that breaks section-by-section navigation.
No spot is highlighted because this problem lives in how the whole page is built, not in one place you can see on the screen.
What to change
→Remove the automatic page reload so visitors can read the album page at their own pace without the page jumping.
→Make sure there is exactly one main content area and it sits at the top level, not inside another section.
→Fill in or remove the empty heading so screen readers do not announce a heading with no text.
Artist: Eminem
/artists/Eminem
82
score
1 high-impact3 moderate1 low
The artist page refreshes on its own after a short delay, interrupting visitors who read slowly or use screen readers, and its page regions are duplicated in a way that makes section navigation unreliable.
No spot is highlighted because this problem lives in how the whole page is built, not in one place you can see on the screen.
What to change
→Remove the automatic page refresh so the artist page stays put while visitors read.
→Fix the page so it has a single, clearly placed main content area not nested inside another region.
→Fill in or remove the empty heading so it does not interrupt screen reader users with a heading that has no text.
Lyrics: Eminem - Lose Yourself
/Eminem-lose-yourself-lyrics
65
score
1 high-impact3 moderate1 low
The lyrics page reloads automatically before many visitors finish reading, and its page structure has a duplicated, mis-nested main section that prevents screen reader users from reliably jumping to the song text.
No spot is highlighted because this problem lives in how the whole page is built, not in one place you can see on the screen.
What to change
→Remove the automatic page reload so visitors can read the full lyrics without the page resetting.
→Fix the page so there is only one main content region and it is not nested inside another section.
→Fill in or remove the empty heading so it does not interrupt screen reader users with a heading that contains no text.
Genre: Rap
/tags/rap
88
score
1 high-impact3 moderate1 low
The genre page refreshes automatically after a short time, interrupting visitors who browse at their own pace, and its page regions are duplicated in a way that leaves screen reader navigation of the track listing unreliable.
No spot is highlighted because this problem lives in how the whole page is built, not in one place you can see on the screen.
What to change
→Remove the automatic page refresh so the genre page and its track listing stay in place while visitors read.
→Fix the page structure so there is a single, correctly placed main content area, not nested inside another region.
→Fill in or remove the empty heading so screen readers do not encounter a heading with no content.
Can AI read and recommend you?
Mostly readable
All content on genius.com can be read by AI tools and search crawlers without needing to run any code - a strong foundation. The score of 59 out of 100 reflects a gap in how well the page describes itself before any interactive features load, which can limit how AI tools summarize or surface the site.
Start here
→Album: The Eminem Show(description before javascript)
→Homepage(structured data before javascript)
2 more pages have similar gaps; 1 more page has different gaps.
Can AI reach your site at all?
site-wide
24
access
robots.txt blocks 2 AI answer crawlers (ChatGPT-User, ClaudeBot), which reduces how often AI answers can cite you.
robots.txt blocks 7 training-only crawlers (GPTBot, anthropic-ai, Google-Extended, CCBot). This is a deliberate opt-out with no effect on AI-answer citations, so it does not lower the score.
No sitemap.xml found, so crawlers may miss pages.
No llms.txt (an optional, emerging guide for AI tools - low impact today).
The pages we checked allow indexing.
Page-level gaps · 5 pages
Album: The Eminem Show
/albums/Eminem/The-eminem-show
66
/ 100
The page description is missing before JavaScript runs.
Add a meta description in the HTML the server sends.
Readable without running code80
Labeled so AI knows what it is23
Clear structure & enough text88
What to change
→Move the page description into the server HTML so crawlers see it without needing JavaScript
→Add schema.org structured data in the server HTML so machines know this is a music album page
→Add social preview tags so the page produces proper link cards when cited or shared
Homepage
/
70
/ 100
No machine-readable structured data in the page the server sends.
Add schema.org structured data to the HTML the server sends.
Readable without running code88
Labeled so AI knows what it is23
Clear structure & enough text88
What to change
→Add schema.org structured data to the server HTML so machines understand what this site is about
→Add a page description tag summarizing the site
→Add social preview tags so the page produces proper link cards when cited or shared
Lyrics: Eminem - Lose Yourself
/Eminem-lose-yourself-lyrics
70
/ 100
No machine-readable structured data in the page the server sends.
Add schema.org structured data to the HTML the server sends.
Readable without running code88
Labeled so AI knows what it is23
Clear structure & enough text88
What to change
→Add schema.org structured data to the server HTML so machines know this is a song lyrics page
→Add a page description tag summarizing the song and artist
→Add social preview tags so the page produces proper link cards when cited or shared
Genre: Rap
/tags/rap
70
/ 100
No machine-readable structured data in the page the server sends.
Add schema.org structured data to the HTML the server sends.
Readable without running code88
Labeled so AI knows what it is23
Clear structure & enough text88
What to change
→Add schema.org structured data to the server HTML so machines know this is a music genre listing
→Add a page description tag describing what this genre page covers
→Add social preview tags so the page produces proper link cards when cited or shared
Artist: Eminem
/artists/Eminem
77
/ 100
No schema.org structured data, so machines must infer what the page is about.
Add schema.org structured data (Organization, Product, Article, and so on) so machines can identify the page.
Readable without running code100
Labeled so AI knows what it is23
Clear structure & enough text88
What to change
→Add schema.org structured data to the server HTML so machines identify this as an artist page
→Add a page description tag summarizing the artist
→Add social preview tags so the page produces proper link cards when cited or shared
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 26, 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.