6.6 sec in total
623 ms
5.2 sec
829 ms
Visit exendo.be now to see the best up-to-date Exendo content and also check out these interesting facts you probably never knew about exendo.be
Visit exendo.beWe analyzed Exendo.be page load time and found that the first response time was 623 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
exendo.be performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value10.6 s
0/100
25%
Value14.1 s
1/100
10%
Value690 ms
43/100
30%
Value0.005
100/100
15%
Value10.7 s
22/100
10%
623 ms
432 ms
278 ms
190 ms
1575 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 36% of them (32 requests) were addressed to the original Exendo.be, 8% (7 requests) were made to Px.owneriq.net and 8% (7 requests) were made to Dsum-sec.casalemedia.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Exendo.be.
Page size can be reduced by 1.5 MB (26%)
5.8 MB
4.3 MB
In fact, the total size of Exendo.be main page is 5.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. 55% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 857.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. 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 857.9 kB or 93% of the original size.
Potential reduce by 24.1 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. Exendo images are well optimized though.
Potential reduce by 600.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 600.0 kB or 72% of the original size.
Potential reduce by 52.3 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. Exendo.be needs all CSS files to be minified and compressed as it can save up to 52.3 kB or 84% of the original size.
Number of requests can be reduced by 45 (59%)
76
31
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Exendo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
exendo.be
623 ms
gzip.php
432 ms
gzip.php
278 ms
gzip.php
190 ms
explanatory-dictionary-style.php
1575 ms
M9QvL9BNzkhPy88rKc6sSkXjAgA.js
184 ms
M9FPzs_NTc0r0S1KLcip1MvNzNMx1M_JTM8oScqv0C3IKS3WzwKiwtLUokq95Pyc_CKguJ6hnqmeJQA.js
88 ms
shareaholic.js
17 ms
1a8bc4975c40b1bbf115fb8a08876391.json
145 ms
ga.js
33 ms
12.gif
300 ms
bg_3.png
213 ms
exendo-epigenomics-header-final-logo-3500x253.jpg
510 ms
search.png
212 ms
printer_famfamfam.gif
209 ms
Logo-Praktijk-Klein-e1439653410732.png
215 ms
Logo-Analytics-Klein-e1439653794875.png
216 ms
Logo_Exendo-Epigenomics-e1439568558693.jpg
1779 ms
Logo-BrainQ-Klein-e1439568251960.jpg
1871 ms
gelukkig-zijn-150x150.jpg
299 ms
Oorzaken-van-uitputting-van-het-beloningssysteem-en-het-stresssysteem-150x150.png
443 ms
verslaving--150x150.jpg
441 ms
oxytocine-150x150.jpg
443 ms
Hooggevoeligheid--150x150.jpg
442 ms
HSP-150x150.jpg
510 ms
ADHD--150x150.gif
510 ms
Exendo-Epigenomics-verkleind-logo.jpg
619 ms
exendo-analytics-logo-web.png
616 ms
mbog-erkend-door-medium.jpg
617 ms
main_bg_6_1016px.png
600 ms
main_inner_bg.png
642 ms
shrMain.min.js
53 ms
__utm.gif
132 ms
decrease_activated.gif
534 ms
decrease_deactivated.gif
534 ms
increase_activated.gif
550 ms
increase_deactivated.gif
612 ms
exendo-footer-2-3500px.jpg
796 ms
jquery.min.js
78 ms
analytics.js
17 ms
pageview.gif
56 ms
vglnk.js
21 ms
partners.js
604 ms
pixel.gif
16 ms
pixel.gif
17 ms
ping
16 ms
domains
53 ms
sholic.js
64 ms
usermatch
181 ms
beacon.js
12 ms
cms-sh2c.html
61 ms
ping_match.gif
6 ms
eexelate.js
33 ms
169 ms
2964
30 ms
ep
1480 ms
pixel
14 ms
45 ms
match-result
38 ms
rs
4 ms
net.php
9 ms
pixel
14 ms
generic
8 ms
usermatch
112 ms
generic
4 ms
xrefid.xgi
5 ms
pixel.gif
27 ms
pixel.gif
17 ms
ep
44 ms
xrefid.xgi
10 ms
pixel
15 ms
GenericUserSync.ashx
70 ms
i.gif
137 ms
pixelssl.htm
200 ms
cs
74 ms
pixel
49 ms
cm
1583 ms
crum
155 ms
crum
182 ms
rum
208 ms
crum
209 ms
cfcm.ashx
7 ms
crum
156 ms
rum
172 ms
ddcssl.htm
132 ms
crum
51 ms
ermcm
73 ms
pxj
25 ms
exendo.be accessibility score
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
Links do not have a discernible name
exendo.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
exendo.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exendo.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Exendo.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.
exendo.be
Open Graph description is not detected on the main page of Exendo. 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: