Website review, no card needed
can-doc.de website review
Visit site (opens in a new tab)Reviewed 8 November 202628 issues · 72 checks
This review found 28 issues worth fixing on can-doc.de, 14 of them high impact, across 72 checks. The most urgent: avoid multiple page redirects. 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
78C- #59,475 of 117,595 reviewed websitesbeats 44%
- #39,126 of 66,923 online storesbeats 36%
- #37,413 of 61,018 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 123 ms |
| May 23, 2026 | 124 ms |
| May 30, 2026 | 125 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 126 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 130 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 131 ms |
| Jul 25, 2026 | 130 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 135 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 132 ms |
| Sep 26, 2026 | 130 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 128 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
Avoid multiple page redirects
17.3 sThe page goes through 1 redirect before it starts loading, costing about 17.3 s. Link and advertise the final URL directly.
Reduce unused JavaScript
2.8 s · 391 KiBAbout 391 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7,523 HTML elements
The page has 7,523 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (tt-srv.com, Hotjar and Shopify and others), adding 778 KiB and 1.4 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 551 ms. During a long task the page ignores taps.
tt-srv.com adds 467 ms
467 mstt-srv.com costs a phone 467 ms of main-thread work and 60 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.
Hotjar adds 403 ms
403 msHotjar costs a phone 403 ms of main-thread work and 65 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.
Shopify adds 143 ms
143 msShopify costs a phone 143 ms of main-thread work and 317 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.
Use efficient cache lifetimes
178 KiB23 files are served with short cache lifetimes, so returning visitors download them again (178 KiB).
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Improve image delivery
80 KiB5 images could be 80 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need.
Minify JavaScript
7 KiB7 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.9 s
16.9 sYour largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Arzt schaut in die Kamera, Frau steht im Freien und Lächelt…”.
Time to Interactive: 21.0 s
21.0 sThe page becomes fully interactive after 21.0 s. Good is under 3.8 s.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 123 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 123 ms
123 msReal visitors wait 123 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 257 ms
257 msReal visitors wait 257 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 333 requests
3.7 MBYour homepage downloads 3.7 MB in 333 requests on a phone: scripts 1.6 MB (118), images 1.4 MB (102) and fonts 294 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 126.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
98 text elements with low contrast
98 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
14 links without text
14 links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
SEO
459 internal links, 13 external
The homepage links to 459 pages on can-doc.de and 13 external pages.
8 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “Medizinisches Cannabis auf Rezept: Online beantragen, von Ärzt:innen prüfen lassen und Cannabisblüten bequem bestellen.”.
One H1 headline
Your main headline reads: “Cannabis-Rezept online – ab 0 € & ohne Registrierung”.
Title: 51 characters
Your title is a healthy 51 characters: “Cannabis-Rezept online: ab 0 € & ohne Registrierung”.
Canonical URL set
The canonical URL is https://can-doc.de/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, 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://can-doc.de/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
llms.txt published
The site publishes https://can-doc.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://can-doc.de/collections/deal-of-the-week is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.
6 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.
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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
8 third-party cookies
8 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
7 console errors
7 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 5,732 words of copy
The homepage carries about 5,732 words of visible text.
3 checks passed
72 short forms
72 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 11 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Hotjar.
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 can-doc.de, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Adcell Tracking Remarketing · Klaviyo Email Marketing Sms · Digital Appointments · Upcharge Fees · amazonaws.com
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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on can-doc.de, including 15 speed issues and 2 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.