2.7 sec in total
263 ms
2.1 sec
268 ms
Welcome to exellent.be homepage info - get ready to check Exellent best content for Belgium right away, or after learning these important things about exellent.be
De beste elektro van je vakman in tv, audio, IT, telefonie, foto, video, smart devices, huishouden, keuken, verzorging | Ontdek ons assortiment | Exellent
Visit exellent.beWe analyzed Exellent.be page load time and found that the first response time was 263 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
exellent.be performance score
263 ms
445 ms
252 ms
468 ms
50 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 26% of them (32 requests) were addressed to the original Exellent.be, 14% (17 requests) were made to Cdn.html5maker.com and 12% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (588 ms) relates to the external source Track.adform.net.
Page size can be reduced by 177.8 kB (30%)
593.9 kB
416.1 kB
In fact, the total size of Exellent.be main page is 593.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. 65% of websites need less resources to load. Images take 303.4 kB which makes up the majority of the site volume.
Potential reduce by 116.3 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 15.4 kB, which is 11% 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 116.3 kB or 84% of the original size.
Potential reduce by 28.0 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. Exellent images are well optimized though.
Potential reduce by 33.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 33.5 kB or 22% of the original size.
Number of requests can be reduced by 44 (39%)
112
68
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Exellent. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
exellent.be
263 ms
www.exellent.be
445 ms
252 ms
468 ms
dc.js
50 ms
piwik.js
499 ms
gtm.js
95 ms
all.js
10 ms
campagne-860056.jpg
550 ms
0854248e7c6ada4e396afb94ced1d483ad1dbdefa8c3.html
205 ms
ITHP15AK020NB_230x195.jpg
93 ms
hp_50x50.jpg
99 ms
GRES91_210x230.jpg
99 ms
graef_50x50.jpg
97 ms
onze-selectie.png
196 ms
BGMUM57830_230x159.jpg
196 ms
bosch.gif
196 ms
ITLOG430_230x230.jpg
195 ms
logitech_50x30.jpg
191 ms
ITHP15AN080NB_230x129.jpg
194 ms
ITHP17G179NB_230x145.jpg
284 ms
ITHAMARACTONBL_230x159.jpg
284 ms
LIDO2322.jpg
283 ms
domo.gif
283 ms
ITDE9393_230x213.jpg
283 ms
SWRZ28H6005WWEG_84x230.jpg
283 ms
samsung.gif
371 ms
becommerce-label.png
372 ms
ecommerce-europe-label.png
370 ms
campagne-395565_184x184.jpg
370 ms
campagne-110346_184x184.jpg
374 ms
campagne-128958_372x184.jpg
371 ms
campagne-127770_184x184.jpg
374 ms
294 ms
__utm.gif
17 ms
__utm.gif
16 ms
exellent.png
290 ms
xd_arbiter.php
22 ms
xd_arbiter.php
89 ms
ga-audiences
101 ms
shopping-cart-icon.png
246 ms
sprites_2014.png
248 ms
exellent.png
359 ms
payment-providers.png
359 ms
conversion_async.js
69 ms
roundtrip.js
62 ms
analytics.js
68 ms
588 ms
controls.png
314 ms
border.png
311 ms
loading_background.png
314 ms
loading.gif
315 ms
TweenMax.1.11.4.min.js
35 ms
spin.min.js
34 ms
a87ffb50edde634bc956d389c530284656cc5c2f45d2aeQQcZCKHN6uQUhckxxeU.png
12 ms
38215b57624bce2080535160d43ab8fd56cc5c3b324844yM9E33AvOUp4C16wV8Y.png
26 ms
5686d602a410db773678a8e82bb7b6b856cc5c4e00c44KJICvVl8iWtLuLDW646m.png
25 ms
80373ced3c590a4afa4c9b826e1734b956cc5c911f4a7jdsDd7QsuR6en8hK9yV1.png
27 ms
40094eb924a0d1e37ecc57231f591cf556cc5ca5aad5fOw79ArlYAVmm73RPk5Wd.png
57 ms
a75c80273fd40c25fbaa03513c4343c356cc5d1f7168bIMH6RqWZs9SlKEs2RNhn.png
28 ms
e1e5fa6c30165dd93dd4dcc75c83213f56cc5d236cac4BlHNL5jFcWvD6v2KUDDs.png
31 ms
0399723d9c009b1f3f84848b7a0ecd8956cc5d28e5665LB8zCtwwIkQX5l5b4Djo.png
28 ms
72240f435fdaa4fc7922a39d57eb9b4556cc5d2e416f0c5O2Tj47vxuUQzKU8FtQ.png
58 ms
f10d041de1ed9715eb5838788e72c14456cc5d30bfb18Sz0SbrGzSxU8dt9VDZhw.png
56 ms
35f993ad750ddb3a91a2f749eed5dad156cc5d327706831vES1ogEnAUNE7OPBiv.png
57 ms
99 ms
ec.js
38 ms
212363c64c2e310e5f7c30e81cf7e1df56cc5c1758cdb0oGYbZyuJX6jV3EElbCd.png
20 ms
6a27e65567d6d27a4de7da10564ed5f656cc5c15c689bVI6hVEVNR7FhUkhlT4G2.png
39 ms
7d1843c87118d32a9a46fff11d8f264b56cc5c2bbb5afXbOMrLdqvN0hHsC9QvCu.png
20 ms
collect
28 ms
collect
71 ms
H32CYIEKTJCBFMPCZVZKNT.js
203 ms
31 ms
like_box.php
231 ms
widget_v2.132.js
10 ms
__$$__stringtable_lang_nl.js
21 ms
xd_arbiter.php
40 ms
out
21 ms
28 ms
tr
64 ms
tr
320 ms
tr
77 ms
out
17 ms
out
16 ms
out
16 ms
out
16 ms
out
21 ms
out
20 ms
sync
12 ms
adsct
193 ms
u.php
213 ms
pixel
73 ms
45 ms
jTuqQ-OPDr6.css
38 ms
n370yiaI2G6.css
41 ms
_rx8naC75Dy.js
56 ms
x5F9OMjKyLw.js
73 ms
ICDbTSzjQEg.js
52 ms
TTCre3391I0.js
55 ms
26 ms
42 ms
377928.gif
10 ms
sd
10 ms
in
91 ms
11078067_847178058652418_6732472497382522546_n.jpg
106 ms
165190_171953202841577_1876850_n.jpg
60 ms
12734200_125792881141850_6809568675850097214_n.jpg
65 ms
1960098_10208554965370906_8326303659154222804_n.jpg
61 ms
11666029_104843803194226_4438392999318474027_n.jpg
65 ms
10374945_1553882231569324_3533483991777106948_n.jpg
63 ms
10941904_453594361462606_2798598206895790403_n.jpg
62 ms
12717846_1683884011890006_197068003734362803_n.jpg
173 ms
12662587_10205650999214413_5438956833597625053_n.jpg
66 ms
1013857_370927466378314_1339081641_n.jpg
89 ms
10415656_657481367672021_7457327174744625623_n.jpg
66 ms
10980741_1381598222153597_3756739420272718648_n.jpg
129 ms
1798447_10208320597962979_1114442497008965982_n.jpg
67 ms
12246877_893786317371861_3562511229514262290_n.jpg
68 ms
10583914_915182271885020_4502046323607921247_n.jpg
67 ms
wL6VQj7Ab77.png
49 ms
s7jcwEQH7Sx.png
49 ms
228 ms
I6-MnjEovm5.js
5 ms
vlXaquuXMrr.js
10 ms
exellent.be SEO score
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exellent.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 Exellent.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.
exellent.be
Open Graph data is detected on the main page of Exellent. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: