nomadicstateofmindmea.com website review

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

About 488 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

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

8 third-party services load with your homepage (loox.io, nomadicstateofmind.com and Shopify and others), adding 5.5 MB and 815 ms of main-thread time.

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

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

51 KiB could be saved by minifying JavaScript.

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

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

Shopify costs a phone 142 ms of main-thread work and 952 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,590 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

The HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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 21.0 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 21.6 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 6.9 MB in 504 requests on a phone: images 3.6 MB (47), scripts 1.6 MB (198) and other files 1,010 KiB (198). Under 2 MB keeps phones on slow connections fast.

romano-black-shot-1.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).

3 images (226 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.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your meta description is 294 characters; Google truncates after about 160, so the end of your pitch is cut.

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

Your <h1> is empty.

The homepage links to 49 pages on nomadicstateofmindmea.com and 16 external pages.

https://www.nomadicstateofmindmea.com/collections/all, https://www.nomadicstateofmindmea.com/collections/slingback-sandals, https://www.nomadicstateofmindmea.com/collections/sandals-with-laces, https://www.nomadicstateofmindmea.com/collections/platforms, https://www.nomadicstateofmindmea.com/collections/size-3-7-eu-36-40 and https://www.nomadicstateofmindmea.com/collections/just-landed and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nomadicstateofmindmea.com/collections/all, https://www.nomadicstateofmindmea.com/pages/about-us, https://www.nomadicstateofmindmea.com/collections/unisex-sandals, https://www.nomadicstateofmindmea.com/collections/slingback-sandals, https://www.nomadicstateofmindmea.com/collections/sandals-with-laces and https://www.nomadicstateofmindmea.com/collections/sandals-with-sole and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.nomadicstateofmindmea.com/collections/all, https://www.nomadicstateofmindmea.com/pages/about-us, https://www.nomadicstateofmindmea.com/collections/unisex-sandals, https://www.nomadicstateofmindmea.com/collections/slingback-sandals, https://www.nomadicstateofmindmea.com/collections/sandals-with-laces and https://www.nomadicstateofmindmea.com/collections/sandals-with-sole and 9 others 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.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d38dvuoodjuw9x.cloudfront.net/ml-flag.css' from origin 'https://www.nomadicstateof…”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage has only about 180 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.