Website review, no card needed

spacegarden.de logo

spacegarden.de website review

Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 82 checks

This review found 28 issues worth fixing on spacegarden.de, 12 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
1.8 s1.4 sJul 11Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
Jul 11, 20261.6 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.5 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
220 ms153 msSep 5Nov 7188 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 2026161 ms
Sep 12, 2026163 ms
Sep 19, 2026177 ms
Sep 26, 2026187 ms
Oct 17, 2026212 ms
Oct 24, 2026208 ms
Oct 31, 2026193 ms
Nov 7, 2026188 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 spacegarden.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. spacegarden.de at 0.7 s0.7 s
  2. spacegarden.de at 1.4 s1.4 s
  3. spacegarden.de at 2.1 s2.1 s
  4. spacegarden.de at 2.8 s2.8 s
  5. spacegarden.de at 3.5 s3.5 s
  6. spacegarden.de at 4.2 s4.2 s
  7. spacegarden.de at 4.9 s4.9 s
  8. spacegarden.de at 5.7 s5.7 s

Speed

8 to fix56
  • Reduce unused JavaScript

    1.8 s · 698 KiB

    About 698 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 56

    56/100

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

  • Improve image delivery

    865 KiB

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    300 ms · 472 KiB

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

  • Shopify adds 124 ms

    124 ms

    Shopify costs a phone 124 ms of main-thread work and 1.4 MB 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: 2.5 s

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

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    86 KiB

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

  • Minify JavaScript

    79 KiB

    79 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix100
  • First Contentful Paint: 7.0 s

    7.0 s

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

  • Largest Contentful Paint: 7.0 s

    7.0 s

    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 text “Für ein gesundes und langes Leben.”.

  • Time to Interactive: 13.6 s

    13.6 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • 3 images without width and height

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

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

    +18%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 187 ms

    187 ms

    Real visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.06

    0.06

    For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 422 ms

    422 ms

    Real visitors wait 422 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Total Blocking Time: 174 ms

    174 ms

    Scripts block the page for only 174 ms while loading. Good is under 200 ms.

  • 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.2 MB in 252 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 252 requests on a phone: scripts 1.9 MB (99), images 1,021 KiB (19) and other files 846 KiB (113). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    131 KiB

    2 images are downloaded at several times the size a phone draws them, for example sg_team_hands_v2.png at 1,536 px wide, shown at 354 px. Resized copies would save about 131 KiB.

  • About 1.2 g of CO₂ per visit

    1.18 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

7 to fixGoogle 8790
  • 23 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

Google 92100
  • 67 internal links, 7 external

    The homepage links to 67 pages on spacegarden.de and 7 external pages.

8 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Hochdosierte Longevity-Supplements und Biohacking-Kapseln nach dem Reinsubstanzenprinzip. Laborgeprüft, vegan, Versand …”.

  • One H1 headline

    Your main headline reads: “Für ein gesundes und langes Leben.”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Longevity Supplements & Biohacking | Spacegarden”.

  • Canonical URL set

    The canonical URL is https://spacegarden.de/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ItemList, Organization and WebSite.

  • 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://spacegarden.de/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix81
  • 2 pages share a title

    https://spacegarden.de/collections/sport and https://spacegarden.de/collections/sport/Sport-&-Bewegung all use the title “Sport Supplements & Regeneration kaufen | Spacegarden”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://spacegarden.de/collections/sport and https://spacegarden.de/collections/sport/Sport-&-Bewegung use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://spacegarden.de/collections/sport/Sport-&-Bewegung, whose canonical is https://spacegarden.de/collections/sport. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://spacegarden.de/pages/uber-uns has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    14 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 977 words of copy

    The homepage carries about 977 words of visible text.

5 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Shop”.

  • 7 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 0 phone links 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, Hotjar 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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 2 of them by other companies (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.

  • 46 other companies contacted

    Loading the homepage contacts 46 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 spacegarden.de, 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 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Timesact Pre Order · Eaze Button · Reelup Shoppable Videos Reels · Omnisend · Upcart · cloudfront.net · loox.io · sealsubscriptions.com · gorgias.chat · shappify.com · boldapps.net · archive-digger.com · trustedshops.com · 9gtb.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

E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on spacegarden.de, including 13 speed issues and 1 conversion gap. 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