mygeisha.ro website review

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

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

Your mobile performance score is 70. 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 650 ms.

8 third-party services load with your homepage (Klaviyo, userway.org and cookiebot.eu and others), adding 1.2 MB and 396 ms of main-thread time.

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

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

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

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

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

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

Polyfills for old browsers add 29 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.

3 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three bottles of exfoliating hand and body wash labeled "Sa…”.

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

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

Your homepage downloads 4.3 MB in 323 requests on a phone: images 1.7 MB (45), scripts 1.3 MB (133) and other files 890 KiB (101). Under 2 MB keeps phones on slow connections fast.

Slider_RO_mobile_13.jpg 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 is downloaded at several times the size a phone draws it, for example anpc-sal.webp at 500 px wide, shown at 150 px. Resized copies would save about 11 KiB.

1 image (57 KiB) is 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.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 315 pages on mygeisha.ro and 19 external pages.

https://mygeisha.ro/pages/jasmine-in-the-sun-the-new-fragrance and https://mygeisha.ro/pages/what-burns-reveals-burning-love-collection are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://mygeisha.ro/pages/jasmine-in-the-sun-the-new-fragrance, https://mygeisha.ro/pages/what-burns-reveals-burning-love-collection and https://mygeisha.ro/collections/makeup-my-geisha use the same meta description. A description written for each page earns more clicks.

https://mygeisha.ro/pages/jasmine-in-the-sun-the-new-fragrance and https://mygeisha.ro/pages/what-burns-reveals-burning-love-collection have no <h1> headline, so visitors and search engines get no clear main topic.

https://mygeisha.ro/pages/what-burns-reveals-burning-love-collection, https://mygeisha.ro/collections/makeup-my-geisha, https://mygeisha.ro/products/my-geisha-cannabis-lost-island-extrait-de-parfum, https://mygeisha.ro/collections/parfumuri-unisex, https://mygeisha.ro/collections/extract-de-parfum and https://mygeisha.ro/collections/apa-de-parfum and 5 others took over 3 s to send their HTML from our server.

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

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

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

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies (measured from a US location before any click).

Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.