Website review, no card needed
anjunabeats.com website review
Visit site (opens in a new tab)Reviewed 6 November 202635 issues · 81 checks
This review found 35 issues worth fixing on anjunabeats.com, 12 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74C- #82,024 of 116,627 reviewed websitesbeats 26%
- #52,338 of 66,797 online storesbeats 18%
- #49,279 of 60,941 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 221 ms |
| May 23, 2026 | 204 ms |
| May 30, 2026 | 198 ms |
| Jun 6, 2026 | 204 ms |
| Jun 13, 2026 | 212 ms |
| Jun 20, 2026 | 226 ms |
| Jun 27, 2026 | 226 ms |
| Jul 4, 2026 | 220 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 201 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 189 ms |
| Aug 15, 2026 | 190 ms |
| Aug 22, 2026 | 202 ms |
| Aug 29, 2026 | 203 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 174 ms |
| Oct 10, 2026 | 198 ms |
| Oct 17, 2026 | 229 ms |
| Oct 24, 2026 | 230 ms |
| Oct 31, 2026 | 235 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.2 s
Speed
Reduce unused JavaScript
1.3 s · 376 KiBAbout 376 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Render-blocking requests
1.0 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Use efficient cache lifetimes
900 ms · 376 KiB6 files are served with short cache lifetimes, so returning visitors download them again (376 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
400 ms · 281 KiB5 images could be 281 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 869 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
250 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (ochre.io, Cloudflare and Google Fonts and others), adding 478 KiB and 135 ms of main-thread time.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Reduce unused CSS
110 ms · 11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 ms faster on a phone.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Anjunastore Winter Sale 2026”.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 9.2 s
9.2 sThe page becomes fully interactive after 9.2 s. Good is under 3.8 s.
Real-user INP: 278 ms
278 msReal visitors wait 278 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 292 ms
292 msScripts block taps and scrolling for 292 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 221 ms to 235 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 552 ms
552 msReal visitors wait 552 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.4 MB in 62 requests
1.4 MBYour homepage downloads 1.4 MB in 62 requests on a phone: scripts 594 KiB (26), images 341 KiB (6) and other files 269 KiB (22). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 buttons without a name
9 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
<html> element must have a valid value for the lang attribute (1 element)
<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h4 → h6, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (11 characters)
Your title is only 11 characters: “Anjunabeats”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://anjunabeats.com/sitemap.xml, so Google discovers your pages only by following links.
67 internal links, 42 external
The homepage links to 67 pages on anjunabeats.com and 42 external pages.
3 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “The official home of Anjunabeats, Above & Beyond's record label. Releases info, music downloads, playlists, a super…”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://anjunabeats.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (216 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages without a meta description
https://anjunabeats.com/cd-and-vinyl, https://anjunabeats.com/merch, https://anjunabeats.com/merch/new-arrivals, https://anjunabeats.com/merch/bigger-than-all-of-us-merch, https://anjunabeats.com/merch/anjuna-staple-tees and https://anjunabeats.com/merch/t-shirts-and-hoodies and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://anjunabeats.com/features, https://anjunabeats.com/events, https://anjunabeats.com/artists, https://anjunabeats.com/radio-shows and https://anjunabeats.com/playlists use the same meta description. A description written for each page earns more clicks.
9 pages without an H1
https://anjunabeats.com/music, https://anjunabeats.com/merch, https://anjunabeats.com/merch/new-arrivals, https://anjunabeats.com/merch/bigger-than-all-of-us-merch, https://anjunabeats.com/merch/anjuna-staple-tees and https://anjunabeats.com/merch/t-shirts-and-hoodies and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://anjunabeats.com/merch/homeware, https://anjunabeats.com/artists, https://anjunabeats.com/radio-shows and https://anjunabeats.com/playlists have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
34 small tap targets
34 of 94 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://player.ochre.io/embed/css' from origin 'https://anjunabeats.com' has been blocked …”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 228 words
The homepage has only about 228 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop CD & Vinyl” and “Join”.
6 calls to action
The homepage has 6 calls to action, for example “Join” and “Contact”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at anjunabeats.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- E-commerce
- Shopify Plus
- Hosting
- Cloudflare
Company
- Founded
- 2000
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on anjunabeats.com, including 12 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.