Tools & Wizards About Us
komfort.no screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

komfort.no

Stressless© Scandinavian recliner chairs and sofas | Ekornes

Page Load Speed

11.7 sec in total

First Response

328 ms

Resources Loaded

3.7 sec

Page Rendered

7.7 sec

komfort.no screenshot

About Website

Click here to check amazing Komfort content. Otherwise, check out these important facts you probably never knew about komfort.no

Crafting furniture is wound deeply in our Nordic roots and tells the story of who we are. It is a craftsmanship perfected by our families over time. - Our promise is to make the world’s most comfortab...

Visit komfort.no

Key Findings

We analyzed Komfort.no page load time and found that the first response time was 328 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

komfort.no performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value42.2 s

0/100

25%

SI (Speed Index)

Value29.0 s

0/100

10%

TBT (Total Blocking Time)

Value9,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value45.2 s

0/100

10%

Network Requests Diagram

komfort.no

328 ms

en

1159 ms

gtm.js

93 ms

gtm.js

277 ms

css

588 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Komfort.no, 34% (25 requests) were made to Stressless.com and 8% (6 requests) were made to Px.owneriq.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Stressless.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 486.2 kB (7%)

Content Size

6.8 MB

After Optimization

6.3 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Komfort.no main page is 6.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 60.8 kB

  • Original 80.0 kB
  • After minification 66.0 kB
  • After compression 19.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 14.1 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 60.8 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 424.9 kB

  • Original 6.6 MB
  • After minification 6.2 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Komfort images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 495 B

  • Original 94.5 kB
  • After minification 94.5 kB
  • After compression 94.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 36 (57%)

Requests Now

63

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Komfort. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

komfort.no

komfort.no

328 ms

en

en

1159 ms

gtm.js

gtm.js

93 ms

gtm.js

gtm.js

277 ms

css

css

588 ms

VisitorIdentification.js

VisitorIdentification.js

432 ms

js

js

902 ms

validate

validate

543 ms

unobtrusive

unobtrusive

531 ms

4

4

298 ms

hotjar-2788627.js

hotjar-2788627.js

330 ms

js

js

170 ms

conversion_async.js

conversion_async.js

286 ms

analytics.js

analytics.js

300 ms

css

css

199 ms

css2

css2

203 ms

css2

css2

231 ms

modules.2be88a2123e5e486752f.js

modules.2be88a2123e5e486752f.js

84 ms

246 ms

collect

collect

21 ms

collect

collect

144 ms

stresslesslogo_transparent.png

stresslesslogo_transparent.png

196 ms

aura720x640.jpg

aura720x640.jpg

191 ms

stella720x640.jpg

stella720x640.jpg

706 ms

tokyo720x640.jpg

tokyo720x640.jpg

828 ms

mint720x640.jpg

mint720x640.jpg

778 ms

wave3spalomalightgrey1100x478.png

wave3spalomalightgrey1100x478.png

405 ms

mayfairpalomaoxfordblueoak575x465.png

mayfairpalomaoxfordblueoak575x465.png

360 ms

wingpalomablackteaksign575x465.png

wingpalomablackteaksign575x465.png

472 ms

p4-leftside-sidebyside-721x808.jpg

p4-leftside-sidebyside-721x808.jpg

558 ms

royal-paloma-black-original-1440x820jpg.jpg

royal-paloma-black-original-1440x820jpg.jpg

679 ms

sustainability940x820.jpg

sustainability940x820.jpg

628 ms

bua940x820.jpg

bua940x820.jpg

636 ms

mint_480x639.jpg

mint_480x639.jpg

631 ms

leather480x640.jpg

leather480x640.jpg

894 ms

function480x640.jpg

function480x640.jpg

744 ms

london360x639.jpg

london360x639.jpg

770 ms

stella360x639.jpg

stella360x639.jpg

775 ms

windsor360x639.jpg

windsor360x639.jpg

797 ms

wing360x639.jpg

wing360x639.jpg

949 ms

fbds.js

fbds.js

266 ms

g8xny4.js

g8xny4.js

348 ms

fbevents.js

fbevents.js

317 ms

tv2track.js

tv2track.js

369 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

346 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

365 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

447 ms

288 ms

FWWebsitePlugins-1.0.551.js

FWWebsitePlugins-1.0.551.js

140 ms

OtAutoBlock.js

OtAutoBlock.js

432 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

190 ms

1837842719782462

1837842719782462

26 ms

5

5

258 ms

eps

eps

210 ms

tv2track.php

tv2track.php

175 ms

tv2track.php

tv2track.php

132 ms

visit-data

visit-data

796 ms

g.pixel

g.pixel

157 ms

379208.gif

379208.gif

233 ms

1

1

181 ms

generic

generic

174 ms

pixel

pixel

179 ms

Pug

Pug

138 ms

font-awesome.min.css

font-awesome.min.css

197 ms

rum

rum

138 ms

generic

generic

140 ms

cm

cm

141 ms

sd

sd

153 ms

apndmp

apndmp

154 ms

ttd

ttd

36 ms

setuid

setuid

11 ms

epx.gif

epx.gif

30 ms

cpa.png

cpa.png

278 ms

Accessibility Review

komfort.no accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

komfort.no best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

komfort.no SEO score

80

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Komfort.no can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Komfort.no main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

komfort.no

Open Graph data is detected on the main page of Komfort. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: