Website review, no card needed
dieaerzte.shop website review
Visit site (opens in a new tab)Reviewed 8 November 202618 issues · 70 checks
This review found 18 issues worth fixing on dieaerzte.shop, 3 of them high impact, across 70 checks. The most urgent: 8 text elements with low contrast. 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
84B- #22,130 of 124,214 reviewed websitesbeats 77%
- #14,248 of 69,815 online storesbeats 74%
- #13,817 of 63,493 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 500 ms |
| May 23, 2026 | 511 ms |
| May 30, 2026 | 521 ms |
| Jun 6, 2026 | 522 ms |
| Jun 13, 2026 | 525 ms |
| Jun 20, 2026 | 522 ms |
| Jun 27, 2026 | 535 ms |
| Jul 4, 2026 | 539 ms |
| Jul 11, 2026 | 545 ms |
| Jul 18, 2026 | 548 ms |
| Jul 25, 2026 | 544 ms |
| Aug 1, 2026 | 558 ms |
| Aug 8, 2026 | 562 ms |
| Aug 15, 2026 | 559 ms |
| Aug 22, 2026 | 554 ms |
| Aug 29, 2026 | 549 ms |
| Sep 5, 2026 | 543 ms |
| Sep 12, 2026 | 545 ms |
| Sep 19, 2026 | 546 ms |
| Sep 26, 2026 | 546 ms |
| Oct 3, 2026 | 520 ms |
| Oct 10, 2026 | 506 ms |
| Oct 17, 2026 | 501 ms |
| Oct 24, 2026 | 493 ms |
| Oct 31, 2026 | 502 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 64 ms |
| May 23, 2026 | 64 ms |
| May 30, 2026 | 65 ms |
| Jun 6, 2026 | 65 ms |
| Jun 13, 2026 | 65 ms |
| Jun 20, 2026 | 67 ms |
| Jun 27, 2026 | 67 ms |
| Jul 4, 2026 | 69 ms |
| Jul 11, 2026 | 69 ms |
| Jul 18, 2026 | 69 ms |
| Jul 25, 2026 | 69 ms |
| Aug 1, 2026 | 70 ms |
| Aug 8, 2026 | 69 ms |
| Aug 15, 2026 | 69 ms |
| Aug 22, 2026 | 68 ms |
| Aug 29, 2026 | 66 ms |
| Sep 5, 2026 | 66 ms |
| Sep 12, 2026 | 67 ms |
| Sep 19, 2026 | 68 ms |
| Sep 26, 2026 | 69 ms |
| Oct 3, 2026 | 67 ms |
| Oct 10, 2026 | 65 ms |
| Oct 17, 2026 | 64 ms |
| Oct 24, 2026 | 63 ms |
| Oct 31, 2026 | 65 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
Speed
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 125 KiBAbout 125 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Accessibe Accessibility Overlay, Shopify and shop.app), adding 316 KiB and 182 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 167 ms. During a long task the page ignores taps.
Improve image delivery
67 KiB6 images could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
5 KiB3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
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.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 479 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Weiblich”.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.6 s
6.6 sThe page becomes fully interactive after 6.6 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 64 ms to 65 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.5 s to 0.5 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: 0.7 s
0.7 sReal visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 61 ms
61 msReal visitors wait 61 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: 0.5 s
0.5 sReal visitors see the first content after 0.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 272 ms
272 msReal visitors wait 272 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 121 ms
121 msScripts block the page for only 121 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
An image on the first screen is lazy-loaded
kachel-weiblich_cd5e9382-ebde-40fc-9bbb-a8fb8428d8ba.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).
About 0.5 g of CO₂ per visit
0.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 57.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.7 MB in 199 requests
1.7 MBYour homepage downloads 1.7 MB in 199 requests on a phone: other files 834 KiB (111), scripts 458 KiB (44) and images 316 KiB (17). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
44 internal links, 8 external
The homepage links to 44 pages on dieaerzte.shop and 8 external pages.
6 checks passed
Meta description: 84 characters
Your meta description is 84 characters: “Hier findet ihr das offizielle Merchandise von Der Besten Band Der Welt - die ärzte.”.
Title: 38 characters
Your title is a healthy 38 characters: “die ärzte Online Shop – die ärzte Shop”.
Canonical URL set
The canonical URL is https://dieaerzte.shop/.
Structured data in place
Structured data found: Organization and WebSite.
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://dieaerzte.shop/sitemap.xml.
AI search readiness
No llms.txt
There is no https://dieaerzte.shop/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.
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.
Other pages
8 pages without a meta description
https://dieaerzte.shop/collections/all, https://dieaerzte.shop/policies/shipping-policy, https://dieaerzte.shop/collections/alles, https://dieaerzte.shop/collections/weiblich, https://dieaerzte.shop/collections/maennlich and https://dieaerzte.shop/collections/kindlich and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://dieaerzte.shop/collections/all, https://dieaerzte.shop/collections/alles, https://dieaerzte.shop/collections/weiblich, https://dieaerzte.shop/collections/maennlich, https://dieaerzte.shop/collections/kindlich and https://dieaerzte.shop/collections/aktion have 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 20 found) and read each the way a search engine does.
5 checks passed
Linked pages load
8 pages of 15 loaded without an error (the rest turned automated requests away).
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 8 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
13 of 13 tappable elements near the top are at least 24 px.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 96 words
The homepage has only about 96 words of visible text; thin pages give Google and first-time buyers little to go on.
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
2 calls to action
The homepage has 2 calls to action, for example “dieaerzte.shop” and “die ärzte Shop”.
4 short forms
4 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 10 customer or partner logos and 1 trust badge.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
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 dieaerzte.shop, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on dieaerzte.shop, including 5 speed issues, 2 SEO 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.