22.3 sec in total
7.3 sec
14.5 sec
495 ms
Click here to check amazing Brcn Go content for South Korea. Otherwise, check out these important facts you probably never knew about brcn.go.kr
Visit brcn.go.krWe analyzed Brcn.go.kr page load time and found that the first response time was 7.3 sec and then it took 15 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
brcn.go.kr performance score
name
value
score
weighting
Value11.4 s
0/100
10%
Value42.9 s
0/100
25%
Value15.5 s
0/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value15.7 s
6/100
10%
7279 ms
512 ms
759 ms
522 ms
1005 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 90% of them (125 requests) were addressed to the original Brcn.go.kr, 4% (6 requests) were made to Scontent.xx.fbcdn.net and 2% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (7.3 sec) belongs to the original domain Brcn.go.kr.
Page size can be reduced by 344.1 kB (50%)
690.7 kB
346.5 kB
In fact, the total size of Brcn.go.kr main page is 690.7 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. 70% of websites need less resources to load. Images take 282.5 kB which makes up the majority of the site volume.
Potential reduce by 104.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. 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 104.8 kB or 84% of the original size.
Potential reduce by 21.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. Brcn Go images are well optimized though.
Potential reduce by 148.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 148.8 kB or 74% of the original size.
Potential reduce by 69.1 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. Brcn.go.kr needs all CSS files to be minified and compressed as it can save up to 69.1 kB or 83% of the original size.
Number of requests can be reduced by 15 (11%)
134
119
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brcn 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 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
brcn.go.kr
7279 ms
common.css
512 ms
layout.css
759 ms
layout_rwd.css
522 ms
main.css
1005 ms
jquery-1.9.0.min.js
1314 ms
jquery.easing.1.3.js
746 ms
common.js
760 ms
gnb.js
981 ms
jquery.cycle.all.js
1473 ms
main.js
997 ms
script.js
1174 ms
jquery.printElement.js
1214 ms
slide.js
1236 ms
nanumgothic.css
64 ms
nanummyeongjo.css
78 ms
tab_list.js
542 ms
20160317080314_0.JPG
2701 ms
getImage.do
302 ms
slide_pop_prevbtn.gif
301 ms
slide_pop_nextbtn.gif
302 ms
popup_close_bul.gif
305 ms
popup_open_bul.gif
298 ms
nara.png
301 ms
logo.png
478 ms
rwd_search_btn.jpg
483 ms
slogon.png
487 ms
slogon2.png
486 ms
getImage.do
1708 ms
getImage.do
1031 ms
getImage.do
1426 ms
photoImage_down.do
2385 ms
getImage.do
969 ms
getImage.do
732 ms
getImage.do
997 ms
getImage.do
1218 ms
getImage.do
1245 ms
getImage.do
1288 ms
getImage.do
1460 ms
getImage.do
1488 ms
getImage.do
1547 ms
getImage.do
1895 ms
getImage.do
1701 ms
getImage.do
1732 ms
getImage.do
1807 ms
getImage.do
2184 ms
getImage.do
1946 ms
main_banner_prev.png
1973 ms
main_banner_next.png
2062 ms
main_banner_stop.png
2129 ms
BNR_201602010935338970.gif
2185 ms
BNR_201602010936138760.gif
2213 ms
BNR_201602110915449380.jpg
2317 ms
BNR_201510060150334490.jpg
2327 ms
NanumGothic-Regular.woff
101 ms
NanumGothic-Bold.woff
189 ms
NanumGothic-ExtraBold.woff
257 ms
board_more.gif
1574 ms
cont03_btn.png
1575 ms
posts
243 ms
widgets.js
139 ms
BNR_201509111023478340.jpg
2135 ms
BNR_201502040415514900.jpg
2134 ms
BNR_201502040416464280.jpg
2163 ms
BNR_201502040417252460.jpg
2281 ms
BNR_201502040418126140.jpg
2306 ms
BNR_201502040418538200.jpg
2320 ms
1422470_1728697627365560_6753509485731265232_n.png
91 ms
1915652_1754613818107274_3945366717141756838_n.jpg
89 ms
BNR_201502040419388000.jpg
2196 ms
BNR_201502040421151250.jpg
2193 ms
BNR_201502040421463850.jpg
2219 ms
BNR_201502040423150180.jpg
2351 ms
1422470_1728697627365560_6753509485731265232_n.png
32 ms
1489210_239223736252876_1998421553_n.jpg
5 ms
11781750_586652741488555_5494348660239909004_n.jpg
6 ms
12642912_504766723046938_2700889698494779638_n.jpg
5 ms
BNR_201502040424144210.jpg
2110 ms
BNR_201502040424576730.jpg
1893 ms
BNR_201502040425451870.jpg
1916 ms
BNR_201502040426402980.jpg
1883 ms
BNR_201502040427187130.jpg
1728 ms
BNR_201502040428080080.jpg
1848 ms
BNR_201502040429034110.jpg
1789 ms
BNR_201502040429389930.jpg
1675 ms
BNR_201502040430397930.jpg
1691 ms
BNR_201502040431280310.jpg
1663 ms
BNR_201505060720589410.jpg
1640 ms
BNR_201502040432418930.jpg
1610 ms
BNR_201502040433131830.jpg
1643 ms
BNR_201502040433502950.jpg
1602 ms
header_bg.png
1583 ms
site_link_bul_ov.png
1495 ms
site_link_bul.png
1481 ms
lang_bul.gif
1571 ms
gnb_animate_bg.gif
1508 ms
gnb_patternbg.gif
1469 ms
special_m_bg.png
1445 ms
gnb_titlebg.gif
1443 ms
gnb_depth3_bul.gif
1453 ms
blank_ico.gif
1462 ms
main_vi01.jpg
1954 ms
main_vi02.jpg
4303 ms
main_vi03.jpg
4101 ms
main_vi_control_btn.gif
1467 ms
main_search_inputbg.gif
1463 ms
total_search_bg.png
1441 ms
popularity_word_bg.gif
1531 ms
popularity_word_bul.gif
1542 ms
slide_banner_bg.png
1583 ms
slidebn_btn.png
1705 ms
mayor_infor_bg.jpg
1941 ms
mayor_infor_bul.png
1654 ms
main_mud2.png
1720 ms
board_bg.gif
1757 ms
sector_tab_bg.gif
1813 ms
sns_fb_bg.png
1886 ms
sns_tw_bg.png
1912 ms
visitor_service_bg.jpg
2051 ms
visitor_service_btn.jpg
1868 ms
minwon_bg.jpg
1940 ms
popup_prev.gif
1943 ms
popup_next.gif
2043 ms
popup_play.gif
2089 ms
relation_site_bg.gif
2027 ms
town_hall_bg.jpg
2034 ms
town_hall_bul.gif
2083 ms
city_council_bg.gif
2120 ms
city_council_bg02.png
2187 ms
footer_logo.jpg
2183 ms
footer_br_pt.gif
2116 ms
footer_br_logo.png
2177 ms
footer_br_bul.png
2217 ms
footer_m_bul.gif
2221 ms
top_btn.gif
2268 ms
slidebn_bul.png
2324 ms
board_bul.gif
2275 ms
board_more.gif
2197 ms
sns_fb_bg_ov.png
2213 ms
brcn.go.kr accessibility score
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
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.
brcn.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
brcn.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
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 Brcn.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 Brcn.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.
brcn.go.kr
Open Graph description is not detected on the main page of Brcn 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: