8.5 sec in total
1.2 sec
6.4 sec
941 ms
Click here to check amazing IIDSS content. Otherwise, check out these important facts you probably never knew about iidss.org
Indonesia International Defense Sciense Seminar
Visit iidss.orgWe analyzed Iidss.org page load time and found that the first response time was 1.2 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
iidss.org performance score
1196 ms
390 ms
467 ms
47 ms
469 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 54% of them (64 requests) were addressed to the original Iidss.org, 13% (15 requests) were made to Pbs.twimg.com and 11% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Iidss.org.
Page size can be reduced by 1.5 MB (23%)
6.3 MB
4.9 MB
In fact, the total size of Iidss.org main page is 6.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 92.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. 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 92.4 kB or 85% of the original size.
Potential reduce by 457.3 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. IIDSS images are well optimized though.
Potential reduce by 583.3 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 583.3 kB or 59% of the original size.
Potential reduce by 358.0 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. Iidss.org needs all CSS files to be minified and compressed as it can save up to 358.0 kB or 87% of the original size.
Number of requests can be reduced by 75 (66%)
113
38
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IIDSS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.iidss.org
1196 ms
wp-emoji-release.min.js
390 ms
layerslider.css
467 ms
css
47 ms
styles.css
469 ms
frontend.css
486 ms
base.css
479 ms
layout.css
478 ms
widgets.css
611 ms
style.css
936 ms
responsive.css
702 ms
admin-ajax.php
757 ms
style.css
709 ms
greensock.js
980 ms
jquery.js
1082 ms
jquery-migrate.min.js
979 ms
layerslider.kreaturamedia.jquery.js
1186 ms
layerslider.transitions.js
991 ms
mediaelement-and-player.min.js
1175 ms
mediaelement-migrate.min.js
1172 ms
ext.js
1230 ms
jquery.bxslider.min.js
1230 ms
jquery.isotope.min.js
1316 ms
jquery.prettyPhoto.js
1407 ms
jquery.transit.min.js
1407 ms
jquery.selene.js
1420 ms
jquery.quartz.js
1465 ms
custom.js
1479 ms
js
102 ms
widgets.js
87 ms
default.css
1409 ms
comment-reply.min.js
1501 ms
scripts.js
1501 ms
core.min.js
1521 ms
widget.min.js
1561 ms
tabs.min.js
1585 ms
accordion.min.js
1641 ms
jquery.color.min.js
1732 ms
wp-mediaelement.min.js
1733 ms
wp-embed.min.js
1753 ms
easy-table.css
1231 ms
_ioa_front.css
1040 ms
www.iidss.org
474 ms
clogo.jpg
260 ms
facebook.png
246 ms
facebook.png
246 ms
twitter.png
246 ms
twitter.png
244 ms
instagram.png
497 ms
instagram.png
494 ms
IIDSS-2020-Logo.png
494 ms
sh_left_wing.png
493 ms
embed
302 ms
analytics.js
116 ms
_ioa_front.woff
955 ms
IIDSS-2020-Banner.jpg
2039 ms
Download-Material.png
669 ms
IIDSS-Paraller-Session-Rundown.png
1367 ms
iidss.jpg
2307 ms
0.gif
669 ms
8.gif
890 ms
6.gif
891 ms
2.gif
1145 ms
1.gif
1147 ms
mvcvisit.png
1195 ms
mvcyesterday.png
1365 ms
mvcmonth.png
1372 ms
mvcyear.png
1449 ms
mvctotal.png
1592 ms
widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html
22 ms
settings
157 ms
collect
25 ms
moment~timeline~tweet.ae149926685a43cb146e35371430188e.js
4 ms
timeline.687eed636a16648c9f0b1f72d7fa68bd.js
16 ms
js
54 ms
profile
170 ms
init_embed.js
60 ms
common.js
44 ms
util.js
43 ms
map.js
39 ms
google4.png
61 ms
overlay.js
5 ms
StaticMapService.GetMapImage
237 ms
onion.js
32 ms
search_impl.js
32 ms
kh
82 ms
ViewportInfoService.GetViewportInfo
35 ms
timeline.32f7f89e2e680ebfe3f4cfefb27966ae.light.ltr.css
34 ms
vt
195 ms
vt
207 ms
vt
211 ms
vt
207 ms
timeline.32f7f89e2e680ebfe3f4cfefb27966ae.light.ltr.css
12 ms
vt
211 ms
ry3blIlY_normal.jpg
96 ms
D-9kCwrU8AEDodH
319 ms
D-7WgWgUEAAUjFv
291 ms
D-rQiYaU4AA-MVQ
293 ms
D-jRnxUVUAE0ksQ
292 ms
D-jQ2ewUYAAzFe9
294 ms
D-eFEgsUYAAJ_Gy
310 ms
D_B_UPJUEAAJbOV
440 ms
D_B_UyXU0AAGiSk
522 ms
D_B_VPTU0AEvdNF
481 ms
D_B_Vk_U8AAZamb
542 ms
D_An4OaUwAEEHlX
518 ms
D_An4vUUEAA8MsQ
519 ms
D_An5OWUIAE8YkG
654 ms
D_An5uIU4AArOgj
649 ms
AuthenticationService.Authenticate
18 ms
QuotaService.RecordEvent
25 ms
controls.js
4 ms
QuotaService.RecordEvent
38 ms
css
56 ms
jot
53 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
39 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
23 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
23 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
22 ms
iidss.org SEO score
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iidss.org 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 Iidss.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.
iidss.org
Open Graph description is not detected on the main page of IIDSS. 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: