vitori.de website review

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

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

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

4 images could be 236 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

About 168 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 850 ms faster on a phone.

8 third-party services load with your homepage (Klaviyo, cloudfront.net and Klarna and others), adding 1.6 MB and 839 ms of main-thread time.

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

About 557 KiB of JavaScript is downloaded but never used on this page.

106 KiB could be saved by minifying CSS.

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

cloudfront.net costs a phone 155 ms of main-thread work and 296 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 92 ms of main-thread work and 367 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

45 KiB could be saved by minifying JavaScript.

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

11 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.3 MB in 254 requests on a phone: scripts 1.5 MB (92), images 1.3 MB (31) and other files 996 KiB (108). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example efeu-blackweek.jpg at 2,400 px wide, shown at 391 px. Resized copies would save about 172 KiB.

1 image further down the page (114 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 82 pages on vitori.de and 10 external pages.

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.

https://www.vitori.de/collections/neu-im-sortiment, https://www.vitori.de/collections/kristallprodukte, https://www.vitori.de/pages/vitori-frequenz-app-landingpage, https://www.vitori.de/collections/meditationen-beats, https://www.vitori.de/pages/erfahrungen and https://www.vitori.de/pages/wirkung and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.vitori.de/products/vitori%C2%AE-premium-saunadecke, whose canonical is https://www.vitori.de/products/vitori%c2%ae-premium-saunadecke. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.vitori.de/pages/erfahrungen and https://www.vitori.de/pages/beratung-interessenten have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 402 ()”.

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

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

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 2,192 words of visible text.

Before a visitor clicks anything, the page loads HubSpot, Klaviyo, Meta Pixel, Microsoft Clarity and TikTok Pixel (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 17 cookies, 3 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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.