34.9 sec in total
2.8 sec
31.9 sec
233 ms
Welcome to naas.go.kr homepage info - get ready to check Naas Go best content for South Korea right away, or after learning these important things about naas.go.kr
농촌진흥청 국립농업과학원. 우리나라 농업과학기반기술의 개발과 실용화, 산업화를 촉진하는 중추적인 연구기관
Visit naas.go.krWe analyzed Naas.go.kr page load time and found that the first response time was 2.8 sec and then it took 32.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
naas.go.kr performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value13.9 s
0/100
25%
Value16.0 s
0/100
10%
Value650 ms
46/100
30%
Value0.189
65/100
15%
Value16.3 s
5/100
10%
2758 ms
3975 ms
2917 ms
1450 ms
839 ms
Our browser made a total of 198 requests to load all elements on the main page. We found that 97% of them (193 requests) were addressed to the original Naas.go.kr, 2% (3 requests) were made to 0 and 1% (2 requests) were made to Nongsaro.go.kr. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Naas.go.kr.
Page size can be reduced by 125.0 kB (81%)
155.3 kB
30.3 kB
In fact, the total size of Naas.go.kr main page is 155.3 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. 40% of websites need less resources to load. HTML takes 139.5 kB which makes up the majority of the site volume.
Potential reduce by 113.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 113.9 kB or 82% of the original size.
Potential reduce by 11.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 11.2 kB or 71% of the original size.
Number of requests can be reduced by 13 (7%)
194
181
The browser has sent 194 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Naas 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 14 to 1 for JavaScripts and as a result speed up the page load time.
naas.go.kr
2758 ms
jquery-1.9.1.min.js
3975 ms
jquery-ui-1.10.2.custom.min.js
2917 ms
jquery.form.js
1450 ms
jquery.cookie.js
839 ms
jquery.colorbox-min.js
1124 ms
jquery.printThis.js
1402 ms
json2.js
1727 ms
jquery.poshytip.js
2282 ms
jquery.validate.js
2180 ms
function.js
1609 ms
naas.css
3426 ms
base.css
1884 ms
pop140527.js
1939 ms
jquery.cookie.js
806 ms
www.naas.go.kr.js
499 ms
topbg.gif
298 ms
logo.gif
555 ms
search_bar1.gif
307 ms
btn_search.gif
282 ms
logo1.gif
288 ms
icon_glb.gif
287 ms
menu1.gif
566 ms
menu_line.gif
568 ms
menu2.gif
564 ms
menu3.gif
577 ms
menu4.gif
576 ms
menu5.gif
851 ms
allmenu.gif
854 ms
btn_mclose1.gif
862 ms
allbanbg.gif
830 ms
ban_tab1.gif
866 ms
ban_tab2.gif
837 ms
ban_tab6.gif
1132 ms
ban_tab3.gif
1104 ms
ban_tab4.gif
1132 ms
ban_tab5.gif
1166 ms
ban_tab7.gif
1154 ms
banner_naas1.gif
1208 ms
banner_naas2.gif
1360 ms
banner_naas4.gif
1413 ms
banner_naas3.gif
1423 ms
banner_fact.gif
1418 ms
ban2015_20.gif
1684 ms
ban2015_21.gif
1531 ms
ban2015_22.gif
1680 ms
ban2015_23.gif
2007 ms
ban2015_28.gif
1729 ms
ban2015_31.gif
1690 ms
banner_22.gif
1834 ms
banner_23.gif
2041 ms
banner_25.gif
2035 ms
wtid.js
527 ms
banner_35.gif
1798 ms
banner_37.gif
1804 ms
banner_29.gif
1917 ms
banner_36.gif
2041 ms
banner_33.gif
2148 ms
banner_nfis.gif
1900 ms
banner_ati.gif
1915 ms
banner_at.gif
1914 ms
banner_lhca.gif
2029 ms
banner_nfrdi.gif
2118 ms
banner_krei.gif
2152 ms
testjsonp.ps
271 ms
dcs.gif
517 ms
ajaxCall.do
2775 ms
banner_agiedu.gif
1917 ms
banner_cric.gif
1940 ms
ban2015_1.gif
2109 ms
ban2015_2.gif
2161 ms
ban2015_3.gif
2139 ms
ban2015_24.gif
1973 ms
ban2015_27.gif
1949 ms
ban2015_4.gif
2139 ms
ban2015_5.gif
2164 ms
ban2015_6.gif
2158 ms
ban2015_12.gif
2157 ms
ban2015_17.gif
2035 ms
ban2015_18.gif
2196 ms
ban2015_19.gif
2248 ms
banner_39.gif
2200 ms
banner_40.gif
2168 ms
banner_41.gif
2040 ms
banner_43.gif
2271 ms
banner_44.gif
2243 ms
banner_45.gif
2219 ms
banner_47.gif
2129 ms
banner_48.gif
2028 ms
banner_49.gif
2008 ms
banner_50.gif
2228 ms
banner_51.gif
2225 ms
banner_52.gif
2451 ms
banner_53.gif
2091 ms
banner_54.gif
2042 ms
banner_56.gif
1964 ms
banner_irri.gif
2377 ms
banner_cimmyt.gif
2132 ms
banner_avrdc.gif
2156 ms
banner_cipotato.gif
2075 ms
banner_icarda.gif
2071 ms
banner_iwmi.gif
2094 ms
ban2015_7.gif
2156 ms
ban2015_8.gif
2151 ms
ban2015_9.gif
2003 ms
ban2015_10.gif
2049 ms
ban2015_11.gif
2101 ms
ban2015_13.gif
2038 ms
ban2015_14.gif
2116 ms
ban2015_15.gif
1976 ms
ban2015_16.gif
2245 ms
ban2015_25.gif
2296 ms
ban2015_26.gif
2977 ms
ban2015_29.gif
2960 ms
ban2015_30.gif
2113 ms
btn_mclose.gif
2138 ms
tit_allban.gif
2229 ms
NAAS020160304012939922.jpg
2964 ms
NAAS02015122301512765.jpg
2533 ms
NAAS020151008094118296.jpg
3004 ms
NAAS020150812094803332.png
2178 ms
NAAS020140729101102740.gif
2511 ms
NAAS020131107000076.gif
2588 ms
NAAS020131107000074.gif
2656 ms
NAAS020131107000073.gif
2816 ms
NAAS020131107000072.gif
2722 ms
NAAS020131107000071.gif
2595 ms
NAAS020131107000070.jpg
4417 ms
NAAS020131107000064.gif
2661 ms
NAAS020131107000063.gif
2712 ms
NAAS020131107000045.gif
2668 ms
NAAS020131107000030.gif
2623 ms
NAAS020131107000025.gif
2552 ms
pquick_cen.gif
2633 ms
pquick_top.gif
2697 ms
NAAS12016012802283300.gif
2624 ms
NAAS120160121032705867.gif
2617 ms
NAAS120160121032724206.gif
2618 ms
NAAS120160121034754166.gif
2622 ms
NAAS120160121034811963.gif
2701 ms
NAAS120160121034827868.gif
2694 ms
NAAS120160121034849250.gif
2667 ms
pquick_bot.gif
2640 ms
tit03_box.gif
2772 ms
tit05.gif
2759 ms
tit06.gif
2720 ms
tit_more2.gif
2472 ms
icon_left.png
2450 ms
icon_right.png
2452 ms
NAAS520160408024745178.jpg
6742 ms
NAAS520160407011822370.jpg
4053 ms
NAAS520160406024649463.jpg
6695 ms
NAAS520160404053106438.jpg
3268 ms
NAAS52016040110324401.jpg
12212 ms
NAAS52016033102553431.jpg
9264 ms
NAAS020160314114757120.JPG
12823 ms
NAAS020160314112035406.JPG
11751 ms
NAAS020160307094300113.JPG
19754 ms
NAAS020160224054702213.JPG
19746 ms
NAAS020160224044710981.JPG
19652 ms
bot_b.png
11798 ms
tit02_box.gif
11966 ms
tit02.gif
11967 ms
tit03.gif
12165 ms
tit04.gif
12049 ms
tit_more1.gif
12321 ms
tit01_box.gif
12248 ms
tit01.gif
12452 ms
btn_left.gif
12405 ms
btn_right.gif
12303 ms
bot_bl.png
12540 ms
bot_br.png
12518 ms
NAAS20160205111257927.jpg
13902 ms
NAAS20160301061505521.jpg
18984 ms
center_iconbg.gif
12737 ms
NAAS120160119082417527.png
13016 ms
NAAS120160119082610592.png
13232 ms
NAAS120160119082657285.png
13501 ms
NAAS120160119082759875.png
13645 ms
NAAS120160119082819620.png
14208 ms
NAAS120160119082842368.png
13838 ms
tit07_box.gif
14080 ms
tit07.gif
14378 ms
icon_news2.gif
14309 ms
icon_new.gif
14062 ms
tit08_box.gif
13727 ms
tit08.gif
13103 ms
tit09_box.gif
11092 ms
tit09.gif
10728 ms
btn_datago.gif
8197 ms
ban_bg.gif
5561 ms
btn_go.gif
5543 ms
ban_line.gif
5568 ms
icon_letter.gif
5551 ms
bot_call.gif
5588 ms
ban_tab1_o.gif
5585 ms
tit05_o.gif
5665 ms
tit02_o.gif
5694 ms
naas.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
naas.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
naas.go.kr 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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naas.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 Naas.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.
naas.go.kr
Open Graph description is not detected on the main page of Naas 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: