13.4 sec in total
1.5 sec
11.6 sec
283 ms
Click here to check amazing Otth content for South Korea. Otherwise, check out these important facts you probably never knew about otth.co.kr
FAQ, 강좌, 퀴즈게시판, 자주묻는질문, 제품소개
Visit otth.co.krWe analyzed Otth.co.kr page load time and found that the first response time was 1.5 sec and then it took 11.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.
otth.co.kr performance score
1517 ms
976 ms
592 ms
397 ms
451 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 96% of them (85 requests) were addressed to the original Otth.co.kr, 2% (2 requests) were made to Image.inicis.com and 1% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Otth.co.kr.
Page size can be reduced by 185.1 kB (25%)
737.3 kB
552.2 kB
In fact, the total size of Otth.co.kr main page is 737.3 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. 30% of websites need less resources to load. Images take 556.5 kB which makes up the majority of the site volume.
Potential reduce by 48.2 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 48.2 kB or 85% of the original size.
Potential reduce by 41.8 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. Otth images are well optimized though.
Potential reduce by 86.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 86.9 kB or 76% of the original size.
Potential reduce by 8.3 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. Otth.co.kr needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 80% of the original size.
Number of requests can be reduced by 18 (21%)
87
69
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otth. 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 as a result speed up the page load time.
index.php
1517 ms
common.js
976 ms
godo.cart_tab.js
592 ms
style.css
397 ms
style.css
451 ms
wcslog.js
23 ms
naverCommonInflowScript.js
453 ms
style_horizontal.css
505 ms
inipay_60x60_color.png
660 ms
escrow_60x60_gray.png
861 ms
close.gif
395 ms
btn_mypage_go.gif
445 ms
gnb_bg.gif
451 ms
main_t_left.gif
457 ms
logo.jpg
509 ms
header_btn_login.gif
523 ms
header_btn_joinus.gif
859 ms
header_btn_qna.gif
840 ms
header_btn_search.gif
847 ms
gnb_menu_cart.jpg
953 ms
gnb_menu_order.jpg
963 ms
gnb_menu_my.jpg
974 ms
gnb_menu_wish.jpg
1293 ms
gnb_menu_review.jpg
1302 ms
gnb_menu_cs.jpg
1304 ms
gnb_menu_community.jpg
1341 ms
sid_title.gif
1440 ms
sid_icon.gif
1473 ms
sid_tit_cscenter.gif
1736 ms
sid_ban_cscenter.gif
1757 ms
sid_tit_bank.gif
1728 ms
sid_btn_bank.gif
1821 ms
sid_btn_name.gif
1834 ms
sid_btn_account.gif
1926 ms
sid_ban_img01.gif
2135 ms
sid_ban_img02.gif
2157 ms
main_FLASH_1_20151201.jpg
3755 ms
tit_notice.gif
2231 ms
btn_more.gif
2333 ms
BANNER_01.jpg
2717 ms
main_mdchoice_tit.jpg
2807 ms
11246772911.jpg
2826 ms
1431354296233s0.jpg
2625 ms
1449043494661s0.jpg
2930 ms
1448895038306s0.JPG
3012 ms
1448870102514s0.jpg
3363 ms
blank.php
2844 ms
1448884660358s0.JPG
2814 ms
1448884721163s0.JPG
2943 ms
144533396444s0.JPG
3358 ms
main_new_tit.jpg
3154 ms
1453362111499s0.jpg
3171 ms
145336104756s0.jpg
2946 ms
1453355920873s0.jpg
3216 ms
1453354737367s0.jpg
3484 ms
1448884745220s0.JPG
3157 ms
main_best_tit.jpg
3259 ms
1394811047948s0.jpg
3482 ms
1429508222211s0.jpg
3108 ms
1340785198_s_0.jpg
3150 ms
11279724951.jpg
3266 ms
11170946601.jpg
3551 ms
main_priceoff_tit.jpg
3303 ms
1453360617981s0.jpg
3382 ms
1453360317942s0.jpg
3115 ms
1453355043485s0.jpg
3486 ms
144889510855s0.JPG
3273 ms
1448892905213s0.JPG
3312 ms
sky_ban_codi.gif
3422 ms
sky_btn_todayview.gif
3371 ms
sky_btn_up.gif
3260 ms
sky_btn_down.gif
3379 ms
sky_btn_top.gif
3425 ms
sky_btn_back.gif
3348 ms
sky_ban_event02.gif
3070 ms
fnb_company.gif
2973 ms
fnb_personal.gif
2978 ms
fnb_use.gif
3169 ms
fnb_cs.gif
3183 ms
fnb_partner.gif
3118 ms
fnb_lost.gif
2918 ms
bn_foots01.gif
2948 ms
bn_foots02.gif
2844 ms
foot_logo.jpg
2998 ms
btn_c_view.gif
2904 ms
icon_soldout
2923 ms
bg_foot.gif
2857 ms
m
474 ms
prevent.contents.copy.js
255 ms
otth.co.kr SEO score
N/A
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otth.co.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 Otth.co.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.
otth.co.kr
Open Graph description is not detected on the main page of Otth. 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: