11.7 sec in total
975 ms
10.4 sec
305 ms
Visit mobelife.be now to see the best up-to-date Mobelife content and also check out these interesting facts you probably never knew about mobelife.be
Artikelen over leuke ervaringen en verhalen
Visit mobelife.beWe analyzed Mobelife.be page load time and found that the first response time was 975 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
mobelife.be performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value7.1 s
5/100
25%
Value33.5 s
0/100
10%
Value0 ms
100/100
30%
Value0.002
100/100
15%
Value6.3 s
61/100
10%
975 ms
958 ms
427 ms
431 ms
432 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 98% of them (46 requests) were addressed to the original Mobelife.be, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Mobelife.be.
Page size can be reduced by 65.8 kB (13%)
515.9 kB
450.0 kB
In fact, the total size of Mobelife.be main page is 515.9 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. 30% of websites need less resources to load. Images take 347.9 kB which makes up the majority of the site volume.
Potential reduce by 49.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.4 kB or 81% of the original size.
Potential reduce by 13.3 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. Mobelife images are well optimized though.
Potential reduce by 70 B
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.
Potential reduce by 3.0 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. Mobelife.be has all CSS files already compressed.
Number of requests can be reduced by 15 (63%)
24
9
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobelife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
mobelife.be
975 ms
www.mobelife.be
958 ms
style.min.css
427 ms
styles.css
431 ms
front.min.css
432 ms
style.css
572 ms
themegrill-icons.min.css
430 ms
all.min.css
972 ms
swiper.min.css
576 ms
front.min.js
569 ms
js
44 ms
index.js
744 ms
index.js
577 ms
skip-link-focus-fix.min.js
713 ms
hammer.min.js
716 ms
swiper.min.js
1028 ms
Headroom.min.js
727 ms
imagesloaded.min.js
856 ms
masonry.min.js
867 ms
cenote-custom.min.js
872 ms
ge87f46b2f500ea780dbcf336e6659300293f25557711b31fd2e88d7ffa4549e5279197fa921abdc5a39bd7d8c3928d8a2ad2347ae18bb349c82e9fa03fee2dbb_1280-600x399.jpg
287 ms
gdeb83ed819891abbf96b4aa2271a4108ef8265167b3c8b00b443142ffd1b6415483ceec2e8d8a2b581c27ef1e8146720c9c195ef96846fcbde0a41d2aa5ee514_1280-600x398.jpg
437 ms
gdaec1d32320e11627aa2e740efce11aa674c341698a7dd1be2b440cdbae14c2a0571c6c43f6454bfd9a267017907dc42dad8f55761ca1e9d28dd6b12dfd86143_1280-600x399.jpg
431 ms
gd3506760481f4274ceb3e61b9e256f7f7a5e4c750722dd833faff7f4e4ca518b24d1f914657340eb8aaa772ef8bf0223c00a352285c5bc6bf03ed5256baae953_1280-600x400.jpg
560 ms
g888756983ec751267194b937de418e398bd67c08642031336c920384277d6e5ddbd2d7257e31d0bafd5ebbe867b424197c72caac85238e89598682836981c557_1280-600x424.png
1267 ms
g885ae588c1781d6a235399fac79712e7583bab82e718cfff52257187d76d920a7e0554685ddf49401ae29e6973743d09a2cbc5130a0077e248214d710803276a_1280-600x399.jpg
1138 ms
g35bcf6122c3b4528bdd1ea7943a223ade24d552f84fefec3d7d2d4ea5d41e8705dc19573de58422d7b3287ac762cc493ee06b0b73ab863b528be23d234c9be6f_1280-600x398.jpg
720 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
685 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
551 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
668 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
695 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
812 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
825 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
970 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
979 ms
KFOlCnqEu92Fr1MmWUlfChc-AMP6lbBP.woff
955 ms
KFOlCnqEu92Fr1MmWUlfCxc-AMP6lbBP.woff
969 ms
KFOlCnqEu92Fr1MmWUlfBxc-AMP6lbBP.woff
1273 ms
KFOlCnqEu92Fr1MmWUlfCBc-AMP6lbBP.woff
1119 ms
KFOlCnqEu92Fr1MmWUlfABc-AMP6lbBP.woff
1114 ms
KFOlCnqEu92Fr1MmWUlfCRc-AMP6lbBP.woff
1739 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5a7dvXmnPy1diQ.woff
1386 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5aDdvXmnPy1diRg0.woff
1258 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5bjdvXmnPy1diRg0.woff
1263 ms
fa-solid-900.woff
4242 ms
fa-regular-400.woff
1545 ms
themegrill-icons.woff
1406 ms
mobelife.be accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
mobelife.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
mobelife.be SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobelife.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Mobelife.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.
mobelife.be
Open Graph data is detected on the main page of Mobelife. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: