mythicessence.com website review

30 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

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

5 third-party services load with your homepage (Shopify, shop.app and Judge.me and others), adding 34.5 MB and 95 ms of main-thread time.

Instagram costs a phone 0 ms of main-thread work and 33.3 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.

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

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

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

Shopify costs a phone 91 ms of main-thread work and 1.1 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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.

3 KiB JavaScript is shipped twice across bundles.

Your largest element takes 14.2 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 14.7 s. Good is under 3.8 s.

Visually, the page fills in at 5.2 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-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 105 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 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 36.6 MB in 316 requests on a phone: media 32.5 MB (10), images 2.3 MB (40) and other files 1.1 MB (148). Under 2 MB keeps phones on slow connections fast.

rn-image_picker_lib_temp_75657acf-ce0c-4e41-9495-4d42c33e0a0 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).

3 images are downloaded at several times the size a phone draws them, for example rbt_tr.png at 1,254 px wide, shown at 52 px. Resized copies would save about 383 KiB.

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

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

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

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

All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.

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

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. (1 element).

Your title is 127 characters, so Google will cut it off around 60: “Mythic Essence | Perfumes de calidad – Mythic Essence - Perfumes de equivalencia de calid…”.

There are 2 <h1> headlines (“” and “HAZTE NOTAR.”). One clear main headline is easier for people and search engines.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 108 pages on mythicessence.com and 10 external pages.

https://mythicessence.com/collections/novedades, https://mythicessence.com/collections/all, https://mythicessence.com/pages/contact, https://mythicessence.com/collections/niche, https://mythicessence.com/collections/woman and https://mythicessence.com/collections/man and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://mythicessence.com/collections/novedades/products/m_105_phantom, whose canonical is https://mythicessence.com/products/m_105_phantom. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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

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

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

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

The page uses urgency cues (a countdown or limited-time wording).

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