plus420.de website review

6 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.0 s faster on a phone.

About 173 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.

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

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

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

Shopify costs a phone 176 ms of main-thread work and 421 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.

8 third-party services load with your homepage (Shopify, Facebook and Trust Pilot and others), adding 676 KiB and 356 ms of main-thread time.

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

3 long tasks block the main thread while loading, the longest for 153 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 36.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobiles Bild”.

The page becomes fully interactive after 37.0 s. Good is under 3.8 s.

Visually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 8.6 MB in 200 requests on a phone: images 7.0 MB (16), other files 755 KiB (89) and scripts 704 KiB (56). Under 2 MB keeps phones on slow connections fast.

5 images weigh 5.2 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example mobile_banner_6666_5851b78a-6032-47f9-b86d-c6f188fd9a47.png at 2,917 px wide, shown at 390 px. Resized copies would save about 2.0 MB.

4 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (38 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.

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

29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 4 characters: “+420”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 43 pages on plus420.de and 0 external pages.

/collections/bestseller, /collections/vapes, /collections/edibles-1, /collections/bluten-2, /collections/hasch and /collections/headshop and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /products/%F0%9F%8C%88-skittles-h2-superior, whose canonical is /products/%f0%9f%8c%88-skittles-h2-superior. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/edibles-1, /collections/bluten-2, /collections/hasch, /collections/smartshop and /collections/headshop have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/edibles-1, /collections/bluten-2, /collections/hasch, /collections/smartshop and /collections/headshop have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/products/amnesia-superior-sativa, /products/%F0%9F%8C%88-skittles-h2-superior, /blogs/news/blauer-lotus, /blogs/news/10-oh-hhc and /blogs/news/wo-kann-ich-hhc-bluten-in-koln-kaufen took over 3 s to send their HTML from our server.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

plus420.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 366 words of visible text.

DMARC is set to p=none, so mail pretending to be plus420.de is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 8 cookies, 1 of them by other companies (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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.