pelsbarn.no website review

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

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

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

8 third-party services load with your homepage (Clarity, Klaviyo and Shopify and others), adding 1.4 MB and 613 ms of main-thread time.

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

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

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

cloudfront.net costs a phone 112 ms of main-thread work and 387 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 images could be 180 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.

About 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.

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

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 425 requests on a phone: other files 1.5 MB (265), scripts 1.2 MB (103) and images 477 KiB (15). Under 2 MB keeps phones on slow connections fast.

Early_Black_Friday_Sale_-_Homepage_-_Mobile_adf6dda3-8f88-48 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 further down the page (132 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 0.99 g of CO₂e: 119.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Structured data found (Organization and WebSite) but with 4 problems, for example “Organization: sameAs is not an absolute URL ("twitter.com")”.

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

Your <h1> is empty.

The homepage links to 35 pages on pelsbarn.no and 4 external pages.

Your homepage links to https://pelsbarn.no/twitter.com, https://pelsbarn.no/facebook.com, https://pelsbarn.no/pinterest.com and https://pelsbarn.no/instagram.com, which answer with an error. Visitors hit a dead end and search engines drop them.

https://pelsbarn.no/collections/pelsbarn-26 and https://pelsbarn.no/collections/black-friday-2 all use the title “Pelsbarn '26 – Pelsbarn ♡”. Search engines can't tell which page to show for a search, so each competes with the others.

https://pelsbarn.no/collections/all, https://pelsbarn.no/policies/shipping-policy, https://pelsbarn.no/collections/pelsbarn-26, https://pelsbarn.no/collections/luxe-collection, https://pelsbarn.no/collections/car-beds and https://pelsbarn.no/collections/orthopedic-beds and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://pelsbarn.no/collections/black-friday-2, whose canonical is https://pelsbarn.no/collections/pelsbarn-26. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pelsbarn.no/collections/all, https://pelsbarn.no/pages/om-pelsbarn, https://pelsbarn.no/collections/pelsbarn-26, https://pelsbarn.no/collections/luxe-collection, https://pelsbarn.no/collections/car-beds and https://pelsbarn.no/collections/orthopedic-beds and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://pelsbarn.no/a/Sporing has 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://pelsbarn.no/collections/black-friday-2 and https://pelsbarn.no/a/Sporing took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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