kijimea.at website review

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

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

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

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

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

8 third-party services load with your homepage (Reviews.io, Klaviyo and boostcommerce.io and others), adding 1.8 MB and 853 ms of main-thread time.

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

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

Shopify costs a phone 111 ms of main-thread work and 797 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 151 ms of main-thread work and 355 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.

95 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

18 long tasks block the main thread while loading, the longest for 144 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).

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

7 KiB could be saved by minifying JavaScript.

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.

3 KiB could be saved by minifying CSS.

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 10.9 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 21.9 s. Good is under 3.8 s.

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

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

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

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-10-31, real Chrome visitors' tap response (inp) went from 187 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.5 MB in 334 requests on a phone: scripts 1.7 MB (107), images 1.2 MB (40) and other files 921 KiB (115). Under 2 MB keeps phones on slow connections fast.

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

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

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

6 visible links have no text or label, so screen readers cannot say where they go.

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

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

The homepage links to 116 pages on kijimea.at and 24 external pages.

https://kijimea.at/pages/personliche-beratung-4 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://kijimea.at/pages/personliche-beratung-4 and https://kijimea.at/pages/personliche-beratung all use the title “Persönliche Beratung | Produkte von den Mikrobiomexperten”. Search engines can't tell which page to show for a search, so each competes with the others.

https://kijimea.at/collections/alle-produkte, https://kijimea.at/pages/personliche-beratung-4, https://kijimea.at/pages/abo-service, https://kijimea.at/pages/experteninterview-mikrobiom, https://kijimea.at/pages/stiftung-warentest and https://kijimea.at/pages/personliche-beratung 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://kijimea.at/products/kijimea-regularis-old, whose canonical is https://kijimea.at/products/kijimea-regularis. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://kijimea.at/collections/alle-produkte, https://kijimea.at/pages/personliche-beratung-4, https://kijimea.at/products/kijimea-reizdarm-pro, https://kijimea.at/products/kijimea-k53-advance, https://kijimea.at/products/kijimea-floracare and https://kijimea.at/pages/abo-service and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://edge.optimeleon.com/b/U2BaPzfnIPS7.js' from origin 'https://kijimea.at' has been blocked b…”.

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

Social proof on the homepage: 425 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (6 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Hotjar and Klaviyo (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 12 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.