napapijri.com website review

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

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

About 713 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Optimizely and Optanon and others), adding 1.7 MB and 985 ms of main-thread time.

10 images could be 491 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.

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

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

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

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

sierra.chat costs a phone 60 ms of main-thread work and 711 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 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

5 KiB could be saved by minifying JavaScript.

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 see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MADE FOR EVERY JOURNEY: JACKETS”.

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

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

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

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

The first text or image appears after 2.4 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.

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

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

Your homepage downloads 4.6 MB in 315 requests on a phone: scripts 1.9 MB (126), images 1.5 MB (28) and other files 824 KiB (110). Under 2 MB keeps phones on slow connections fast.

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

4 images have 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.

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

There are 4 <h1> headlines (“MADE FOR EVERY JOURNEY: JACKETS”, “WARM LAYERS: SWEATS & KNITS” and “COLD DAYS APPROACHING”). One clear main headline is easier for people and search engines.

Structured data found (Brand, OnlineStore, WebPage and WebSite) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected end of JSON input)”.

11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 432 pages on napapijri.com and 7 external pages.

Your homepage links to https://www.napapijri.com/en-gb/pages/size-chart, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.napapijri.com/en-gb/pages/select-your-location, https://www.napapijri.com/en-gb/pages/wishlist and https://www.napapijri.com/en-gb/pages/faq have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.napapijri.com/en-gb/products/bering-duffle-bag-48-lt-np0a4ggmn7c and https://www.napapijri.com/en-gb/products/bering-duffle-bag-48-lt-np0a4ggmg4c use the same meta description. A description written for each page earns more clicks.

Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.napapijri.com/en-gb/products/skidoo-cotton-anorak-jacket-np0a8b2twt3, whose canonical is https://www.napapijri.com/en-gb/products/skidoo-cotton-anorak-jacket-np0a8b2tn7c. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.napapijri.com/en-gb/pages/wishlist, https://www.napapijri.com/en-gb/products/skidoo-cotton-anorak-jacket-np0a8b2twt3, https://www.napapijri.com/en-gb/products/archive-full-zip-fleece-np0a8apen5e, https://www.napapijri.com/en-gb/products/rainforest-next-summer-anorak-jacket-unisex-np0a4fi3g4c, https://www.napapijri.com/en-gb/products/rainforest-next-winter-anorak-jacket-np0a4ib9g1f and https://www.napapijri.com/en-gb/products/yupik-full-zip-fleece-hoodie-np0a8azxm5e and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “google_tag_manager.rm.208000814(...)(...) is not a function”.

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

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

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

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

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

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