nunalie.eu website review

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

Your mobile performance score is 37. 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, ZenDesk and accessibit.com and others), adding 1.7 MB and 899 ms of main-thread time.

1 image could be 129 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

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

Google Tag Manager costs a phone 398 ms of main-thread work and 489 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.

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

ZenDesk costs a phone 218 ms of main-thread work and 431 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.

accessibit.com costs a phone 80 ms of main-thread work and 299 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.

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 104 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 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.8 MB in 155 requests on a phone: media 2.6 MB (1), scripts 1.9 MB (83) and images 1.1 MB (7). Under 2 MB keeps phones on slow connections fast.

slider-mobile-new-in.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).

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

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

1 image has no alt text, which hurts accessibility and image search.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 14 characters: “Nunalie-europa”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Nunalie-europa” and “Shipping to a different location?”). One clear main headline is easier for people and search engines.

The homepage links to 131 pages on nunalie.eu and 7 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://nunalie.eu/collections/denim, https://nunalie.eu/collections/leggings, https://nunalie.eu/collections/pince and https://nunalie.eu/collections/shorts have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'createShopifyExtend')”.

Social proof on the homepage: 1 testimonial or review block. 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.

The homepage carries about 272 words of visible text.

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

Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).

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