Website review, no card needed

derstahlgarten.at logo

derstahlgarten.at website review

Visit site (opens in a new tab)Reviewed 10 November 202634 issues · 78 checks

This review found 34 issues worth fixing on derstahlgarten.at, 12 of them high impact, across 78 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.6 s1.8 sMay 23Sep 122.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.4 s
May 30, 20262.2 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
173 ms79 msMay 23Sep 12138 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202690 ms
May 30, 202693 ms
Jun 6, 202691 ms
Jun 13, 202694 ms
Jun 20, 202694 ms
Jul 25, 2026158 ms
Aug 1, 2026160 ms
Aug 8, 2026162 ms
Aug 15, 2026144 ms
Aug 22, 2026125 ms
Aug 29, 2026129 ms
Sep 5, 2026123 ms
Sep 12, 2026138 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of derstahlgarten.at (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. derstahlgarten.at at 0.9 s0.9 s
  2. derstahlgarten.at at 1.7 s1.7 s
  3. derstahlgarten.at at 2.6 s2.6 s
  4. derstahlgarten.at at 3.4 s3.4 s
  5. derstahlgarten.at at 4.3 s4.3 s
  6. derstahlgarten.at at 5.1 s5.1 s
  7. derstahlgarten.at at 6.0 s6.0 s
  8. derstahlgarten.at at 6.8 s6.8 s

Speed

8 to fix79
  • Render-blocking requests

    1.7 s

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

  • 8 third-party services on the page

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

  • Mobile performance score: 79

    79/100

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

  • Improve image delivery

    910 KiB

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

  • Reduce unused JavaScript

    300 ms · 559 KiB

    About 559 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.

  • Google Tag Manager adds 516 ms

    516 ms

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

  • Main-thread work: 3.7 s

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

  • 2,576 HTML elements

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

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    148 KiB

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

  • Use efficient cache lifetimes

    110 KiB

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

  • Minify CSS

    107 KiB

    107 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    47 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 27 ms

    27 ms

    Your server sent the HTML in 27 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix89
  • Time to Interactive: 16.2 s

    16.2 s

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

  • Speed Index: 8.3 s

    8.3 s

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

  • Tap response (INP) got 43% slower for real visitors

    +43%

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Total Blocking Time: 293 ms

    293 ms

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir und unsere Geschäftspartner verwenden Technologien, ein…”. Most of its time is element render delay (2.7 s).

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Largest content (LCP) got 14% faster for real visitors

    -14%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 4.9 MB in 326 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 326 requests on a phone: images 2.1 MB (55), scripts 1.6 MB (86) and other files 978 KiB (167). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    166 KiB

    6 images are downloaded at several times the size a phone draws them, for example DE_herzformigesbeet.jpg at 400 px wide, shown at 96 px. Resized copies would save about 166 KiB.

  • 2 images in older formats

    2 images (112 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 below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.40 g

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

Accessibility

7 to fixGoogle 7589
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

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

  • 10 images without alt text

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

  • 119 links without text

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

  • All page content should be contained by landmarks (2 elements)

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9289
  • Title is short (15 characters)

    Your title is only 15 characters: “Der Stahlgarten”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 152 internal links, 24 external

    The homepage links to 152 pages on derstahlgarten.at and 24 external pages.

6 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Wir helfen Ihnen bei Ihrem Traumgarten. Für Profis und Gartenliebhaber. Alles aus Cortenstahl.”.

  • One H1 headline

    Your main headline reads: “Der Stahlgarten”.

  • Canonical URL set

    The canonical URL is https://derstahlgarten.at/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://derstahlgarten.at/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (717 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://derstahlgarten.at/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 8 pages without a meta description

    https://derstahlgarten.at/collections/hochbeete-und-pflanzkasten-massgeschneiderte, https://derstahlgarten.at/collections/hochbeete-und-pflanzkasten-rund, https://derstahlgarten.at/collections/beeteinfassungen-massgeschneiderte, https://derstahlgarten.at/collections/fugen-fur-beeteinfassungen, https://derstahlgarten.at/collections/massgeschneiderte-abmessungen and https://derstahlgarten.at/collections/hochbeete-und-pflanzkasten-rund-massgeschneiderte and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343237616&tm=gtm002&Ver=2&mid=1ba549f7-5cd8-4fd0-8693-f5b30deb8c7e&bo=1&sid=cc3f42a0dce611f1aba01d2e7d656e25&vid=cc3f61b0dce611f180501f204163741e&vids=1&msclkid=N&gtm_.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    42 of 44 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

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

  • No calls to action

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

  • Thin social proof

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

  • No risk reducer

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

  • About 610 words of copy

    The homepage carries about 610 words of visible text.

3 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.

  • 13 cookies set on arrival

    13

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

  • No consent tool detected

    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.

  • 44 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at derstahlgarten.at, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Microsoft Clarity · Ta Labels Badges · Lucky Orange · Variant Image Wizard Swatch · Apippa Custom Price Calc · Stape Remix · Klarna On Site Messaging · Order Value Booster · Boo Eu Withdrawal Button · Essential Free Gifts · amazonaws.com · trustedshops.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
SvelteKit
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on derstahlgarten.at, including 15 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25