mymense.com website review

Google Tag Manager costs a phone 4.2 s of main-thread work and 1.4 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.

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

alia-prod.com costs a phone 1.2 s of main-thread work and 416 KiB 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 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and Shopify and others), adding 2.2 MB and 5.9 s of main-thread time.

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

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

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

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

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

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

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

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

13 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 187 ms to 253 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

13 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' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.8 MB in 120 requests on a phone: scripts 2.1 MB (34), images 313 KiB (24) and fonts 136 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

The homepage links to 132 pages on mymense.com and 13 external pages.

https://mymense.com/en/pages/periodenbademode and https://mymense.com/pages/periodenbademode all use the title “Period Swimwear and Bikini for Swimming | my.mense”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://mymense.com/en/pages/periodenbademode and https://mymense.com/pages/periodenbademode use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://mymense.com/pages/periodenbademode, whose canonical is https://mymense.com/en/pages/periodenbademode. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mymense.com/en/collections/periodenunterwasche-premium, https://mymense.com/en/pages/komfort-codzienny-bhs, https://mymense.com/en/pages/periodenbademode, https://mymense.com/en/products/magnesium-7-komplex, https://mymense.com/en/pages/finde-deine-grosse and https://mymense.com/en/pages/4-layer-technologie and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://mymense.com/en/products/bestseller-periodpanty-mix-match-copy-2-10 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

Large scripts ship without source maps.

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 850 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, Klaviyo and Meta Pixel and 2 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 30 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.