14.1 sec in total
1.5 sec
12.4 sec
164 ms
Visit niied.go.kr now to see the best up-to-date Niied Go content for Indonesia and also check out these interesting facts you probably never knew about niied.go.kr
Visit niied.go.krWe analyzed Niied.go.kr page load time and found that the first response time was 1.5 sec and then it took 12.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
niied.go.kr performance score
name
value
score
weighting
Value8.3 s
1/100
10%
Value18.1 s
0/100
25%
Value24.2 s
0/100
10%
Value30 ms
100/100
30%
Value0.695
8/100
15%
Value8.7 s
37/100
10%
1496 ms
471 ms
474 ms
480 ms
477 ms
Our browser made a total of 186 requests to load all elements on the main page. We found that 98% of them (182 requests) were addressed to the original Niied.go.kr, 1% (2 requests) were made to Code.jquery.com and 1% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Niied.go.kr.
Page size can be reduced by 196.8 kB (41%)
483.2 kB
286.4 kB
In fact, the total size of Niied.go.kr main page is 483.2 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. 35% of websites need less resources to load. Images take 242.3 kB which makes up the majority of the site volume.
Potential reduce by 53.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 53.9 kB or 82% of the original size.
Potential reduce by 2.7 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. Niied Go images are well optimized though.
Potential reduce by 92.2 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 92.2 kB or 79% of the original size.
Potential reduce by 48.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. Niied.go.kr needs all CSS files to be minified and compressed as it can save up to 48.0 kB or 81% of the original size.
Number of requests can be reduced by 22 (14%)
160
138
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Niied Go. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
index.do
1496 ms
basic.css
471 ms
layout_summer.css
474 ms
header_summer.css
480 ms
footer.css
477 ms
search.css
512 ms
jquery-ui-1.8.20.custom.css
1131 ms
jquery.min.js
6 ms
jquery-ui.min.js
8 ms
util.js
696 ms
jquery.ui.datepicker-ko.js
701 ms
jquery.form.js
1173 ms
common.js
710 ms
tab.js
758 ms
tab2.js
924 ms
menu_model1.js
934 ms
menu_model2.js
945 ms
wcslog.js
13 ms
index_summer.css
1012 ms
jquery.hrzAccordion.examples.css
1170 ms
template.js
1171 ms
js_rolling.js
1183 ms
jquery.rotate.js
1271 ms
jquery.hrzAccordion.js
1359 ms
ettn.js
1380 ms
m
648 ms
util_bg.gif
229 ms
util_bar.gif
228 ms
util01.gif
231 ms
util02.gif
230 ms
util03.gif
230 ms
util07.gif
252 ms
logo.gif
454 ms
icon_search.gif
451 ms
icon_mail.gif
454 ms
icon_facebook.gif
456 ms
icon_scrap.gif
455 ms
icon_twitter.gif
498 ms
menu01.gif
678 ms
menu02.gif
675 ms
menu03.gif
680 ms
menu04.gif
681 ms
menu05.gif
683 ms
allmenu01.gif
744 ms
allmenu02.gif
900 ms
allmenu03.gif
902 ms
allmenu04.gif
906 ms
allmenu05.gif
908 ms
allmenu06.gif
907 ms
main_visual_tit01.gif
989 ms
main_visual_txt01.gif
1127 ms
main_visual_img01.gif
1129 ms
main_visual_tit02.gif
1132 ms
main_visual_txt02.gif
1134 ms
main_visual_img02.gif
1135 ms
main_visual_img03.gif
1235 ms
main_visual_tit03.gif
1352 ms
main_visual_txt03.gif
1353 ms
main_visual_img04.gif
1358 ms
main_visual_tit04.gif
1359 ms
main_visual_txt04.gif
1359 ms
main_visual_img05.gif
1473 ms
epik.jsp
1445 ms
talk.jsp
1618 ms
topik.jsp
1562 ms
neat.jsp
1368 ms
jb.jsp
4380 ms
main_visual_tit05.gif
1487 ms
main_visual_txt05.gif
1377 ms
main_visual_img06.gif
1445 ms
main_visual_tit06.gif
1532 ms
main_visual_txt06.gif
1565 ms
main_visual_img07.gif
1598 ms
main_visual_img08.gif
1570 ms
biz_menu01.gif
1449 ms
biz_menu02.gif
1554 ms
biz_menu03.gif
1570 ms
biz_menu04.gif
1600 ms
biz_menu05.gif
1606 ms
biz_menu06.gif
1608 ms
schedule_tit.gif
1575 ms
btn_more01.gif
1576 ms
schedule_arrow_up.gif
1603 ms
schedule_arrow_down.gif
1609 ms
biz_faq_tit.gif
1670 ms
faq_tit01.gif
1732 ms
faq_tit02.gif
1580 ms
faq_tit03.gif
1613 ms
faq_tit04.gif
1611 ms
faq_tit05.gif
1670 ms
faq_tit06.gif
1803 ms
inde_banner01.gif
1731 ms
inde_banner02.gif
1616 ms
inde_banner03.gif
1613 ms
notice_tab01.gif
1671 ms
btn_more02.gif
1808 ms
notice_tab02.gif
1851 ms
epic_tab03.gif
1713 ms
epic_tab01.gif
1604 ms
epic_tab02.gif
1591 ms
shortcut_tit.gif
1667 ms
shortcut01.gif
1632 ms
shortcut02.gif
1607 ms
shortcut03.gif
1620 ms
shortcut04.gif
1595 ms
organ_tit01.gif
1651 ms
organ_tit02.gif
1635 ms
organ_tit03.gif
1611 ms
organ_tit04.gif
1649 ms
organ_tit05.gif
1597 ms
ceo_tit.gif
1631 ms
ceo_txt.gif
1633 ms
btn_go01.gif
1613 ms
news_tit.gif
1672 ms
popnum1.gif
1596 ms
1455863737341_324_zone
1617 ms
popnum2.gif
1632 ms
1455585000977_140_zone
1624 ms
btn_pop_pri.gif
1656 ms
btn_pop_pause.gif
1630 ms
btn_pop_next.gif
1615 ms
movie_tit.gif
1614 ms
btn_more03.gif
1624 ms
1455169969273_401_THUMB
1660 ms
gallery_tit.gif
1651 ms
1456201588302_894_THUMB
1612 ms
1456199152354_415_THUMB
1591 ms
main_banner_left_btn.gif
1628 ms
main_banner_stop_btn.gif
1664 ms
main_banner_right_btn.gif
1671 ms
1444096000712_948
1612 ms
1442189037940_913
1588 ms
1389248084795_229
1627 ms
1373520333275_999
1616 ms
1347382223534_618
1599 ms
1347356781188_622
1552 ms
1347356719502_205
1592 ms
1347356869599_276
1582 ms
1347356654647_677
1591 ms
1347356850621_804
1570 ms
1392605088568_290
1458 ms
1439170234562_711
1549 ms
1347356688171_416
1572 ms
1347356616176_890
1533 ms
1381449128336_850
1566 ms
1367469080210_423
1429 ms
1365467737307_46
1436 ms
1386211486565_479
1555 ms
black_logo01.gif
1514 ms
black_logo02.gif
1518 ms
fmenu01.gif
1422 ms
fmenu02.gif
1412 ms
fmenu06.gif
1413 ms
fmenu04.gif
1524 ms
fmenu05.gif
1480 ms
address.gif
1391 ms
btn_go02.gif
1406 ms
1347610700222_828
1379 ms
qr_tit.gif
1367 ms
qr_txt.gif
1458 ms
icon_facebook_ov.gif
1388 ms
gnb_bg.gif
1387 ms
menu06.gif
1372 ms
allmenu_bg.png
1378 ms
bg05.gif
1367 ms
bg10.gif
1435 ms
main_visual.jpg
4474 ms
bg01.gif
1391 ms
btn_biz_open.gif
1378 ms
biz_bg.gif
1388 ms
bg05.gif
1369 ms
schedule_tit_bg.gif
1419 ms
schedule_content_bg.gif
1399 ms
biz_faq_bg.gif
1424 ms
bg02.gif
1396 ms
inde_banner_icon01.gif
1396 ms
inde_banner_icon02.gif
1509 ms
inde_banner_icon03.gif
1438 ms
tab_line.gif
1440 ms
notice_tab01_ov.gif
1437 ms
epic_tab03_ov.gif
1402 ms
organ_img01.gif
1543 ms
ceo_bg.gif
1551 ms
bg06.gif
1451 ms
popnum2_on.gif
1452 ms
popnum1_on.gif
1434 ms
niied.go.kr 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
[role]s are not contained by their required parent element
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
niied.go.kr 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
niied.go.kr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Niied.go.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Niied.go.kr 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.
niied.go.kr
Open Graph description is not detected on the main page of Niied Go. 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: