dangarden.de website review

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

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

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

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

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

4 images could be 231 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

Google Tag Manager costs a phone 529 ms of main-thread work and 503 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.

About 475 KiB of JavaScript is downloaded but never used on this page.

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

Klaviyo costs a phone 308 ms of main-thread work and 324 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.

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

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

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

6 KiB could be saved by minifying JavaScript.

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.

5 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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 4.5 MB in 341 requests on a phone: images 1.9 MB (42), scripts 1.4 MB (84) and other files 1,011 KiB (203). Under 2 MB keeps phones on slow connections fast.

1 image (39 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 1.26 g of CO₂e: 151.6 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”.

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

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

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (6 elements).

Your title is only 21 characters: “Dangarden – dangarden”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 67 characters: “Dangarden Premium Outdoor Geschmackvolles Design für Lebensgenießer”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“November Sale” and “Design für Lebensgenießer”). One clear main headline is easier for people and search engines.

The homepage links to 278 pages on dangarden.de and 10 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/ and https://dangarden.de/collections/dangarden all use the title “Dangarden – dangarden”. Search engines can't tell which page to show for a search, so each competes with the others.

https://dangarden.de/pages/about-us, https://dangarden.de/pages/faq, https://dangarden.de/pages/contacts, https://dangarden.de/collections/dangarden, https://dangarden.de/collections/grillar and https://dangarden.de/collections/utekok and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://dangarden.de/pages/faq and https://dangarden.de/pages/contacts have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

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

Large scripts ship without source maps.

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.

Social proof on the homepage: 779 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,749 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 15 cookies (measured from a US location before any click).

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