14.8 sec in total
900 ms
13.7 sec
171 ms
Welcome to ycc.ac.kr homepage info - get ready to check Ycc Ac best content for South Korea right away, or after learning these important things about ycc.ac.kr
Visit ycc.ac.krWe analyzed Ycc.ac.kr page load time and found that the first response time was 900 ms and then it took 13.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ycc.ac.kr performance score
name
value
score
weighting
Value19.6 s
0/100
10%
Value48.0 s
0/100
25%
Value37.7 s
0/100
10%
Value3,690 ms
1/100
30%
Value0.195
63/100
15%
Value51.1 s
0/100
10%
900 ms
595 ms
994 ms
595 ms
11 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 91% of them (154 requests) were addressed to the original Ycc.ac.kr, 5% (9 requests) were made to Heeil.http.or.kr and 2% (3 requests) were made to Cnf.http.or.kr. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Ycc.ac.kr.
Page size can be reduced by 327.5 kB (18%)
1.8 MB
1.5 MB
In fact, the total size of Ycc.ac.kr main page is 1.8 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 2.5 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 2.5 kB or 70% of the original size.
Potential reduce by 129.1 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. Ycc Ac images are well optimized though.
Potential reduce by 184.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 184.2 kB or 63% of the original size.
Potential reduce by 11.6 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. Ycc.ac.kr needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 75% of the original size.
Number of requests can be reduced by 22 (13%)
168
146
The browser has sent 168 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ycc Ac. 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 4 to 1 for CSS and as a result speed up the page load time.
ycc.ac.kr
900 ms
EchoScriptV2.js
595 ms
index.jsp
994 ms
main.css
595 ms
jquery.min.js
11 ms
default.js
814 ms
jaquery.jshowoff.js
817 ms
webwidget_slideshow_dot.css
398 ms
webwidget_slideshow_dot.js
637 ms
reset.css
199 ms
layout.css
200 ms
sr.gif
895 ms
20160223_gaegang.jpg
2968 ms
yjcwongo_20160316.jpg
1981 ms
20160304_yeunsue.jpg
3174 ms
20160304_yeunsue2.jpg
3387 ms
20160307_janghak.jpg
2376 ms
20160111_jankhak.jpg
1629 ms
lp_close.png
1834 ms
ico_home.gif
2039 ms
plus.gif
2179 ms
minus.gif
2241 ms
text.gif
2379 ms
logo.gif
2445 ms
mNav01_off.gif
2575 ms
gnb0101_off.png
2576 ms
gnb0109_off.png
2648 ms
gnb0102_off.png
2770 ms
gnb0103_off.png
2774 ms
gnb0104_off.png
2852 ms
gnb0105_off.png
2969 ms
gnb0106_off.png
2973 ms
gnb0107_off.png
3055 ms
gnb0108_off.png
3163 ms
mNav02_off.gif
3167 ms
gnb0201_off.png
3171 ms
gnb0210_off.png
3260 ms
gnb0203_off.png
3362 ms
gnb0204_off.png
3364 ms
gnb0205_off.png
3368 ms
gnb0206_off.png
3368 ms
gnb0207_off.png
3462 ms
gnb0208_off.png
3559 ms
gnb0209_off.png
3563 ms
mNav03_off1.gif
3567 ms
gnb0301_off.png
3565 ms
mNav04_off.gif
3579 ms
gnb0401_off.png
3661 ms
analytics.js
55 ms
collect
12 ms
ASP_Conf.js
1221 ms
gnb0402_off.png
2136 ms
gnb0403_off.png
1934 ms
gnb0404_off.png
1793 ms
gnb0405_off.png
1734 ms
[sr].gif
634 ms
emd_pt.js
640 ms
gnb0406_off.png
1605 ms
gnb0407_off.png
1636 ms
gnb0408_off.png
1586 ms
mNav05_off.gif
1588 ms
gnb0501_off.png
1524 ms
gnb0502_off.png
1395 ms
gnb0503_off.png
1406 ms
gnb0504_off.png
1431 ms
HTTP_s.js
1999 ms
gnb0505_off.png
1386 ms
gnb0506_off.png
1392 ms
gnb0507_off.png
1314 ms
mNav06_off.gif
1206 ms
gnb0601_off.png
1209 ms
gnb0602_off.png
1308 ms
gnb0603_off.png
1299 ms
gnb0604_off.png
1203 ms
gnb0605_off.png
1200 ms
gnb0606_off.png
1202 ms
gnb0607_off.png
1208 ms
gnbImg.gif
1629 ms
visual01.jpg
3564 ms
visual02.jpg
3571 ms
visual03.jpg
3771 ms
login.gif
1195 ms
num.gif
1198 ms
pass.gif
1301 ms
btn_login01.gif
1218 ms
btn_login02.gif
1401 ms
h3_01.gif
1412 ms
ico01_off.gif
1526 ms
main_txt01.gif
1583 ms
ico02_off.gif
1509 ms
main_txt02.gif
1539 ms
ico03_off.gif
1601 ms
main_txt03.gif
1610 ms
ico04_off.gif
1736 ms
main_txt04.gif
1785 ms
ico05_off.gif
1705 ms
main_txt05.gif
1749 ms
vision2020.jpg
2594 ms
tab01_on.gif
1809 ms
tab02_off.gif
1944 ms
tab03_off.gif
1997 ms
tab04_off.gif
2038 ms
more.gif
2021 ms
h3_02.gif
2156 ms
btn_larr.gif
2209 ms
btn_rarr.gif
2358 ms
btn_puz.gif
2396 ms
btn_play.gif
2450 ms
bner01.jpg
2602 ms
bner10.jpg
3802 ms
bner03.jpg
3378 ms
bner04.jpg
3553 ms
bner05.jpg
3746 ms
bner06.jpg
2789 ms
bner07.jpg
3788 ms
bner08.jpg
3383 ms
st.php
965 ms
bner09.jpg
3780 ms
h3_03.gif
3232 ms
phone.gif
3356 ms
icon01.gif
3350 ms
icon02.gif
3253 ms
icon044.gif
3206 ms
hakbup.jpg
3541 ms
hakbup-.jpg
3426 ms
h3_04.gif
3182 ms
movie.gif
3782 ms
homplist.gif
3067 ms
homplist01.gif
3181 ms
homplist10.gif
3186 ms
homplist03.gif
3060 ms
homplist04.gif
3144 ms
homplist05.gif
3015 ms
homplist06.gif
2970 ms
homplist07.gif
2854 ms
homplist08.gif
2791 ms
homplist09.gif
2797 ms
quickguide.jpg
3154 ms
sst.php
639 ms
quicktit.gif
2621 ms
banner_cuinfo.gif
2611 ms
btn_move.gif
2598 ms
tongsin.gif
2584 ms
btm_banner03.gif
2420 ms
btm_mark01.gif
2423 ms
btm_mark02.gif
2410 ms
log_run.php
615 ms
btm_mark03.jpg
4062 ms
mob.gif
2175 ms
st.php
876 ms
HTTP_s1_v4.js
1819 ms
face.gif
1800 ms
twi.gif
1636 ms
topBg.gif
1444 ms
bar.gif
1590 ms
mNav_bg02.gif
1578 ms
bg_visual.gif
1576 ms
bg_con.gif
1434 ms
bg_login.gif
1437 ms
bg_line.gif
1567 ms
bg_quick.gif
1557 ms
bull_dot.gif
1574 ms
ico03_on.gif
1406 ms
carousel_back_normal.png
1407 ms
carousel_circle_normal.png
1545 ms
carousel_next_normal.png
1404 ms
carousel_circle_solid.png
1419 ms
character.gif
962 ms
absence.gif
1046 ms
ycc.ac.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
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.
ycc.ac.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
ycc.ac.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ycc.ac.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 Ycc.ac.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.
ycc.ac.kr
Open Graph description is not detected on the main page of Ycc Ac. 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: