13 sec in total
1.8 sec
10.6 sec
613 ms
Click here to check amazing Osanjunggo content. Otherwise, check out these important facts you probably never knew about osanjunggo.co.kr
http://wluv.kr
Visit osanjunggo.co.krWe analyzed Osanjunggo.co.kr page load time and found that the first response time was 1.8 sec and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
osanjunggo.co.kr performance score
1802 ms
463 ms
698 ms
473 ms
239 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 97% of them (109 requests) were addressed to the original Osanjunggo.co.kr, 3% (3 requests) were made to Clicksaver.co.kr. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Osanjunggo.co.kr.
Page size can be reduced by 448.0 kB (6%)
7.2 MB
6.7 MB
In fact, the total size of Osanjunggo.co.kr main page is 7.2 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. 30% of websites need less resources to load. Images take 7.1 MB which makes up the majority of the site volume.
Potential reduce by 38.6 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 10.0 kB, which is 22% 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 38.6 kB or 86% of the original size.
Potential reduce by 372.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. Osanjunggo images are well optimized though.
Potential reduce by 18.7 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 18.7 kB or 73% of the original size.
Potential reduce by 18.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. Osanjunggo.co.kr needs all CSS files to be minified and compressed as it can save up to 18.6 kB or 83% of the original size.
Number of requests can be reduced by 23 (21%)
111
88
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Osanjunggo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
osanjunggo.co.kr
1802 ms
common.css
463 ms
inc_flash.js
698 ms
quick.js
473 ms
layout.css
239 ms
style.css
706 ms
C015B5209.js
620 ms
ClicksaverScript.js
889 ms
ico_banner.gif
247 ms
btn_homr.gif
245 ms
bar.gif
245 ms
btn_login.GIF
251 ms
btn_join.gif
244 ms
btn_company.gif
467 ms
bar2.gif
474 ms
btn_customer.gif
475 ms
btn_map.gif
473 ms
btn_community.gif
474 ms
logo_09.gif
495 ms
but_close.jpg
1159 ms
btn_search.gif
703 ms
title_09.gif
717 ms
tel_09.gif
735 ms
time.gif
722 ms
time_09.gif
744 ms
btn_map.gif
932 ms
btn_sell.gif
944 ms
p01out.gif
964 ms
p02out.gif
965 ms
p03out.gif
975 ms
p04out.gif
1162 ms
p05out.gif
1170 ms
p06out.gif
1192 ms
p07out.gif
1196 ms
p09out.gif
1209 ms
p10out.gif
1386 ms
p11out.gif
1391 ms
p12out.gif
1403 ms
p13out.gif
1419 ms
p14out.gif
1424 ms
p15out.gif
1437 ms
p16out.gif
1617 ms
p17out.gif
1620 ms
p18out.gif
1622 ms
banner.asp
1414 ms
p19out.gif
1418 ms
p20out.gif
1430 ms
p00.gif
1612 ms
p21out.gif
1393 ms
p22out.gif
1387 ms
p23out.gif
1411 ms
p24out.gif
1417 ms
p25out.gif
1432 ms
p26out.gif
1593 ms
www.clicksaver.co.kr
196 ms
newbox1.gif
1386 ms
newbox2.gif
1375 ms
71906_1.jpg
2368 ms
40618_1.jpg
2001 ms
50687_1.jpg
2490 ms
46145_1.jpg
2835 ms
66031_1.jpg
2815 ms
66032_1.jpg
2826 ms
hotbox1.gif
2197 ms
hotbox2.gif
2166 ms
70364_1.jpg
3198 ms
73703_1.jpg
3330 ms
67431_1.jpg
3433 ms
67432_1.jpg
3736 ms
69437_1.jpg
3795 ms
67600_1.jpg
3768 ms
hitbox1.gif
3386 ms
hitbox2.gif
3345 ms
72897_1.jpg
4400 ms
67345_1.jpg
4411 ms
72314_1.jpg
4493 ms
74390_1.jpg
4683 ms
72880_1.jpg
4725 ms
40613_1.jpg
3612 ms
72568_1.jpg
4800 ms
63286_1.jpg
5364 ms
58679_1.jpg
5478 ms
49194_1.jpg
5594 ms
70875_1.jpg
5438 ms
67344_1.jpg
5494 ms
57643_1.jpg
5796 ms
74627_1.jpg
6302 ms
title_notice.gif
5484 ms
img_cust.gif
5605 ms
bank_09.gif
5438 ms
title_cust.gif
5501 ms
title_time.gif
5510 ms
btn_fmap.gif
4816 ms
btn_ffaq.gif
4669 ms
btn_fsell.gif
4645 ms
m_01.gif
4508 ms
bar.gif
4453 ms
m_02.gif
4202 ms
m_03.gif
4194 ms
m_04.gif
4248 ms
logo_09.gif
3712 ms
search_box.gif
3631 ms
menubar.gif
3616 ms
left_box.jpG
3589 ms
right_box.jpg
3554 ms
boxbg.gif
3372 ms
hitbox3.gif
3385 ms
cust_box.gif
3422 ms
dot.gif
3213 ms
box.gif
2652 ms
box_hit01.gif
2700 ms
box_hit02.gif
2621 ms
osanjunggo.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 Osanjunggo.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 Osanjunggo.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.
osanjunggo.co.kr
Open Graph description is not detected on the main page of Osanjunggo. 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: