weedshop.eu website review

A phone's processor spends 4.3 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Cookiebot and others), adding 1.2 MB and 776 ms of main-thread time.

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

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

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

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

About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Polyfills for old browsers add 80 KiB JavaScript that modern phones do not need.

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

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.

2 KiB could be saved by minifying JavaScript.

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

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

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

Scripts block taps and scrolling for 242 ms in total while the page loads. Good is under 200 ms.

Your homepage downloads 5.0 MB in 279 requests on a phone: images 2.1 MB (59), scripts 1.4 MB (78) and other files 1.3 MB (122). Under 2 MB keeps phones on slow connections fast.

WS_Halloweed_bundle_png.webp 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).

12 images (618 KiB) are 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.

4 images are downloaded at several times the size a phone draws them, for example WS_CBD_CBN_THCA_Olie_3Pak_feb_26.webp at 2,000 px wide, shown at 283 px. Resized copies would save about 222 KiB.

1 image further down the page (75 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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

14 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

Your title is only 11 characters: “Weedshop.eu”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “THCA”). One clear main headline is easier for people and search engines.

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

The homepage links to 172 pages on weedshop.eu and 4 external pages.

https://weedshop.eu/collections/news, https://weedshop.eu/collections/outlet and https://weedshop.eu/collections/bundles have no meta description, so Google writes the search snippet from whatever text it finds.

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

38 of 75 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 ()”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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 580 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before 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 (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 10 cookies, 1 of them by other companies (measured from a US location before any click).

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