Website review, no card needed
afm-records.com website review
Visit site (opens in a new tab)Reviewed 10 November 202624 issues · 77 checks
This review found 24 issues worth fixing on afm-records.com, 6 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
87B- #7,590 of 108,858 reviewed websitesbeats 90%
- #4,453 of 61,765 online storesbeats 89%
- #4,327 of 56,365 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 97 ms |
| May 30, 2026 | 100 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 102 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 101 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 106 ms |
| Oct 24, 2026 | 108 ms |
| Oct 31, 2026 | 109 ms |
| Nov 7, 2026 | 105 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.1 s · 192 KiB4 images could be 192 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 139 KiBAbout 139 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
850 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Use efficient cache lifetimes
350 ms · 48 KiB5 files are served with short cache lifetimes, so returning visitors download them again (48 KiB).
Legacy JavaScript
350 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Usercentrics CMP adds 297 ms
297 msUsercentrics CMP costs a phone 297 ms of main-thread work and 274 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
2,579 HTML elements
The page has 2,579 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (Usercentrics CMP, Shopify and icmaa.info), adding 421 KiB and 339 ms of main-thread time.
Reduce unused CSS
150 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 668 ms of it running JavaScript. That is comfortably low.
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.9 s
11.9 sYour largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wenn du ablehnst, kannst du unsere Seite weiterhin nutzen –…”.
Time to Interactive: 12.0 s
12.0 sThe page becomes fully interactive after 12.0 s. Good is under 3.8 s.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 97 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 102 ms
102 msReal visitors wait 102 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 408 ms
408 msReal visitors wait 408 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 36 ms
36 msScripts block the page for only 36 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.9 MB in 239 requests
2.9 MBYour homepage downloads 2.9 MB in 239 requests on a phone: images 1.4 MB (24), other files 960 KiB (149) and scripts 532 KiB (56). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
20260227_afm_thundermother_fullsize_mobile_1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image in older formats
1 image (174 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 100.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
224 internal links, 6 external
The homepage links to 224 pages on afm-records.com and 6 external pages.
8 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Stöbere in den neuesten Musikveröffentlichungen und Merchandise von AFM Records. Entdecke Top-Alben und limitierte Edit…”.
One H1 headline
Your main headline reads: “AFM Records”.
Title: 51 characters
Your title is a healthy 51 characters: “AFM Records - Dein Shop für Hard Rock & Heavy Metal”.
Canonical URL set
The canonical URL is https://www.afm-records.de/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.afm-records.de/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,502 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.afm-records.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.afm-records.de/collections/new/Media, whose canonical is https://www.afm-records.de/collections/new/media. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.afm-records.de/collections/music has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 109 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
9 small tap targets
9 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 108-field form
Your longest form asks for 108 fields (0 required). Every extra field lowers completion.
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.
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.
About 444 words of copy
The homepage carries about 444 words of visible text.
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Pre-Order”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) loads with the page.
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 afm-records.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Analyzify Ga4 Ads Tracking · Icmaa Checkout Validation · Icmaa Delivery Time
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on afm-records.com, including 11 speed issues and 4 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.