magicperfume.co website review

The page goes through 2 redirects before it starts loading, costing about 18.3 s. Link and advertise the final URL directly.

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

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

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 2.7 MB and 3.4 s of main-thread time.

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

Shopify costs a phone 903 ms of main-thread work and 1.2 MB 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.

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

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

29 KiB could be saved by minifying JavaScript.

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

The HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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.

2 KiB JavaScript is shipped twice across bundles.

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.

Real visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.

Your largest element takes 34.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Duftzwillinge in Premiumqualität. Für jeden Tag und jede Se…”.

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

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

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

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

Real visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

9 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 121 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.9 MB in 914 requests on a phone: scripts 3.3 MB (290), images 3.1 MB (90) and other files 2.7 MB (389). Under 2 MB keeps phones on slow connections fast.

10 images further down the page (531 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example 78325675e2294cd3b5379c7552ee5c75.thumbnail.0000000000.jpg at 600 px wide, shown at 175 px. Resized copies would save about 67 KiB.

7 images (282 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

Scrollable region must have keyboard access: 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.

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

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

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

There are 2 <h1> headlines (“” and “Duftzwillinge in Premiumqualität. Für jeden Tag u…”). One clear main headline is easier for people and search engines.

Your meta description is 166 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 171 pages on magicperfume.co and 7 external pages.

https://magicperfume.co/collections/all, https://magicperfume.co/policies/shipping-policy, https://magicperfume.co/collections/fuer-maenner, https://magicperfume.co/collections/fuer-frauen and https://magicperfume.co/collections/bestseller-singles have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

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