10.3 sec in total
535 ms
9.3 sec
443 ms
Click here to check amazing Yabada content. Otherwise, check out these important facts you probably never knew about yabada.co.kr
남성정력제, 미스터하이코코메디가격, 발기부전원인, 남성성기능개선, 정력좋아지는법, 정력강화제
Visit yabada.co.krWe analyzed Yabada.co.kr page load time and found that the first response time was 535 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yabada.co.kr performance score
535 ms
424 ms
653 ms
427 ms
444 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 99% of them (145 requests) were addressed to the original Yabada.co.kr, 1% (1 request) were made to Banol.weblog.cafe24.com and 1% (1 request) were made to Youbo.weblog.cafe24.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Yabada.co.kr.
Page size can be reduced by 1.5 MB (33%)
4.6 MB
3.1 MB
In fact, the total size of Yabada.co.kr main page is 4.6 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. 50% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 75.1 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 13.5 kB, which is 16% 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 75.1 kB or 87% of the original size.
Potential reduce by 1.4 MB
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. Obviously, Yabada needs image optimization as it can save up to 1.4 MB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 80.4 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 80.4 kB or 71% of the original size.
Potential reduce by 2.8 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. Yabada.co.kr needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 74% of the original size.
Number of requests can be reduced by 80 (55%)
146
66
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yabada. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
main.htm
535 ms
style.css
424 ms
jquery-1.4.2.min.js
653 ms
common.js
427 ms
capslock.js
444 ms
wrest.js
232 ms
weblog.js
608 ms
top_bg.gif
231 ms
start-btn.gif
217 ms
bookmark-btn.gif
219 ms
login-btn.gif
221 ms
join-btn.gif
215 ms
logo.jpg
405 ms
main_logo_banner8.gif
425 ms
main_logo_banner1.gif
640 ms
main_logo_banner2.gif
430 ms
main_logo_banner5.gif
438 ms
menu1_off.jpg
450 ms
menu2_off.jpg
621 ms
menu3_off.jpg
635 ms
menu4_off.jpg
644 ms
menu5_off.jpg
655 ms
menu6_off.jpg
664 ms
menu7_off.jpg
830 ms
menu8_off.jpg
847 ms
menu9_off.jpg
852 ms
dongyeongsang3-johwang-t.gif
860 ms
981313029_1mAsChaZ_Sequence_02.Still002.jpg
1948 ms
981313029_1Oj4e2Id_Sequence_01.Still001.jpg
1729 ms
2949210357_dxMnwbH7_BBE7C1F8_1707.jpg
1837 ms
2949203407_K1pnWVoJ_1_283329.JPG
1895 ms
dongyeongsang-johwang-b.gif
1067 ms
new_title.gif
1071 ms
chuljo_more.gif
1281 ms
340
1288 ms
339
1499 ms
338
1506 ms
337
1717 ms
new_b.gif
1721 ms
dongyeongsang-johwang-t.gif
1931 ms
3667752993_aFEGnTfS_BBE7C1F8_3533.jpg
2995 ms
981320230_t6zIBQ4O_20151118_121906.png
2375 ms
238041511_j94CLT1m_99-C1BEC7D5_BDC3C1F01.gif
2855 ms
weblog.js
600 ms
johwang.php
1922 ms
2949210357_dxMnwbH7_BBE7C1F8_1707.jpg
2574 ms
dongyeongsang2-johwang-t.gif
1953 ms
1888616534_ZhmOT8QD_20140930_100356.png
2760 ms
1888616534_yb0ki2fh_20140930_093742.png
3240 ms
3067247144_b85fhUKy_2014-04-09_173B203B42.jpg
2406 ms
3067246944_Wy7RNkBq_2014-03-20_113B213B11.jpg
2588 ms
nak-notice-3.gif
2596 ms
1889277261_k7BlwmX5_DSC_7823.MOV.Still003.jpg
2633 ms
3067220596_oIpZrvKu_Sequence_02.Still026.jpg
2745 ms
1925939736_laE1JVjA_DSC_6365.jpg
2618 ms
nak-tbl-b.gif
2593 ms
nak-notice-4.gif
2605 ms
board_icon.gif
2633 ms
nak-notice-5.gif
2751 ms
notice-t1ov.gif
2777 ms
notice-t2.gif
2628 ms
notice-more.gif
2607 ms
notice-t1.gif
2627 ms
notice-t2ov.gif
2756 ms
bg_left.gif
2589 ms
title.gif
2596 ms
id.gif
2388 ms
pw.gif
2392 ms
login_btn.gif
2182 ms
auto.gif
2319 ms
join.gif
2149 ms
pwid_sch.gif
2160 ms
bottom_line.gif
2156 ms
bg_right.gif
2064 ms
main-notice-t1.gif
1992 ms
board_icon.gif
2105 ms
main-notice-b.gif
2139 ms
main-notice-t2.gif
1966 ms
move_title.gif
1935 ms
barogagi_menu1.gif
1714 ms
barogagi_menu5.gif
1331 ms
barogagi_menu2.gif
1444 ms
barogagi_menu6.gif
1439 ms
barogagi_menu3.gif
1317 ms
barogagi_menu7.gif
1316 ms
barogagi_menu4.gif
1307 ms
barogagi_menu8.gif
1315 ms
main_right_banner3.jpg
1397 ms
main_right_banner4.jpg
1308 ms
main_right_banner12.gif
1290 ms
main_right_banner9.gif
1292 ms
main_right_banner10.jpg
1293 ms
main_right_banner8.gif
1285 ms
main_right_banner2.jpg
1274 ms
main_right_banner7.gif
1267 ms
main_right_banner11.gif
1276 ms
main_right_banner13.jpg
1289 ms
main_right_banner6.jpg
1302 ms
address_menu_1.gif
1299 ms
address_menu_bar.gif
1280 ms
address_menu_2.gif
1257 ms
address_menu_3.gif
1303 ms
address_menu_4.gif
1302 ms
address_menu_5.gif
1302 ms
address_menu_6.gif
1312 ms
address_menu_7.gif
1279 ms
address_menu_8.gif
1248 ms
address_menu_9.gif
1303 ms
address_menu_10.gif
1303 ms
menu_bg.jpg
1323 ms
dongyeongsang-johwang-bg.gif
1315 ms
new_t.gif
1279 ms
new_bg.gif
1234 ms
nak-tbl-bg.gif
1309 ms
bg_line.gif
1370 ms
notice-bg.gif
1325 ms
capslock.gif
1440 ms
main-notice-bg.gif
1279 ms
bg_line.gif
1230 ms
address_menu_bg.gif
1319 ms
wrest.gif
1543 ms
ji_yeokbyeol_t.gif
1366 ms
ji_yeokbyeol_title.gif
1395 ms
ji_yeokbyeol_btn1ov.gif
1278 ms
ji_yeokbyeol_btn2.gif
1411 ms
ji_yeokbyeol_btn3.gif
1403 ms
ji_yeokbyeol_btn4.gif
1403 ms
ji_yeokbyeol_btn5.gif
1402 ms
ji_yeokbyeol_btn6.gif
1398 ms
ji_yeokbyeol_btn7.gif
1396 ms
ji_yeokbyeol_btn8.gif
1425 ms
ji_yeokbyeol_btn9.gif
1404 ms
ji_yeokbyeol_btn10.gif
1401 ms
ji_yeokbyeol_btn11.gif
1374 ms
ji_yeokbyeol_btn12.gif
1392 ms
ji_yeokbyeol_bg.gif
1396 ms
seon_icon.gif
1444 ms
u_icon.gif
1385 ms
gaet_icon.gif
1373 ms
tema_t.gif
1379 ms
tema_bg.gif
1385 ms
tema_b.gif
1399 ms
ji_yeokbyeol_num1ov.gif
1434 ms
ji_yeokbyeol_num2.gif
1380 ms
ji_yeokbyeol_num3.gif
1377 ms
ji_yeokbyeol_b.gif
1367 ms
move_t1ov.gif
217 ms
yabada.co.kr SEO score
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yabada.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Yabada.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.
yabada.co.kr
Open Graph description is not detected on the main page of Yabada. 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: