viktilabs.eu website review

32 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

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

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

8 third-party services load with your homepage (posthog.com, Hotjar and viktilabs.de and others), adding 3.0 MB and 2.0 s of main-thread time.

posthog.com costs a phone 556 ms of main-thread work and 258 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.

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

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

Hotjar costs a phone 434 ms of main-thread work and 282 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.

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

viktilabs.de costs a phone 328 ms of main-thread work and 396 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 183 ms of main-thread work and 742 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.

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

19 KiB could be saved by minifying CSS.

13 KiB could be saved by minifying JavaScript.

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

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

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

Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Product Selection from Viktilabs”.

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

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

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

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

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

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

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

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.

Your homepage downloads 5.8 MB in 378 requests on a phone: scripts 3.6 MB (129), other files 989 KiB (165) and images 607 KiB (56). Under 2 MB keeps phones on slow connections fast.

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

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

42 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: 3 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Elements with visible text labels do not have matching accessible names. (21 elements).

There are 2 <h1> headlines (“Viktilabs” and “The Power of Nature.Laboratory Tested.”). One clear main headline is easier for people and search engines.

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

Structured data found ((untyped), BreadcrumbList, Organization and WebSite) but with 3 problems, for example “Organization: url points at a different host (https://www.viktilabs.de)”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 302 pages on viktilabs.eu and 8 external pages.

Your Organization JSON-LD is missing 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.

https://www.viktilabs.eu/policies/shipping-policy, https://www.viktilabs.eu/pages/contact, https://www.viktilabs.eu/pages/news, https://www.viktilabs.eu/collections/alle-produkte, https://www.viktilabs.eu/collections/bestseller and https://www.viktilabs.eu/collections/angebote have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.viktilabs.eu/collections/alle-produkte, https://www.viktilabs.eu/collections/bestseller, https://www.viktilabs.eu/collections/angebote, https://www.viktilabs.eu/collections/neu-im-shop, https://www.viktilabs.eu/collections/antioxidants and https://www.viktilabs.eu/collections/fatty-acids and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.viktilabs.eu/collections/neu-im-shop took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://www.viktilabs.eu/.

49 of 130 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.viktilabs.eu/cdn/shop/t/208/assets/ndnapps-storelocator.css?v=43564' because i…”.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, Klaviyo 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.

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