purpleleafshop.de website review

8 third-party services load with your homepage (Shopify, cdnhub.co and codeblackbelt.com and others), adding 28.4 MB and 5 ms of main-thread time.

Shopify costs a phone 5 ms of main-thread work and 28.4 MB 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.

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

5 images could be 699 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

The page has 1,992 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 64 KiB of CSS is downloaded but never applied on this page.

5 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The layout shifts by 1.018 while loading, so content jumps under the reader's thumb. Good is under 0.1.

The first text or image appears after 3.0 s on a phone. Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 176 ms to 243 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

27 images have no width and height attributes, so the layout jumps as each one loads.

Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “🔄”. Most of its time is element render delay (1.2 s).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 29.1 MB in 115 requests on a phone: media 19.1 MB (3), images 9.0 MB (53) and scripts 709 KiB (45). Under 2 MB keeps phones on slow connections fast.

42e6756e4b73e7a7107f98ef99a66485.gif weighs 19.8 MB. On a phone connection a single image that size takes seconds.

1 image (19.8 MB) 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.

2026_-1250x1800_0699baaf-e037-410d-ad55-edea9c54fd8b.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).

5 images are downloaded at several times the size a phone draws them, for example 2026_-1250x1800_0699baaf-e037-410d-ad55-edea9c54fd8b.jpg at 1,250 px wide, shown at 390 px. Resized copies would save about 74 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 8.24 g of CO₂e: 988.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

7 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

2 visible links have no text or label, so screen readers cannot say where they go.

Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, Organization and WebSite) but with 3 problems, for example “Organization: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 377 pages on purpleleafshop.de and 31 external pages.

Your Organization JSON-LD is missing name, 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.

We fetched 15 pages linked from your homepage (of 119 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://purpleleafshop.de/cdn/shop/t/51/assets/Italy_119x69.jpg?v=12423.

6 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

5 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 187 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.