nunoo.no website review

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

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

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

8 third-party services load with your homepage (ZenDesk, Klaviyo and Google Tag Manager and others), adding 1.3 MB and 779 ms of main-thread time.

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

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

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

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

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.

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

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

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

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.

4 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Saleup 50% off”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.5 MB in 309 requests on a phone: scripts 1.3 MB (88), images 1.1 MB (45) and other files 879 KiB (135). Under 2 MB keeps phones on slow connections fast.

Mille_Washed_Black-Maxi-75169801-6_37c16031-2aa7-4197-839e-e 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 0.98 g of CO₂e: 118.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

All page content should be contained by landmarks: 13 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.

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

There are 2 <h1> headlines (“” and “Where are you shipping to?”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

The homepage links to 237 pages on nunoo.no and 12 external pages.

https://nunoo.no/collections/all, https://nunoo.no/collections/new-arrivals, https://nunoo.no/collections/bags, https://nunoo.no/collections/accessories, https://nunoo.no/collections/sale and https://nunoo.no/collections/nunoo-exclusive and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://nunoo.no/cdn/shop/t/85/assets/section-featured-collection.css?v=5884' because its …”.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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 576 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 (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 10 cookies (measured from a US location before any click).

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