knitting-paradise.de website review

59 files are served with short cache lifetimes, so returning visitors download them again (20.7 MB).

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

25 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.0 s.

About 622 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.

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

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

78 KiB could be saved by minifying JavaScript.

48 KiB could be saved by minifying CSS.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

2 third-party services load with your homepage (cloudflare.com and Cloudflare CDN), adding 31 KiB and 13 ms of main-thread time.

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

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

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

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

Visually, the page fills in at 7.4 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 20.9 MB in 64 requests on a phone: images 19.2 MB (11), scripts 759 KiB (27) and stylesheets 642 KiB (21). Under 2 MB keeps phones on slow connections fast.

8 images weigh 18.5 MB together. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example DJI_0048.jpg at 1,575 px wide, shown at 390 px. Resized copies would save about 7.5 MB.

11 images (19.3 MB) 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.

DJI_0048.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).

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 71 characters, so Google will cut it off around 60: “Dorfgarten – Frisches Gemüse aus der Region | Gemüsebox & Market Garden”.

The homepage links to 25 pages on knitting-paradise.de and 0 external pages.

There is no https://dorfgarten.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://dorfgarten.com/kontakt-2 and https://dorfgarten.com/impressum are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://dorfgarten.com/kontakt-2, https://dorfgarten.com/impressum and https://dorfgarten.com/portfolio/datenschutz have no meta description, so Google writes the search snippet from whatever text it finds.

https://dorfgarten.com/portfolio/handarbeit, https://dorfgarten.com/portfolio/frisch, https://dorfgarten.com/portfolio/regionales-gemuese, https://dorfgarten.com/portfolio/ungespritztes-gemuese-und-blumen, https://dorfgarten.com/portfolio/blumen and https://dorfgarten.com/portfolio/leidenschaft and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://dorfgarten.com/portfolio/gemuesepower-das-buch has 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.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

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

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.

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 has only about 25 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.