salongmobler.no website review

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

6 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

About 645 KiB of JavaScript is downloaded but never used on this page.

Clarity costs a phone 288 ms of main-thread work and 33 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 137 ms of main-thread work and 771 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 9 ms of main-thread work and 1.5 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.

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

azurefd.net costs a phone 51 ms of main-thread work and 331 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.

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

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

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

25 KiB could be saved by minifying JavaScript.

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.

2 KiB could be saved by minifying CSS.

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

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

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

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

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 5.2 MB in 481 requests on a phone: images 1.9 MB (35), scripts 1.7 MB (175) and other files 1.1 MB (235). Under 2 MB keeps phones on slow connections fast.

00c9f6bc-4150-40c6-b382-44688e3bc540.png weighs 1.4 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example 00c9f6bc-4150-40c6-b382-44688e3bc540.png at 1,414 px wide, shown at 185 px. Resized copies would save about 1.2 MB.

1 image (1.4 MB) is 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.

Design_uten_navn_3_9689bb2a-bd84-4998-b412-37311061e227.png 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).

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 5 elements on the page fail this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

8 visible links have no text or label, so screen readers cannot say where they go.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 13 characters: “Salong Møbler”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 50 characters: “Kvalitetsmøbler for salonger – Salong Møbler Norge”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 197 pages on salongmobler.no and 0 external pages.

https://salongmobler.no/pages/prosjekter, https://salongmobler.no/collections/frisorstol-klassisk, https://salongmobler.no/collections/frisorstol-modern, https://salongmobler.no/collections/klippestasjoner-enkelt, https://salongmobler.no/collections/klippestasjoner-veggmodell and https://salongmobler.no/collections/klippestasjoner-oymodell and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://salongmobler.no/pages/prosjekter, https://salongmobler.no/collections/frisor-vaskestasjoner and https://salongmobler.no/collections/speil-frisor-collection have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://buy-me-cdn.makeprosimp.com/v2/css/app.min.css?v=1ff700a7' from origin 'https://sal…”.

Social proof on the homepage: 35 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 692 words of visible text.

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