somavedic.de website review

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

About 658 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 load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 1.3 MB and 931 ms of main-thread time.

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

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

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

About 71 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 costs a phone 323 ms of main-thread work and 352 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.

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

Klaviyo costs a phone 167 ms of main-thread work and 318 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 costs a phone 138 ms of main-thread work and 347 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.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.8 MB in 272 requests on a phone: scripts 1.5 MB (84), images 947 KiB (25) and other files 932 KiB (147). Under 2 MB keeps phones on slow connections fast.

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.

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

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 on the page fail this check, rated critical by axe-core.

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 on the page fail this check, rated serious by axe-core.

<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 have no alt text, which hurts accessibility and image search.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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 on the page fails this check, rated minor by axe-core.

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

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

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

The homepage links to 108 pages on somavedic.de and 50 external pages.

https://www.somavedic.de/collections/all and https://www.somavedic.de/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.somavedic.de/pages/wissenschaft, https://www.somavedic.de/collections/all, https://www.somavedic.de/pages/bewertungen and https://www.somavedic.de/pages/kontakt have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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

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.

Opening the homepage sets 21 cookies, 2 of them by other companies (measured from a US location before any click).

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