Tools & Wizards About Us
habitat.be screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

habitat.be

Meubles, canapés, décorations et luminaires design - Habitat

Page Load Speed

2.4 sec in total

First Response

310 ms

Resources Loaded

1.9 sec

Page Rendered

110 ms

habitat.be screenshot

About Website

Visit habitat.be now to see the best up-to-date Habitat content for Belgium and also check out these interesting facts you probably never knew about habitat.be

Fabricant de design depuis 1964, Habitat propose plus de 1000 références de meubles et de canapés pour un intérieur contemporain.

Visit habitat.be

Key Findings

We analyzed Habitat.be page load time and found that the first response time was 310 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

habitat.be performance score

0

Network Requests Diagram

habitat.be

310 ms

www.habitat.be

1135 ms

jquery-ui.css

7 ms

font-awesome.min.css

45 ms

a8ac970.css

89 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 32% of them (7 requests) were addressed to the original Habitat.be, 23% (5 requests) were made to Img-s.habitat.be and 9% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Habitat.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 295.9 kB (67%)

Content Size

445.0 kB

After Optimization

149.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Habitat.be main page is 445.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 263.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 64.2 kB

  • Original 76.0 kB
  • After minification 53.9 kB
  • After compression 11.9 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 22.1 kB, which is 29% 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 64.2 kB or 84% of the original size.

Image Optimization

-18%

Potential reduce by 1.0 kB

  • Original 5.5 kB
  • After minification 4.4 kB

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. Obviously, Habitat needs image optimization as it can save up to 1.0 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 155.9 kB

  • Original 263.4 kB
  • After minification 263.4 kB
  • After compression 107.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 155.9 kB or 59% of the original size.

CSS Optimization

-75%

Potential reduce by 74.9 kB

  • Original 100.0 kB
  • After minification 99.7 kB
  • After compression 25.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Habitat.be needs all CSS files to be minified and compressed as it can save up to 74.9 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (41%)

Requests Now

17

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

habitat.be

habitat.be

310 ms

www.habitat.be

www.habitat.be

1135 ms

jquery-ui.css

jquery-ui.css

7 ms

font-awesome.min.css

font-awesome.min.css

45 ms

a8ac970.css

a8ac970.css

89 ms

jquery.min.js

jquery.min.js

28 ms

bootstrap.min.js

bootstrap.min.js

46 ms

jquery-ui.js

jquery-ui.js

22 ms

f741465.js

f741465.js

258 ms

ga.js

ga.js

65 ms

up_page.jpg

up_page.jpg

275 ms

logo.png

logo.png

215 ms

btn_search.png

btn_search.png

215 ms

footer_submit.png

footer_submit.png

234 ms

logo.gif

logo.gif

241 ms

dinhabregular-webfont.woff

dinhabregular-webfont.woff

175 ms

dinhabmedium-webfont.woff

dinhabmedium-webfont.woff

166 ms

dinhabrounded-webfont.woff

dinhabrounded-webfont.woff

261 ms

__utm.gif

__utm.gif

11 ms

player_api

player_api

38 ms

www-widgetapi.js

www-widgetapi.js

28 ms

nr-885.min.js

nr-885.min.js

42 ms

SEO Factors

habitat.be SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Habitat.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Habitat.be 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

habitat.be

Open Graph description is not detected on the main page of Habitat. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: