3.5 sec in total
207 ms
3 sec
353 ms
Welcome to ihssn.org homepage info - get ready to check Ihssn best content right away, or after learning these important things about ihssn.org
Visit ihssn.orgWe analyzed Ihssn.org page load time and found that the first response time was 207 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ihssn.org performance score
207 ms
52 ms
67 ms
70 ms
99 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 71% of them (54 requests) were addressed to the original Ihssn.org, 13% (10 requests) were made to Static.xx.fbcdn.net and 9% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (643 ms) relates to the external source Facebook.com.
Page size can be reduced by 812.3 kB (23%)
3.5 MB
2.7 MB
In fact, the total size of Ihssn.org main page is 3.5 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. 60% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 41.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. This page needs HTML code to be minified as it can gain 6.0 kB, which is 12% 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 41.4 kB or 81% of the original size.
Potential reduce by 402.6 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. Obviously, Ihssn needs image optimization as it can save up to 402.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 330.1 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 330.1 kB or 80% of the original size.
Potential reduce by 38.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. Ihssn.org needs all CSS files to be minified and compressed as it can save up to 38.3 kB or 84% of the original size.
Number of requests can be reduced by 31 (41%)
75
44
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ihssn. 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 from 4 to 1 for CSS and as a result speed up the page load time.
ihssn.org
207 ms
stylesheet.css
52 ms
layerslider.css
67 ms
prettyPhoto.css
70 ms
jquery.min.js
99 ms
jquery-easing-1.3.js
72 ms
menu.js
72 ms
custom.js
72 ms
jquery.quicksand.js
113 ms
jquery.prettyPhoto.js
113 ms
style2.css
121 ms
po_holder1.js
130 ms
po_holder2.js
140 ms
layerslider.kreaturamedia.jquery-min.js
127 ms
bg.png
113 ms
Headr-border.png
110 ms
header-shadow.png
158 ms
Logo2.png
255 ms
logo.png
111 ms
menu-left.png
109 ms
menu-bg.png
110 ms
divater.png
112 ms
banner-bg.png
112 ms
banner1.jpg
281 ms
banner2.jpg
359 ms
banner3.jpg
390 ms
banner4.jpg
426 ms
welcome-bg.png
191 ms
event-part-bg.png
225 ms
erro2.png
257 ms
005.jpg
295 ms
006.jpg
295 ms
011.jpg
307 ms
013.jpg
320 ms
014.jpg
323 ms
019.jpg
352 ms
022.jpg
355 ms
024.jpg
377 ms
027.jpg
385 ms
050.jpg
387 ms
047.jpg
395 ms
038.jpg
401 ms
029.jpg
419 ms
021.jpg
421 ms
031.jpg
424 ms
039.jpg
426 ms
sdk.js
80 ms
b03.png
323 ms
a03.png
349 ms
footer-bg.png
381 ms
footer-bottom.png
352 ms
footer-round-corner.png
347 ms
arrow.png
355 ms
68 ms
xd_arbiter.php
81 ms
xd_arbiter.php
143 ms
flex-prev.png
34 ms
flex-next.png
35 ms
page.php
643 ms
OuamSSjcmsY.css
288 ms
1kPfZUdGrka.js
424 ms
HQ1UKbUXIBt.js
623 ms
Qd7TTBR3F_S.js
557 ms
12208576_191290667872890_4369565180149985000_n.jpg
358 ms
1908261_238392696496020_2965949730904173104_n.jpg
497 ms
12809633_197929797241212_6698846242952475496_n.jpg
560 ms
10346317_547549615404070_1755336659105548603_n.jpg
562 ms
12791000_876295859158035_7862539910954746037_n.jpg
560 ms
12189866_950568611697969_407382128486396669_n.jpg
634 ms
12802809_950737104981286_3220142474894312176_n.jpg
631 ms
wL6VQj7Ab77.png
77 ms
s7jcwEQH7Sx.png
78 ms
R9GKCzjAnbk.js
70 ms
AWWjhOengNF.js
68 ms
YnSasnyq68i.js
71 ms
kQf_jlUv-kX.js
136 ms
ihssn.org SEO score
PS
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ihssn.org can be misinterpreted by Google and other search engines. Our service has detected that Pashto/Pushto is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ihssn.org 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.
ihssn.org
Open Graph description is not detected on the main page of Ihssn. 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: