6.4 sec in total
936 ms
5.2 sec
290 ms
Visit wannabem.co.kr now to see the best up-to-date Wannabem content for South Korea and also check out these interesting facts you probably never knew about wannabem.co.kr
Visit wannabem.co.krWe analyzed Wannabem.co.kr page load time and found that the first response time was 936 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wannabem.co.kr performance score
936 ms
216 ms
16 ms
512 ms
239 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wannabem.co.kr, 29% (30 requests) were made to Blogimgs.naver.net and 21% (22 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.0 MB (56%)
1.8 MB
800.0 kB
In fact, the total size of Wannabem.co.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. 60% of websites need less resources to load. Javascripts take 980.3 kB which makes up the majority of the site volume.
Potential reduce by 410 B
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 410 B or 44% of the original size.
Potential reduce by 79.3 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. Obviously, Wannabem needs image optimization as it can save up to 79.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 722.6 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 722.6 kB or 74% of the original size.
Potential reduce by 199.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. Wannabem.co.kr needs all CSS files to be minified and compressed as it can save up to 199.6 kB or 85% of the original size.
Number of requests can be reduced by 41 (39%)
104
63
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wannabem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
wannabem.co.kr
936 ms
mckpub
216 ms
Frameset-981964519.js
16 ms
PrologueList.nhn
512 ms
NBlogHidden.nhn
239 ms
Hidden-597428542.js
6 ms
MusicPlayer-449972894.js
19 ms
LayoutTopCommon-484882993.css
14 ms
player-846d457.css
10 ms
RemoveSubDomain-dea9950.js
11 ms
Jindo152-363950062.js
23 ms
LayoutTopCommon-730083628.js
19 ms
JindoComponent-318925938.js
21 ms
PrologueWebzine-71207160.css
44 ms
gnb_quirks_euckr.nhn
64 ms
spc.gif
46 ms
a1.jpg
565 ms
b1.jpg
532 ms
1603mcmabemh12_17-960x1133_%282%29.jpg
516 ms
b1.jpg
545 ms
thum1-%BB%E7%BA%BB.jpg
541 ms
a1.jpg
511 ms
aaa.jpg
1006 ms
b1.jpg
1002 ms
1603mcmacemr14_09-960x1440.jpg
1000 ms
b1.jpg
1475 ms
03-0363-SS-960x765.jpg
1111 ms
1602mcmafamh05_05-960x1445.jpg
1059 ms
1602mcmafamd36_03-960x1200.jpg
1506 ms
1602mcmafamk06-07.jpg
1613 ms
1602mcmgfamr06_08-1.jpg
1595 ms
----------crop-1.jpg
1723 ms
a1.jpg
1724 ms
b1.jpg
1960 ms
b1.jpg
2027 ms
a1.jpg
2059 ms
aaa.jpg
2092 ms
b1.jpg
2199 ms
PrologueList.nhn
297 ms
0015_login.png
40 ms
promo_npay.png
54 ms
11111111111111111111111111.jpg
584 ms
0101_image.gif
32 ms
btn_blogsearch.gif
31 ms
btn_confirm2.gif
35 ms
btn_thin_close.gif
26 ms
btn_close8.gif
23 ms
ico_file.gif
22 ms
btn_download2.gif
24 ms
btn_cancel3.gif
24 ms
btn_close3.gif
25 ms
btn_close5.gif
24 ms
shadow.png
23 ms
shadow02.png
24 ms
btn_confirm.gif
25 ms
btn_cancel.gif
24 ms
btn_close_1.gif
25 ms
201303_mari_3_01.jpg
517 ms
allowSwfForChrome-7dd9772.js
13 ms
LayoutBottomCommon-902441421.js
20 ms
btn_viewexif.gif
18 ms
btn_originaldn.gif
18 ms
spc.gif
18 ms
tit_viewexif.gif
19 ms
ico_notice2.gif
35 ms
btn_close.gif
35 ms
bg_not_available_word.gif
35 ms
btn_close3.gif
36 ms
btn_close.gif
36 ms
btn_ok.gif
36 ms
btn_close2.gif
36 ms
btn_confirm_pop2.gif
141 ms
btn_cancel_pop2.gif
141 ms
btn_close.gif
141 ms
ico_help.gif
142 ms
WidgetListAsync.nhn
332 ms
m
637 ms
ico_verified_pc.png
11 ms
0162_icon.gif
9 ms
201303_mari_3_01.jpg
549 ms
ExternalWidgetRender.nhn
812 ms
ExternalWidgetRender.nhn
902 ms
ExternalWidgetRender.nhn
929 ms
ExternalWidgetRender.nhn
935 ms
ExternalWidgetRender.nhn
936 ms
ExternalWidgetRender.nhn
939 ms
ExternalWidgetRender.nhn
1414 ms
ExternalWidgetRender.nhn
1588 ms
ExternalWidgetRender.nhn
1526 ms
ExternalWidgetRender.nhn
1559 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%B8%B6%B8%AE%C0%A5%BB%E7%C0%CC%C6%AE.jpg
959 ms
getLoginStatus.nhn
722 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%B8%B6%B8%AE%C6%E4%C0%CC%BD%BA%BA%CF.jpg
1003 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%B8%B6%B8%AE%C6%AE%C0%A7%C5%CD.jpg
968 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%B8%B6%B8%AE%C0%CC%BA%A5%C6%AE.jpg
1052 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%C7%C8%BE%F7%B4%F520.jpg
824 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%B8%DE%C1%BE_%C0%A5%BB%E7%C0%CC%C6%AE.png
782 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%B8%DE%C1%BE%C6%E4%C0%CC%BD%BA%BA%CF.jpg
1241 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%B8%DE%C1%BE%C0%CC%BA%A5%C6%AE.jpg
1033 ms
promo_npay_1603.png
7 ms
clickcrD.js
7 ms
0015_menu.png
202 ms
sp_gnb_v10.png
8 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%BF%C0%C7%C2%C4%B3%BD%BA%C6%AE.jpg
1212 ms
%BA%ED%B7%CE%B1%D7_%C0%A7%C1%AC_%B8%DE%C1%BE%C6%AE%C0%A7%C5%CD.jpg
1331 ms
wannabem.co.kr SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wannabem.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 Wannabem.co.kr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
wannabem.co.kr
Open Graph description is not detected on the main page of Wannabem. 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: