Website review, no card needed

somavedic.ch logo

somavedic.ch website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 81 checks

This review found 36 issues worth fixing on somavedic.ch, 11 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
3.3 s2.3 sMay 16Aug 292.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20262.9 s
Jun 27, 20262.8 s
Jul 4, 20262.7 s
Jul 11, 20262.5 s
Jul 18, 20262.4 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.6 s
Aug 15, 20262.8 s
Aug 22, 20262.9 s
Aug 29, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
159 ms123 msMay 16Aug 15152 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026151 ms
May 23, 2026149 ms
May 30, 2026152 ms
Jun 6, 2026155 ms
Jun 13, 2026152 ms
Jun 20, 2026135 ms
Jun 27, 2026129 ms
Jul 4, 2026127 ms
Jul 11, 2026127 ms
Jul 18, 2026132 ms
Jul 25, 2026129 ms
Aug 1, 2026128 ms
Aug 8, 2026145 ms
Aug 15, 2026152 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 somavedic.ch (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. somavedic.ch at 0.4 s0.4 s
  2. somavedic.ch at 0.8 s0.8 s
  3. somavedic.ch at 1.1 s1.1 s
  4. somavedic.ch at 1.5 s1.5 s
  5. somavedic.ch at 1.9 s1.9 s
  6. somavedic.ch at 2.3 s2.3 s
  7. somavedic.ch at 2.6 s2.6 s
  8. somavedic.ch at 3.0 s3.0 s

Speed

11 to fix46
  • Improve image delivery

    1.1 s · 244 KiB

    5 images could be 244 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    450 ms · 548 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Klaviyo and somavedic.com and others), adding 1.4 MB and 715 ms of main-thread time.

  • Render-blocking requests

    650 ms

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

  • Reduce unused CSS

    300 ms · 73 KiB

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

  • Google Tag Manager adds 257 ms

    257 ms

    Google Tag Manager costs a phone 257 ms of main-thread work and 368 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: 2.9 s

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

  • 2,655 HTML elements

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

  • Klaviyo adds 115 ms

    115 ms

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

  • Shopify adds 92 ms

    92 ms

    Shopify costs a phone 92 ms of main-thread work and 353 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.

  • Use efficient cache lifetimes

    150 ms · 85 KiB

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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: 10 ms

    10 ms

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

Core Web Vitals

5 to fix34
  • Cumulative Layout Shift: 1

    1

    The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 16.1 s

    16.1 s

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

  • Largest Contentful Paint: 6.7 s

    6.7 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

  • 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
  • Total Blocking Time: 165 ms

    165 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix75
  • Page weight: 3.8 MB in 272 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 272 requests on a phone: scripts 1.5 MB (84), images 943 KiB (26) and other files 918 KiB (145). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    122 KiB

    5 images are downloaded at several times the size a phone draws them, for example slide-2-desktop_and_mobile_x900.jpg at 1,400 px wide, shown at 390 px. Resized copies would save about 122 KiB.

  • About 1.1 g of CO₂ per visit

    1.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.1 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

10 to fixGoogle 7887
  • Certain ARIA roles must be contained by particular parents (8 elements)

    Certain ARIA roles must be contained by particular parents: 8 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • 14 text elements with low contrast

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

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • <dt> and <dd> elements must be contained by a <dl> (1 element)

    <dt> and <dd> elements must be contained by a <dl>: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has 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.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • 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
  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 8587
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Somavedic Schweiz – Raum, Wasser & Körper harmonisieren – Somavedic Germany”.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.somavedic.de)”.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 101 internal links, 57 external

    The homepage links to 101 pages on somavedic.ch and 57 external pages.

6 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “Somavedic harmonisiert Raum, Wasser & Körper. 60 Tage Rückgabe, 99 % Zufriedenheit, weltweiter Versand, wissenschaftlic…”.

  • One H1 headline

    Your main headline reads: “Somavedic Germany”.

  • Canonical URL set

    The canonical URL is https://www.somavedic.ch/.

  • 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://www.somavedic.ch/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 (3,034 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.somavedic.ch/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.somavedic.ch/pages/wissenschaft, https://www.somavedic.ch/collections/all and https://www.somavedic.ch/pages/kontakt have 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 30 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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_TUNNEL_CONNECTION_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    31 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “e-shop”.

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 22 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

Privacy and tracking

1 to fix
  • 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.

  • 22 cookies set on arrival

    22

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

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

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 somavedic.ch, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Assortion · Klaviyo Email Marketing Sms · Gsc Countdown Timer · Stape Remix · Orbe Geolocation · Restockrocket · getsitecontrol.com · Selleasy · builder.io

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
jQuery
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 36 issues on somavedic.ch, including 16 speed issues, 3 SEO 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