Website review, no card needed
crazylabels.de website review
Visit site (opens in a new tab)Reviewed 13 November 202638 issues · 84 checks
This review found 38 issues worth fixing on crazylabels.de, 11 of them high impact, across 84 checks. The most urgent: 18 tap targets too small. 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- #55,517 of 109,350 reviewed websitesbeats 44%
- #36,297 of 61,859 online storesbeats 36%
- #34,700 of 56,401 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 98 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 115 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 109 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 109 ms |
| Sep 12, 2026 | 120 ms |
| Sep 19, 2026 | 118 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 123 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 135 ms |
| Oct 31, 2026 | 127 ms |
| Nov 7, 2026 | 121 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.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and jQuery CDN and others), adding 1.6 MB and 1.0 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 567 ms
567 msGoogle Tag Manager costs a phone 567 ms of main-thread work and 683 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.
Reduce unused JavaScript
150 ms · 363 KiBAbout 363 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
450 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
300 ms · 87 KiB15 files are served with short cache lifetimes, so returning visitors download them again (87 KiB).
2,521 HTML elements
The page has 2,521 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 188 ms
188 msShopify costs a phone 188 ms of main-thread work and 400 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.
Reduce unused CSS
62 KiBAbout 62 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
23 KiB23 KiB could be saved by minifying JavaScript.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Improve image delivery
13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 181 ms
181 msYour server sent the HTML in 181 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.4 s
21.4 sThe page becomes fully interactive after 21.4 s. Good is under 3.8 s.
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.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 98 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 368 ms
368 msScripts block taps and scrolling for 368 ms in total while the page loads. Good is under 200 ms.
8 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 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: 520 ms
520 msReal visitors wait 520 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 379 requests
3.5 MBYour homepage downloads 3.5 MB in 379 requests on a phone: scripts 1.7 MB (154), other files 849 KiB (148) and HTML 496 KiB (7). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Minimalistische_labelrol_met_shopknop_1.png 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 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 119.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “Crazylabels | Etiketten bestellen – Immer zum besten Preis – Crazylabels.nl”.
Meta description is long (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (BreadcrumbList, OnlineStore, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.
197 internal links, 10 external
The homepage links to 197 pages on crazylabels.de and 10 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Die zuverlässige Wahl für Etiketten in ganz Europa.”.
Canonical URL set
The canonical URL is https://www.crazylabels.de/.
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.crazylabels.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, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (760 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.crazylabels.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.crazylabels.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.crazylabels.de/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.crazylabels.de/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.crazylabels.de/customer_authentication/redirect, https://www.crazylabels.de/collections/dymo-blanko, https://www.crazylabels.de/collections/dymo-farbig, https://www.crazylabels.de/collections/dymo-etiketten, https://www.crazylabels.de/collections/zebra-etiketten and https://www.crazylabels.de/collections/brother and 9 others 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 94 found) and read each the way a search engine does.
3 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=undefined&tm=gtm002&Ver=2&mid=311688be-4a21-499d-ba88-c068733f4db6&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Crazylabels%20%7C%20Etiketten%20bestellen%20.
68 small tap targets
68 of 181 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
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 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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. 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.
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 963 words of copy
The homepage carries about 963 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) loads with the page.
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 crazylabels.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Schema Plus For Seo · Inbox · Kip Payment Methods · Klaviyo Email Marketing Sms · Reorder Master · Trymry · Simple Reorder · hulkapps.com · trustedshops.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on crazylabels.de, including 15 speed issues, 3 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.