3.4 sec in total
484 ms
2.8 sec
158 ms
Welcome to michellanduyt.be homepage info - get ready to check Michellanduyt best content right away, or after learning these important things about michellanduyt.be
Log into Facebook to start sharing and connecting with your friends, family, and people you know.
Visit michellanduyt.beWe analyzed Michellanduyt.be page load time and found that the first response time was 484 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
michellanduyt.be performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value4.4 s
39/100
25%
Value4.2 s
77/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value4.2 s
85/100
10%
484 ms
349 ms
488 ms
559 ms
551 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Michellanduyt.be, 17% (12 requests) were made to Scontent.xx.fbcdn.net and 4% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (954 ms) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 75.2 kB (56%)
133.3 kB
58.2 kB
In fact, the total size of Michellanduyt.be main page is 133.3 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. 55% of websites need less resources to load. HTML takes 95.7 kB which makes up the majority of the site volume.
Potential reduce by 71.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 71.9 kB or 75% of the original size.
Potential reduce by 3.2 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. Michellanduyt images are well optimized though.
Number of requests can be reduced by 52 (75%)
69
17
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Michellanduyt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
michel.landuyt
484 ms
jri1RqGgcfE.css
349 ms
DY6CRC1i1Bl.css
488 ms
kyEKgjk51ZE.css
559 ms
b_nc0vjtAUF.css
551 ms
xgj7bXhJNEH.css
554 ms
sFTVm4Wm5AN.css
552 ms
avmpRmLcppA.css
569 ms
ZeuPykSxSED.css
558 ms
VFoZ1f4h99C.css
620 ms
RlvWmF7gpVx.css
622 ms
tSgg1_QsZ29.css
617 ms
5ngtluj4kLT.css
615 ms
q68gy-v_YMF.js
688 ms
event
140 ms
12400586_10206925771516029_4221384054855334038_n.jpg
604 ms
info_24.png
83 ms
safe_image.php
338 ms
10376044_10206789025577466_948014163405391398_n.jpg
662 ms
392333_10149999285997743_1364412321_n.png
707 ms
1653797_904521649561139_4918163416290658025_n.jpg
931 ms
1461271_1429029073994469_104495367_n.jpg
823 ms
34631_1477158136574_3793735_n.jpg
774 ms
10922462_787050391365387_6847810921612510846_n.jpg
833 ms
11046477_1563582583893512_2328605223657737111_n.jpg
849 ms
12191716_1633375220213646_3219679918590831794_n.jpg
814 ms
602559_498593590155875_630086601_n.jpg
914 ms
10358709_61015777137555_3661128205461310753_n.jpg
954 ms
11539746_61002232643527_3212770541119206137_n.jpg
887 ms
ZVyMWStefv_.png
75 ms
K00K-UgnsKu.png
72 ms
UgNUNkKQar6.png
70 ms
LOOn0JtHNzb.gif
71 ms
FJmpeSpHpjS.js
216 ms
1bNoFZUdlYZ.js
84 ms
_UYztdBNTjs.js
92 ms
1FCa-btixu2.js
152 ms
7BE0CZr3HTs.js
158 ms
RTHSWgdzleR.js
91 ms
Oagsvfb4VWi.js
262 ms
eR-qA8bp1RM.js
163 ms
N6x5BPT1p97.js
162 ms
LTv6ZK-5zxz.js
436 ms
R_PGrgD5ZlT.js
262 ms
IjqSyiwKeaX.js
263 ms
VfAud2trIQQ.js
295 ms
-7JBD_ybv4q.js
418 ms
J0ZuTxeV0vD.js
287 ms
Xa8aKOYq3zI.js
290 ms
yBzWdmXwoNV.js
301 ms
RJ-tBRDclXF.js
356 ms
Kt4tkgSRvHH.js
356 ms
67L4LyUDskl.js
434 ms
kAwRfubFq5y.js
521 ms
BF5roBtMMc1.js
432 ms
c05laeT1OPx.js
433 ms
-sVccfRXDIY.js
521 ms
spacer.gif
29 ms
GsNJNwuI-UM.gif
75 ms
jKEcVPZFk-2.gif
75 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
134 ms
WnfSPoLOzuN.js
77 ms
aNu_nLTOokj.js
74 ms
ZhzvbB4aaO_.js
72 ms
Dppan5o6UJu.js
71 ms
8v2_hdH4Nfm.js
137 ms
-Tr757ZEtMP.js
336 ms
A0qdgknEnD5.js
138 ms
-PAXP-deijE.gif
69 ms
michellanduyt.be accessibility score
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
[aria-*] attributes do not match their roles
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.
michellanduyt.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
michellanduyt.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Michellanduyt.be 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 Michellanduyt.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.
michellanduyt.be
Open Graph description is not detected on the main page of Michellanduyt. 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: