mawilove.de website review

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

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

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

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

6 third-party services load with your homepage (Klaviyo, Google CDN and Shopify and others), adding 569 KiB and 332 ms of main-thread time.

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

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

1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

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

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

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

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 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “06 Ceo Serum”.

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

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

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.

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

6 buttons have no accessible name, so screen readers announce just “button”.

Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

6 images have no alt text, which hurts accessibility and image search.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 8 characters: “mawilove”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 44 pages on mawilove.de and 6 external pages.

https://www.mawilove.de/collections/produkte and https://www.mawilove.de/collections/all all use the title “produkte – mawilove”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mawilove.de/pages/couperose, https://www.mawilove.de/pages/story, https://www.mawilove.de/pages/unsere-core-values, https://www.mawilove.de/pages/contact and https://www.mawilove.de/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mawilove.de/pages/couperose, https://www.mawilove.de/pages/unsere-core-values and https://www.mawilove.de/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.mawilove.de/wp-content/uploads/ChIJk2Gpye6JsUcR8Mg7QPPFu-0.jpg.

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token ';'”.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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