20.7 sec in total
2.9 sec
17.4 sec
357 ms
Visit idai.or.id now to see the best up-to-date IDAI content for Indonesia and also check out these interesting facts you probably never knew about idai.or.id
IDAI
Visit idai.or.idWe analyzed Idai.or.id page load time and found that the first response time was 2.9 sec and then it took 17.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
idai.or.id performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value20.5 s
0/100
25%
Value22.4 s
0/100
10%
Value6,080 ms
0/100
30%
Value0.032
100/100
15%
Value28.3 s
0/100
10%
2922 ms
3562 ms
20 ms
36 ms
34 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 60% of them (64 requests) were addressed to the original Idai.or.id, 15% (16 requests) were made to Maps.googleapis.com and 9% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Idai.or.id.
Page size can be reduced by 3.3 MB (53%)
6.2 MB
2.9 MB
In fact, the total size of Idai.or.id main page is 6.2 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. Javascripts take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 136.8 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 43.6 kB, which is 28% 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 136.8 kB or 88% of the original size.
Potential reduce by 9.9 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. IDAI images are well optimized though.
Potential reduce by 1.9 MB
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 1.9 MB or 69% of the original size.
Potential reduce by 1.2 MB
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. Idai.or.id needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 89% of the original size.
Number of requests can be reduced by 63 (64%)
99
36
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IDAI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
idai.or.id
2922 ms
www.idai.or.id
3562 ms
css
20 ms
css
36 ms
css
34 ms
css
34 ms
bootstrap.css
1238 ms
font-awesome.css
999 ms
fontello.css
3037 ms
magnific-popup.css
1606 ms
settings.css
1119 ms
animations.css
980 ms
owl.carousel.css
1225 ms
owl.transitions.css
1250 ms
hover-min.css
1678 ms
style.css
1966 ms
idai_green.css
3243 ms
idai.css
1506 ms
jquery.min.js
3006 ms
bootstrap.min.js
2360 ms
modernizr.js
1500 ms
jquery.themepunch.tools.min.js
2751 ms
jquery.themepunch.revolution.min.js
4527 ms
isotope.pkgd.min.js
2384 ms
jquery.magnific-popup.min.js
2766 ms
jquery.waypoints.min.js
2796 ms
jquery.countTo.js
2636 ms
jquery.parallax-1.1.3.js
2754 ms
jquery.validate.js
3393 ms
js
62 ms
google.map.config.js
2993 ms
jquery.vide.js
2998 ms
owl.carousel.js
3745 ms
jquery.browser.js
3041 ms
SmoothScroll.js
3545 ms
template.js
3490 ms
jquery.matchHeight-min.js
3288 ms
idai.js
3782 ms
api.js
93 ms
fullcalendar.css
3895 ms
moment.min.js
3743 ms
fullcalendar.min.js
4521 ms
gcal.js
4001 ms
animate.css
3765 ms
home.js
3812 ms
sdk.js
60 ms
logo-IDAI.png
260 ms
Web%20IDAI%20Perbaharui%20Data%20copy.4be22f53ac3956dd2f6baf2f6676ae31.jpg
2950 ms
Seminar%20piprim_trial.4be22f53ac3956dd2f6baf2f6676ae31.jpg
6111 ms
fea-img-04.691cf8deeb98d0205ac4db93c1cfc081.jpg
1831 ms
fea-img-03.691cf8deeb98d0205ac4db93c1cfc081.jpg
767 ms
fea-img-02.691cf8deeb98d0205ac4db93c1cfc081.jpg
740 ms
fea-img-01.691cf8deeb98d0205ac4db93c1cfc081.jpg
2438 ms
fea-img-05.691cf8deeb98d0205ac4db93c1cfc081.jpg
997 ms
Skrining%20pada%20bayi.e32eaeb15d39bb6dd8819e6c5905552f.jpg
2275 ms
Penanganan%20Kesulitan%20Makan.e32eaeb15d39bb6dd8819e6c5905552f.jpg
1248 ms
bayi%20kuning.e32eaeb15d39bb6dd8819e6c5905552f.jpg
1503 ms
angrybirds.174b69864ad10bc865a661a290408c78.jpg
1761 ms
autis.e32eaeb15d39bb6dd8819e6c5905552f.jpg
2010 ms
category-konika.3e727b4e9ef703f254fed0343e55f955.jpg
2091 ms
category-pit.3e727b4e9ef703f254fed0343e55f955.jpg
2255 ms
category-sinas.3e727b4e9ef703f254fed0343e55f955.jpg
2343 ms
category-pkb.3e727b4e9ef703f254fed0343e55f955.jpg
2498 ms
category-others.3e727b4e9ef703f254fed0343e55f955.jpg
2519 ms
fontawesome-webfont.woff
3588 ms
glyphicons-halflings-regular.woff
3190 ms
fontello.woff
3664 ms
20 ms
analytics.js
171 ms
recaptcha__en.js
182 ms
events
286 ms
0sTQzbapM8j.js
62 ms
0sTQzbapM8j.js
97 ms
coloredbg.png
2067 ms
shadow1.png
2432 ms
revicons.woff
2488 ms
linkid.js
5 ms
collect
15 ms
collect
54 ms
common.js
3 ms
util.js
16 ms
stats.js
15 ms
AuthenticationService.Authenticate
27 ms
fullcalendar.print.css
245 ms
map.js
6 ms
marker.js
5 ms
StaticMapService.GetMapImage
243 ms
onion.js
20 ms
openhand_8_8.cur
148 ms
controls.js
20 ms
ViewportInfoService.GetViewportInfo
119 ms
transparent.png
108 ms
css
113 ms
spotlight-poi.png
57 ms
google4.png
46 ms
mapcnt6.png
47 ms
sv9.png
47 ms
tmapctrl.png
47 ms
cb_scout5.png
48 ms
tmapctrl4.png
47 ms
imgs8.png
53 ms
vt
81 ms
vt
90 ms
vt
96 ms
vt
82 ms
vt
115 ms
idai.or.id 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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
idai.or.id 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
idai.or.id 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
ID
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idai.or.id can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed English language. Our system also found out that Idai.or.id 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.
idai.or.id
Open Graph description is not detected on the main page of IDAI. 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: