monapure.com website review

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

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

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

8 third-party services load with your homepage (Clarity, Klaviyo and TikTok and others), adding 984 KiB and 1.6 s of main-thread time.

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

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

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

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

Clarity costs a phone 487 ms of main-thread work and 30 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.

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

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

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.

For real visitors the layout shifts by 0.65 (75th percentile). Good is under 0.1.

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

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

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Website_Banner_Der_Eisenfreund_950x1650px_a7183e75-a3c2-437…”.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 401 ms to 457 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 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.4 MB in 502 requests on a phone: scripts 2.1 MB (116), other files 1.5 MB (297) and images 1.2 MB (49). Under 2 MB keeps phones on slow connections fast.

Website_Banner_Kollagen_950x1650px_c563b0dd-4f5f-4f07-8688-e is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (25 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.52 g of CO₂e: 182.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

5 elements hidden from screen readers can still receive keyboard focus.

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“” and “Lerne noch mehr über die Schilddrüse.”). One clear main headline is easier for people and search engines.

The homepage links to 130 pages on monapure.com and 13 external pages.

https://miavola.de/products/masterclass declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://miavola.de/collections/frontpage is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://miavola.de/products/masterclass all use the title “miavola - Nährstoffkomplexe für die Schilddrüse”. Search engines can't tell which page to show for a search, so each competes with the others.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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 38 cookies, 1 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 53 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.