nomadicstateofmind.fr website review

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

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

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

8 third-party services load with your homepage (Shopify, nomadicstateofmind.com and Clarity and others), adding 5.7 MB and 839 ms of main-thread time.

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

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

nomadicstateofmind.com costs a phone 165 ms of main-thread work and 3.8 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.

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

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

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

6 long tasks block the main thread while loading, the longest for 186 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.

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

55 KiB could be saved by minifying JavaScript.

About 25 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 8.1 MB in 580 requests on a phone: scripts 3.3 MB (253), images 3.1 MB (53) and other files 929 KiB (194). Under 2 MB keeps phones on slow connections fast.

4 images (369 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.

4 images further down the page (292 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 2.30 g of CO₂e: 276.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

8 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 131 pages on nomadicstateofmind.fr and 4 external pages.

https://nomadicstateofmind.fr/collections and https://nomadicstateofmind.fr/collections/nos-best-seller all use the title “Collections”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nomadicstateofmind.fr/pages/faq has no meta description, so Google writes the search snippet from whatever text it finds.

https://nomadicstateofmind.fr/collections and https://nomadicstateofmind.fr/collections/nos-best-seller 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://nomadicstateofmind.fr/collections/nos-best-seller, whose canonical is https://nomadicstateofmind.fr/collections. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://nomadicstateofmind.fr/collections/toutes-les-sandales-en-corde, https://nomadicstateofmind.fr/collections/sandales-en-corde-femme, https://nomadicstateofmind.fr/collections/sandales-en-corde-avec-semelles and https://nomadicstateofmind.fr/collections/collection-outlet have no <h1> headline, so visitors and search engines get no clear main topic.

https://nomadicstateofmind.fr/collections/toutes-les-sandales-en-corde, https://nomadicstateofmind.fr/collections/sandales-en-corde-femme and https://nomadicstateofmind.fr/collections/collection-outlet have 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.

https://nomadicstateofmind.fr/collections/nos-best-seller took over 3 s to send its HTML from our server.

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

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.

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: 16 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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