6.1 sec in total
669 ms
4.4 sec
973 ms
Welcome to hortusfestival.nl homepage info - get ready to check Hortusfestival best content for Netherlands right away, or after learning these important things about hortusfestival.nl
Visit hortusfestival.nlWe analyzed Hortusfestival.nl page load time and found that the first response time was 669 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hortusfestival.nl performance score
669 ms
465 ms
430 ms
421 ms
605 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 39% of them (30 requests) were addressed to the original Hortusfestival.nl, 29% (22 requests) were made to Static.xx.fbcdn.net and 13% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 653.0 kB (40%)
1.7 MB
999.6 kB
In fact, the total size of Hortusfestival.nl main page is 1.7 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 774.6 kB which makes up the majority of the site volume.
Potential reduce by 35.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 35.9 kB or 75% of the original size.
Potential reduce by 14.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. Hortusfestival images are well optimized though.
Potential reduce by 367.4 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 367.4 kB or 68% of the original size.
Potential reduce by 235.5 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. Hortusfestival.nl needs all CSS files to be minified and compressed as it can save up to 235.5 kB or 82% of the original size.
Number of requests can be reduced by 31 (42%)
74
43
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hortusfestival. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
hortusfestival.nl
669 ms
WebResource.axd
465 ms
styles.css
430 ms
jquery.fancybox-1.3.4.css
421 ms
jquery.min.js
605 ms
jquery.fancybox-1.3.4.js
519 ms
script.js
402 ms
cart.aspx
1162 ms
WebResource.axd
478 ms
system.js
503 ms
ScriptResource.axd
521 ms
ScriptResource.axd
469 ms
fix_webkit.js
484 ms
BetterImageProcessor.ashx
156 ms
BetterImageProcessor.ashx
169 ms
BetterImageProcessor.ashx
98 ms
BetterImageProcessor.ashx
273 ms
BetterImageProcessor.ashx
161 ms
BetterImageProcessor.ashx
336 ms
BetterImageProcessor.ashx
357 ms
BetterImageProcessor.ashx
234 ms
BetterImageProcessor.ashx
391 ms
BetterImageProcessor.ashx
251 ms
header-2015.jpg
93 ms
pvoHrDog56c
88 ms
notplaying.png
106 ms
color-blank.gif
140 ms
color-leiden.gif
139 ms
color-amsterdam.gif
138 ms
color-utrecht.gif
139 ms
color-haren.gif
159 ms
ga.js
12 ms
likebox.php
558 ms
soundmanager2-jsmin.js
214 ms
__utm.gif
18 ms
www-embed-player-vflfNyN_r.css
22 ms
www-embed-player.js
42 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
43 ms
ad_status.js
36 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
33 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
33 ms
410ucuAGgaJ.css
283 ms
tSbl8xBI27R.css
351 ms
Czh0gDTFcBt.css
421 ms
Ek6lpayKeeB.css
568 ms
EoarYgA68t4.css
550 ms
q68gy-v_YMF.js
566 ms
FJmpeSpHpjS.js
616 ms
0wM5s1Khldu.js
482 ms
1bNoFZUdlYZ.js
485 ms
njO1TPvGzoR.js
588 ms
1QuX41zDRrx.js
588 ms
Oagsvfb4VWi.js
679 ms
LTv6ZK-5zxz.js
814 ms
1FCa-btixu2.js
683 ms
10384292_10153428685650256_2188236395808100097_n.jpg
365 ms
safe_image.php
467 ms
safe_image.php
584 ms
safe_image.php
1248 ms
11140274_10153311319030256_6530261587875314542_n.jpg
418 ms
526625_536113313087951_1296980231_n.jpg
484 ms
1508059_10153385937212627_2906922744404352783_n.jpg
549 ms
12418106_10205800669681040_659145874917417187_n.jpg
725 ms
11247970_837695146326588_6195412366070683797_n.jpg
589 ms
11140274_10153311319030256_6530261587875314542_n.jpg
569 ms
11889475_938938109505305_4180912396152087047_n.jpg
624 ms
11060266_938938119505304_7801592953327597776_n.jpg
551 ms
11224768_938938199505296_549892345645620883_n.jpg
672 ms
wL6VQj7Ab77.png
87 ms
s7jcwEQH7Sx.png
85 ms
sSwLTfB7PfP.png
87 ms
QDwYpIaRyfG.png
86 ms
bNvHN6v1NeH.png
88 ms
b53Ajb4ihCP.gif
87 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
134 ms
__utm.gif
7 ms
hortusfestival.nl SEO score
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hortusfestival.nl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Hortusfestival.nl main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
hortusfestival.nl
Open Graph description is not detected on the main page of Hortusfestival. 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: