14.3 sec in total
3.5 sec
10.6 sec
157 ms
Visit jungnang.go.kr now to see the best up-to-date Jungnang Go content for South Korea and also check out these interesting facts you probably never knew about jungnang.go.kr
서울중랑구,역사, 동명유래, 구현황, 행정기구, 문화재와 명소, 주요기관, 관내도, 민원정보, 생활정보, 자치법규, 통계연보 소개
Visit jungnang.go.krWe analyzed Jungnang.go.kr page load time and found that the first response time was 3.5 sec and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
jungnang.go.kr performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value9.0 s
1/100
25%
Value17.1 s
0/100
10%
Value640 ms
47/100
30%
Value0.039
100/100
15%
Value8.5 s
37/100
10%
3511 ms
705 ms
875 ms
658 ms
1184 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 93% of them (141 requests) were addressed to the original Jungnang.go.kr, 7% (10 requests) were made to Jungnang.seoul.kr. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Jungnang.go.kr.
Page size can be reduced by 412.3 kB (20%)
2.1 MB
1.7 MB
In fact, the total size of Jungnang.go.kr main page is 2.1 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.6 MB which makes up the majority of the site volume.
Potential reduce by 174.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. This page needs HTML code to be minified as it can gain 75.4 kB, which is 38% 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 174.4 kB or 88% of the original size.
Potential reduce by 45.2 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. Jungnang Go images are well optimized though.
Potential reduce by 126.4 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 126.4 kB or 70% of the original size.
Potential reduce by 66.2 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. Jungnang.go.kr needs all CSS files to be minified and compressed as it can save up to 66.2 kB or 83% of the original size.
Number of requests can be reduced by 28 (19%)
150
122
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jungnang 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 5 to 1 for CSS and as a result speed up the page load time.
main.do
3511 ms
common.css
705 ms
gnb.css
875 ms
layout_.css
658 ms
main.css
1184 ms
jquery-1.8.3.min.js
1716 ms
jquery.carouFredSel-6.2.1-packed.js
1439 ms
main.js
886 ms
common.js
1107 ms
search.js
1113 ms
dqAutoCompleteCommon.js
1330 ms
layout.css
898 ms
slideCtrl01.js
406 ms
body_bgx01.gif
257 ms
gnb_bg.png
236 ms
seoulrose_ico.gif
216 ms
globalVline.gif
238 ms
bu_zoomin.gif
220 ms
bu_zoom.gif
233 ms
bu_zoomout.gif
428 ms
logo.gif
438 ms
bg_tsh.gif
463 ms
icon_search.gif
467 ms
ico_tshbg.gif
472 ms
ico_num_1.gif
513 ms
rank_default.gif
640 ms
ico_num_2.gif
655 ms
ico_num_3.gif
694 ms
ico_num_4.gif
700 ms
ico_num_5.gif
706 ms
ico_num_6.gif
770 ms
ico_num_7.gif
852 ms
ico_num_8.gif
873 ms
ico_num_9.gif
923 ms
ico_num_10.gif
932 ms
ico_taegki.gif
942 ms
gnb_01_off.png
1026 ms
gService_btn_1.gif
1074 ms
gService_btn_2.gif
1101 ms
gnb_02_off.png
1153 ms
btn_more.gif
1164 ms
gnb_03_off.png
1177 ms
g3_img1.gif
1292 ms
gnb_04_off.png
1285 ms
link_plus.gif
1318 ms
link_worknet.gif
1392 ms
gnb_05_off.png
1396 ms
gnb_06_off.png
1412 ms
gnb_07_off.png
1484 ms
bar.gif
640 ms
bg_service.gif
967 ms
tab_service_img1.jpg
779 ms
bu_blackball.gif
617 ms
bu_line.gif
616 ms
ico_blank_main.gif
693 ms
bg_sprite.jpg
1756 ms
bu_footerline.gif
842 ms
icon_rss.gif
844 ms
icon_com.gif
955 ms
g7-1-img_1.jpg
1602 ms
g7_Service_btn1.gif
1322 ms
allmenuOpen.png
1395 ms
B_201602250857487830.jpg
1650 ms
B_201603040444382560.jpg
1659 ms
B_201603090107274160.jpg
1890 ms
B_201603161055241190.jpg
1586 ms
B_201602260923510690.jpg
1688 ms
B_201603040358590410.jpg
1674 ms
B_201603110327302550.jpg
1881 ms
B_201603150242497070.jpg
1699 ms
B_201601130458394310.jpg
1778 ms
B_201601280318458960.jpg
1775 ms
B_201602051050117000.jpg
1779 ms
B_201602220120565440.jpg
1725 ms
B_201602050921309970.jpg
1990 ms
B_201603080935597710.jpg
2016 ms
B_201503190222179320.jpg
2061 ms
B_201602290243063500.jpg
1855 ms
mayor_tit.png
1768 ms
txt_mayor05.png
1777 ms
txt_mayor06.png
1932 ms
txt_mayor07.png
1983 ms
txt_mayor08.png
1940 ms
serviceLink1.gif
1864 ms
serviceLink2.gif
1839 ms
serviceLink3.gif
1919 ms
serviceLink_new1.gif
1914 ms
serviceLink_new2.gif
1984 ms
serviceLink_new3.gif
1881 ms
serviceLink_new4.gif
1866 ms
more.gif
1906 ms
01_BBS_201602031050418010.JPG
1976 ms
01_BBS_201603160513419990.JPG
1968 ms
jbn_tit.gif
1963 ms
jbn.jpg
1917 ms
btn-more.gif
1860 ms
list-ico-ing.gif
1857 ms
left_service_tit1_on.gif
1767 ms
left_service_tit2_off.gif
1722 ms
etcsite-btn-go2.gif
1702 ms
bannerzoneTit.gif
1618 ms
B_201507010205010590.png
1539 ms
B_201512020157511940.gif
1604 ms
B_201603140355443350.jpg
1660 ms
B_201511171047541210.jpg
1643 ms
B_201505140333477410.jpg
1548 ms
B_201509160941455800.jpg
1523 ms
B_201601250454588740.jpg
1494 ms
B_201507290945212390.jpg
1608 ms
B_201507290947338960.jpg
1586 ms
B_201409020510475980.jpg
1417 ms
B_201502230505385270.gif
1391 ms
B_201402251024564130.gif
1410 ms
B_201312190430254430.jpg
1449 ms
B_201512021018223650.jpg
1518 ms
B_201603110528455150.jpg
1462 ms
B_201505180952185070.gif
1422 ms
B_201502061013518890.jpg
1387 ms
B_201508270335316520.jpg
1406 ms
B_201507030501337730.png
1468 ms
B_201503190453564970.jpg
1486 ms
B_201508190916573310.jpg
1439 ms
B_201603070220384700.jpg
1479 ms
B_201403111056313160.jpg
1400 ms
B_201404170917294350.jpg
1420 ms
B_201603160357240740.jpg
1479 ms
B_201405150325177920.jpg
1450 ms
B_201406271118445250.jpg
1374 ms
B_201407080146392520.jpg
1456 ms
B_201407150152164480.jpg
1425 ms
B_201407170913191720.jpg
1424 ms
B_201407170914402770.jpg
1474 ms
B_201407210328065460.jpg
1406 ms
B_201408010142273740.jpg
1386 ms
B_201410130228132390.jpg
1441 ms
B_201410130331214810.jpg
1461 ms
B_201411141016550610.jpg
1494 ms
B_201603180239187400.jpg
1438 ms
logo_btm.gif
1398 ms
visual-ctrl-up1.gif
1382 ms
visual-ctrl-play1.gif
1456 ms
visual-ctrl-stop1.gif
1459 ms
visual-ctrl-down1.gif
1444 ms
mayor_bg01.jpg
1499 ms
servicebg2.gif
1357 ms
bull.gif
1378 ms
na_tit_off.png
1444 ms
bg_app.gif
1449 ms
mid_quick2.gif
1426 ms
bg_sprite.jpg
1750 ms
na_bg.png
1381 ms
jungnang.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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.
jungnang.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
jungnang.go.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Jungnang.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 Jungnang.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.
jungnang.go.kr
Open Graph description is not detected on the main page of Jungnang 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: