sprossensamen.ch website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user LCP: 2.6 s

  2.6 s

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

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

  +15%

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

• Largest content (LCP) held steady for real visitors

  -5%

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

• Page weight: 4.3 MB

  4.3 MB

  Your homepage downloads 4.3 MB on a phone, 449 KiB of it images (10%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  Olivenoel_4x5_NUR_WEBP.png 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).

  Elements (1)

• 1 image far larger than shown

  12 KiB

  1 image is downloaded at several times the size a phone draws it, for example Olivenoel_4x5_NUR_WEBP.png at 1,200 px wide, shown at 390 px. Resized copies would save about 12 KiB.

  Elements (1)

• About 1.2 g of CO₂ per visit

  1.23 g

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

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (1)

• 1 tap target too small

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

  Elements (1)

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

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

  Elements (3)

• Document should not have more than one contentinfo landmark (1 element)

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

  Elements (1)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  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.

  Elements (1)

• Headings skip levels

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

  View source

• Title is long (86 characters)

  Your title is 86 characters, so Google will cut it off around 60: “Sprossen selber ziehen | Award-Shop 2024 | 110% Zufriedenheitsgarantie – sprossensamen”.

  View source

• Meta description is long (178 characters)

  Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• One H1 headline

  Your <h1> is empty.

  View source

• 201 internal links, 13 external

  The homepage links to 201 pages on sprossensamen.ch and 13 external pages.

• Organization data is thin (2 of 6 facts)

  Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

• 15 internal pages checked

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

• 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”.

• 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.

• Local business without LocalBusiness data

  Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  View source

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• 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 1,003 words of copy

  The homepage carries about 1,003 words of visible text.

• 6 trackers load before any consent

  6

  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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

• 20 cookies set on arrival

  20

  Opening the homepage sets 20 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.

• 38 other companies contacted

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