yourmood.ch website review

Shopify costs a phone 2.3 s of main-thread work and 25.3 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.

negate.io costs a phone 1.7 s of main-thread work and 40 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.

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

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

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

8 third-party services load with your homepage (Shopify, negate.io and YouTube and others), adding 26.9 MB and 5.5 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page.

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

YouTube costs a phone 728 ms of main-thread work and 988 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 209 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 420 ms faster on a phone.

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

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

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

19 KiB could be saved by minifying JavaScript.

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

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

9 KiB could be saved by minifying CSS.

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.

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

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

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nos propositions en avant-première”.

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

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

For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

The layout shifts by 0.109 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your homepage downloads 36.4 MB in 688 requests on a phone: media 30.2 MB (4), scripts 3.0 MB (254) and other files 2.3 MB (374). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

Structured data found (FAQPage, ItemList, Organization and Product) but with 1 problem, for example “Product: no offers (price) block”.

The homepage links to 351 pages on yourmood.ch and 15 external pages.

https://www.yourmood.net/en/pages/black-friday-bague-interchangeable and https://www.yourmood.net/pages/black-friday-bague-interchangeable all use the title “Black Friday bague interchangeable : avant-première | mood – Mood Col…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.yourmood.net/en/pages/black-friday-bague-interchangeable and https://www.yourmood.net/pages/black-friday-bague-interchangeable use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.yourmood.net/pages/black-friday-bague-interchangeable, whose canonical is https://www.yourmood.net/en/pages/black-friday-bague-interchangeable. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.yourmood.net/en/collections/bijoux-montagne, https://www.yourmood.net/en/collections/bijoux-suisses, https://www.yourmood.net/en/collections/bijoux-spirituels, https://www.yourmood.net/en/collections/bijoux-voyage, https://www.yourmood.net/en/collections/bijoux-animaux and https://www.yourmood.net/en/collections/bijoux-white-blanc and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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

The homepage carries about 2,150 words of visible text.

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