9.9 sec in total
698 ms
8.7 sec
438 ms
Visit yido.kr now to see the best up-to-date Yido content and also check out these interesting facts you probably never knew about yido.kr
Visit yido.krWe analyzed Yido.kr page load time and found that the first response time was 698 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yido.kr performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value7.6 s
4/100
25%
Value4.5 s
73/100
10%
Value0 ms
100/100
30%
Value0.328
35/100
15%
Value3.5 s
92/100
10%
698 ms
253 ms
232 ms
457 ms
460 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 92% of them (126 requests) were addressed to the original Yido.kr, 7% (10 requests) were made to Ajax.googleapis.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Yido.kr.
Page size can be reduced by 122.1 kB (13%)
941.5 kB
819.4 kB
In fact, the total size of Yido.kr main page is 941.5 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. 40% of websites need less resources to load. Images take 809.9 kB which makes up the majority of the site volume.
Potential reduce by 40.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 14.6 kB, which is 31% 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 40.8 kB or 88% of the original size.
Potential reduce by 12.9 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. Yido images are well optimized though.
Potential reduce by 29.9 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 29.9 kB or 78% of the original size.
Potential reduce by 38.5 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. Yido.kr needs all CSS files to be minified and compressed as it can save up to 38.5 kB or 82% of the original size.
Number of requests can be reduced by 46 (34%)
135
89
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yido. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
yido.kr
698 ms
main_new.php
253 ms
common.css
232 ms
mEmbed.js
457 ms
member.js
460 ms
jquery.js
86 ms
jquery-ui.min.js
97 ms
jquery.ui.datepicker-ko.js
460 ms
jquery.ui.all.css
462 ms
jsapi
69 ms
lib.validate.js
458 ms
comm.js
458 ms
ajax_register_form.js
695 ms
navi.js
699 ms
rollBanner.js
695 ms
ad_style.css
496 ms
ad_style_board.css
500 ms
jquery.ui.base.css
233 ms
jquery.ui.theme.css
226 ms
jquery.ui.core.css
239 ms
jquery.ui.button.css
234 ms
jquery.ui.datepicker.css
232 ms
prototype.js
33 ms
scriptaculous.js
86 ms
builder.js
25 ms
effects.js
26 ms
dragdrop.js
32 ms
controls.js
72 ms
slider.js
30 ms
sound.js
49 ms
menu1.jpg
214 ms
menu2.jpg
211 ms
menu3.jpg
204 ms
menu8.jpg
209 ms
menu5.jpg
206 ms
menu6.jpg
211 ms
menu7.jpg
407 ms
menu9.jpg
409 ms
menu1_smu.jpg
424 ms
menu1_smu2.jpg
406 ms
menu1_smu3.jpg
412 ms
menu1_smu3_1.jpg
410 ms
menu1_smu3_2.jpg
603 ms
menu1_smu3_3.jpg
608 ms
menu9_smu.jpg
609 ms
menu9_smu2.jpg
609 ms
menu9_smu3.jpg
610 ms
menu2_smu7.jpg
619 ms
menu3_smu.jpg
800 ms
menu4_smu.jpg
807 ms
menu4_smu2.jpg
810 ms
menu4_smu3.jpg
807 ms
menu5_smu.jpg
810 ms
menu5_smu3.jpg
825 ms
menu5_smu4.jpg
1038 ms
menu6_smu.jpg
1041 ms
menu6_smu2.jpg
1042 ms
menu8_smu.jpg
1042 ms
menu8_smu2.jpg
1043 ms
menu8_smu4.jpg
1046 ms
menu8_smu5.jpg
1262 ms
logo.jpg
1266 ms
pottery.jpg
1261 ms
korean.jpg
1271 ms
english.jpg
1266 ms
btn_id.jpg
1273 ms
btn_pw.jpg
1283 ms
btn_login.jpg
1284 ms
btn_join.jpg
1289 ms
facebook.jpg
1287 ms
blog.jpg
1090 ms
btn_num1_on.png
1100 ms
btn_num2_out.png
1295 ms
btn_num3_out.png
1286 ms
btn_num4_out.png
1283 ms
btn_num5_out.png
1285 ms
btn_num6_out.png
1100 ms
btn_num7_out.png
1105 ms
banner01.jpg
2690 ms
banner02.jpg
3166 ms
banner03.jpg
2683 ms
banner04.jpg
3393 ms
banner05.jpg
2948 ms
banner06.jpg
2491 ms
banner07.jpg
3096 ms
notice_new.jpg
2727 ms
more.jpg
2727 ms
dot.jpg
2942 ms
press_new.jpg
2941 ms
banner_paris.jpg
2996 ms
yidopottery.jpg
2922 ms
lineEx1.jpg
2918 ms
lineEx2.jpg
2928 ms
lineEx3.jpg
3893 ms
banner03.jpg
3277 ms
banner04.jpg
3339 ms
hands.jpg
3124 ms
academy.jpg
2906 ms
academy02.jpg
2941 ms
media.jpg
3136 ms
ycc02.jpg
3193 ms
copy.jpg
3268 ms
board_bg.jpg
3129 ms
board_bg2.jpg
3156 ms
copy_bg.jpg
3197 ms
noimg_240.jpg
3272 ms
blank.gif
213 ms
menu8_o.jpg
217 ms
menu1_smu_o.jpg
209 ms
menu1_smu2_o.jpg
205 ms
menu1_smu3_o.jpg
216 ms
menu9_smu_o.jpg
213 ms
menu9_smu2_o.jpg
215 ms
menu9_smu3_o.jpg
432 ms
menu2_smu_o.jpg
436 ms
menu2_smu2_o.jpg
439 ms
menu2_smu3_o.jpg
443 ms
menu2_smu4_o.jpg
442 ms
menu2_smu5_o.jpg
442 ms
menu2_smu6_o.jpg
647 ms
menu3_smu_o.jpg
649 ms
menu3_smu2_o.jpg
646 ms
menu3_smu3_o.jpg
647 ms
menu3_smu4_o.jpg
648 ms
menu3_smu5_o.jpg
647 ms
menu4_smu_o.jpg
839 ms
menu4_smu2_o.jpg
843 ms
menu4_smu3_o.jpg
848 ms
menu5_smu_o.jpg
859 ms
menu5_smu4_o.jpg
847 ms
menu6_smu_o.jpg
857 ms
menu6_smu2_o.jpg
1041 ms
menu7_smu_o.jpg
1052 ms
menu7_smu2_o.jpg
1051 ms
menu8_smu_o.jpg
1051 ms
menu8_smu2_o.jpg
1055 ms
menu8_smu4_o.jpg
1067 ms
yido.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
yido.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
yido.kr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yido.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Yido.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.
yido.kr
Open Graph description is not detected on the main page of Yido. 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: