14.3 sec in total
646 ms
13.4 sec
228 ms
Visit gglec.go.kr now to see the best up-to-date Gglec Go content for South Korea and also check out these interesting facts you probably never knew about gglec.go.kr
Visit gglec.go.krWe analyzed Gglec.go.kr page load time and found that the first response time was 646 ms and then it took 13.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.
gglec.go.kr performance score
name
value
score
weighting
Value17.5 s
0/100
10%
Value24.2 s
0/100
25%
Value17.7 s
0/100
10%
Value120 ms
97/100
30%
Value0.235
53/100
15%
Value19.6 s
2/100
10%
646 ms
2680 ms
789 ms
603 ms
404 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 91% of them (95 requests) were addressed to the original Gglec.go.kr, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (9.5 sec) belongs to the original domain Gglec.go.kr.
Page size can be reduced by 229.6 kB (43%)
533.8 kB
304.1 kB
In fact, the total size of Gglec.go.kr main page is 533.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 265.4 kB which makes up the majority of the site volume.
Potential reduce by 71.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. This page needs HTML code to be minified as it can gain 12.9 kB, which is 14% 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 71.8 kB or 78% of the original size.
Potential reduce by 26.3 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. Gglec Go images are well optimized though.
Potential reduce by 106.6 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 106.6 kB or 73% of the original size.
Potential reduce by 25.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. Gglec.go.kr needs all CSS files to be minified and compressed as it can save up to 25.0 kB or 81% of the original size.
Number of requests can be reduced by 12 (13%)
96
84
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gglec 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 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
gglec.go.kr
646 ms
default.aspx
2680 ms
mainNew.css
789 ms
commonNew.js
603 ms
khk.js
404 ms
jquery-1.11.3.min.js
1844 ms
jquery.bxSlider.js
1577 ms
common.css
200 ms
board.css
401 ms
nanumgothic.css
30 ms
mainBody.gif
265 ms
logo.gif
263 ms
title_search.gif
213 ms
btn_search.gif
257 ms
gnb1.gif
211 ms
line_gray.gif
211 ms
btn_lnb2.gif
423 ms
line_gray.gif
424 ms
btn_lnb3.gif
422 ms
btn_lnb10.gif
512 ms
btn_lnb4.gif
523 ms
btn_lnb5.gif
527 ms
btn_lnb6.gif
599 ms
btn_lnb11.gif
602 ms
btn_lnb1.gif
602 ms
btn_rollStop.jpg
9008 ms
btn_rollPlay.jpg
9470 ms
popupzone_160218.gif
1325 ms
popupzone_150804.gif
1812 ms
title_id.png
840 ms
btn_login.png
830 ms
title_pw.png
1033 ms
btn_findid.png
1044 ms
btn_findpw.png
1233 ms
btn_join.png
1240 ms
ban01.jpg
2031 ms
title_favo.png
1440 ms
micon10.png
1588 ms
micon01.png
1641 ms
micon02.png
1851 ms
micon03.png
1841 ms
micon04.png
2007 ms
micon05.png
2042 ms
micon06.png
2115 ms
micon07.png
2204 ms
minix.php
632 ms
micon08.png
2205 ms
NanumGothic-Regular.woff
37 ms
NanumGothic-Bold.woff
82 ms
NanumGothic-ExtraBold.woff
83 ms
sdk.js
272 ms
title_calan.png
2040 ms
btn_cal_prev.png
2177 ms
btn_cal_next.png
2197 ms
example.png
2183 ms
ttitle_reserv.png
2190 ms
btn_more.png
2393 ms
main_roling_img01.jpg
2579 ms
popupzone_130821.gif
2415 ms
147 ms
btn_rollStop.png
2217 ms
xd_arbiter.php
227 ms
xd_arbiter.php
429 ms
btn_rollPlay.png
2343 ms
btn_banner_prev.png
2397 ms
btn_banner_next.png
2512 ms
btn_banner_allview.gif
2457 ms
n_banner1.jpg
2581 ms
n_banner2.jpg
2596 ms
n_banner3.jpg
2408 ms
n_banner4.jpg
2413 ms
n_banner5.jpg
2414 ms
n_banner6.jpg
2353 ms
n_banner7.jpg
2204 ms
n_banner8.png
2212 ms
gnb_t_logo.gif
2272 ms
n_banner12.jpg
2197 ms
n_banner13.jpg
2122 ms
n_banner15.jpg
2020 ms
n_banner16.jpg
1991 ms
n_banner18.jpg
2000 ms
n_banner19.jpg
2012 ms
n_banner20.jpg
1968 ms
n_banner21.jpg
1977 ms
(110215)info_open_banner.gif
2004 ms
(110311)multiculture_banner.jpg
1955 ms
n_banner30.jpg
2042 ms
site_bn30.gif
1978 ms
site_bn33.gif
2007 ms
logo.png
1897 ms
%EA%B5%AD%EB%AF%BC%EC%95%88%EC%A0%84%EC%B2%98.jpg
2006 ms
%EA%B2%BD%EA%B8%B0%EB%8F%84%EA%B5%90%EC%9C%A1%EC%B2%AD_%EB%B3%B5%EC%A7%80%EB%B2%95%EB%AC%B4%EA%B3%BC_%EB%B0%B0%EB%84%88.png
2082 ms
btn_select_go.gif
2011 ms
footlogo.gif
1836 ms
marc_wa.gif
1964 ms
bg_sec3.png
1822 ms
bg_calico1.png
1834 ms
bg_calico2.png
1865 ms
bg_news.gif
1815 ms
bul_dot3pxlight.gif
1822 ms
bg_tabR.gif
1834 ms
bg_slit.gif
1865 ms
bg_no_on.png
1816 ms
bg_no_off.png
1821 ms
gglec.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
gglec.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
Page has valid source maps
gglec.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
N/A
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gglec.go.kr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Korean. Our system also found out that Gglec.go.kr main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
gglec.go.kr
Open Graph description is not detected on the main page of Gglec 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: