15.1 sec in total
879 ms
14.1 sec
167 ms
Visit andong.go.kr now to see the best up-to-date Andong Go content for South Korea and also check out these interesting facts you probably never knew about andong.go.kr
Visit andong.go.krWe analyzed Andong.go.kr page load time and found that the first response time was 879 ms and then it took 14.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
andong.go.kr performance score
name
value
score
weighting
Value11.5 s
0/100
10%
Value13.2 s
0/100
25%
Value18.5 s
0/100
10%
Value70 ms
99/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
879 ms
2342 ms
1548 ms
1092 ms
1392 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that all of those requests were addressed to Andong.go.kr and no external sources were called. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Andong.go.kr.
Page size can be reduced by 552.5 kB (21%)
2.6 MB
2.1 MB
In fact, the total size of Andong.go.kr main page is 2.6 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. 25% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 172.3 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 91.5 kB, which is 48% 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 172.3 kB or 90% of the original size.
Potential reduce by 12.4 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. Andong Go images are well optimized though.
Potential reduce by 275.8 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 275.8 kB or 73% of the original size.
Potential reduce by 92.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. Andong.go.kr needs all CSS files to be minified and compressed as it can save up to 92.0 kB or 87% of the original size.
Number of requests can be reduced by 38 (44%)
87
49
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Andong 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 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
andong.go.kr
879 ms
main.do
2342 ms
common.css
1548 ms
default.css
1092 ms
ko_main.css
1392 ms
ko_layout.css
1409 ms
common.js
591 ms
jquery-1.9.1.min.js
2239 ms
jquery-ui-1.10.0.custom.min.js
2930 ms
jquery.form.js
2200 ms
menu.js
1684 ms
common.js
1799 ms
mainLib.js
1959 ms
bg_main_top.gif
264 ms
btn_skip_contents.gif
273 ms
logo.gif
264 ms
andong_slogan.gif
254 ms
split_gnb.gif
281 ms
search_box.gif
282 ms
search_btn.gif
487 ms
Taegeukgi_logo.gif
505 ms
bg_menu01.png
791 ms
bul_lnb_st02.gif
540 ms
point_blank.gif
550 ms
bg_menu02.png
1640 ms
bg_menu03.png
1272 ms
bg_menu04.png
1546 ms
bg_menu05.png
1351 ms
bg_navi06.gif
822 ms
icon_area_01.gif
1055 ms
icon_area_02.gif
1096 ms
icon_area_03.gif
1318 ms
icon_area_04.gif
1371 ms
icon_area_05.gif
1534 ms
icon_area_06.gif
1581 ms
icon_area_07.gif
1621 ms
icon_area_08.gif
1646 ms
icon_area_09.gif
1799 ms
icon_area_10.gif
1796 ms
bg_navi07.gif
1841 ms
icon_tour01.gif
2199 ms
icon_tour02.gif
2189 ms
icon_tour03.gif
2746 ms
btn_visual_next.gif
2045 ms
btn_visual_pause.gif
2060 ms
btn_visual_prev.gif
2103 ms
visual_main09.jpg
3815 ms
visual_main01.jpg
3641 ms
visual_main02_02.jpg
3940 ms
weather.json
2247 ms
visual_main04.jpg
3858 ms
visual_main03.jpg
3856 ms
photo_mayor.jpg
2760 ms
tle_mayor.gif
3028 ms
go_mayor01.gif
3306 ms
go_mayor02.gif
3377 ms
tle_popup.gif
3407 ms
btn_popup_prev.gif
3535 ms
btn_popup_pause.gif
3585 ms
btn_popup_next.gif
3384 ms
thumbImgViewer.jsp
3395 ms
thumbImgViewer.jsp
3271 ms
thumbImgViewer.jsp
3286 ms
thumbImgViewer.jsp
3125 ms
thumbImgViewer.jsp
3094 ms
thumbImgViewer.jsp
3090 ms
thumbImgViewer.jsp
3112 ms
thumbImgViewer.jsp
3049 ms
thumbImgViewer.jsp
3113 ms
thumbImgViewer.jsp
3091 ms
thumbImgViewer.jsp
3068 ms
thumbImgViewer.jsp
3070 ms
thumbImgViewer.jsp
3104 ms
thumbImgViewer.jsp
3044 ms
thumbImgViewer.jsp
3129 ms
ico_dot.gif
3102 ms
ico_more.gif
2917 ms
ico_new.gif
2907 ms
tle_news.gif
2907 ms
thumbImgViewerNewsLetter.jsp
2903 ms
thumbImgViewerNewsLetter.jsp
3003 ms
tle_good.gif
2748 ms
ico_minwon.gif
2490 ms
ico_cityhall.gif
2205 ms
ico_tel.gif
1971 ms
ico_location.gif
1764 ms
ico_organization.gif
1831 ms
link_sns_01.gif
1675 ms
link_sns_02.gif
1636 ms
link_sns_03.gif
1605 ms
link_sns_04.gif
1596 ms
tle_go_link.gif
1527 ms
btn_con_prev.gif
1640 ms
btn_con_next.gif
1653 ms
bg_useful01.gif
1624 ms
tle_useful01.gif
1619 ms
tle_useful02.gif
1589 ms
tle_useful03.gif
1526 ms
tle_banner_zone.gif
1635 ms
thumbImgViewer.jsp
1627 ms
thumbImgViewer.jsp
1631 ms
thumbImgViewer.jsp
1625 ms
thumbImgViewer.jsp
1586 ms
thumbImgViewer.jsp
1521 ms
thumbImgViewer.jsp
1633 ms
thumbImgViewer.jsp
1615 ms
thumbImgViewer.jsp
1628 ms
thumbImgViewer.jsp
1634 ms
thumbImgViewer.jsp
1582 ms
thumbImgViewer.jsp
1516 ms
thumbImgViewer.jsp
1622 ms
thumbImgViewer.jsp
1615 ms
thumbImgViewer.jsp
1631 ms
thumbImgViewer.jsp
1628 ms
thumbImgViewer.jsp
1603 ms
thumbImgViewer.jsp
1517 ms
thumbImgViewer.jsp
1611 ms
thumbImgViewer.jsp
1614 ms
thumbImgViewer.jsp
1640 ms
thumbImgViewer.jsp
1623 ms
thumbImgViewer.jsp
1590 ms
thumbImgViewer.jsp
1546 ms
thumbImgViewer.jsp
1605 ms
thumbImgViewer.jsp
1612 ms
thumbImgViewer.jsp
1631 ms
thumbImgViewer.jsp
1605 ms
thumbImgViewer.jsp
1606 ms
thumbImgViewer.jsp
1570 ms
thumbImgViewer.jsp
1599 ms
thumbImgViewer.jsp
1620 ms
thumbImgViewer.jsp
1605 ms
thumbImgViewer.jsp
1601 ms
thumbImgViewer.jsp
1617 ms
thumbImgViewer.jsp
1593 ms
thumbImgViewer.jsp
1593 ms
thumbImgViewer.jsp
1603 ms
thumbImgViewer.jsp
1608 ms
thumbImgViewer.jsp
1590 ms
thumbImgViewer.jsp
1628 ms
thumbImgViewer.jsp
1616 ms
thumbImgViewer.jsp
1589 ms
thumbImgViewer.jsp
1589 ms
thumbImgViewer.jsp
1607 ms
thumbImgViewer.jsp
1589 ms
thumbImgViewer.jsp
1632 ms
thumbImgViewer.jsp
1640 ms
thumbImgViewer.jsp
1588 ms
thumbImgViewer.jsp
1570 ms
thumbImgViewer.jsp
1590 ms
thumbImgViewer.jsp
1600 ms
thumbImgViewer.jsp
1637 ms
thumbImgViewer.jsp
1657 ms
thumbImgViewer.jsp
1569 ms
thumbImgViewer.jsp
1575 ms
thumbImgViewer.jsp
1587 ms
thumbImgViewer.jsp
1603 ms
thumbImgViewer.jsp
1654 ms
thumbImgViewer.jsp
1658 ms
thumbImgViewer.jsp
1559 ms
20160215banner.jpg
1562 ms
select_open.png
1594 ms
select_close.png
1614 ms
bg_split.gif
1653 ms
mark_wa.gif
1658 ms
weather_01.png
1546 ms
andong.go.kr accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
andong.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
andong.go.kr SEO score
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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Andong.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 Andong.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.
andong.go.kr
Open Graph description is not detected on the main page of Andong 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: