7.7 sec in total
759 ms
6.2 sec
824 ms
Welcome to mstockblog.com homepage info - get ready to check Mstockblog best content for South Korea right away, or after learning these important things about mstockblog.com
Visit mstockblog.comWe analyzed Mstockblog.com page load time and found that the first response time was 759 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mstockblog.com performance score
759 ms
242 ms
42 ms
440 ms
305 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mstockblog.com, 30% (30 requests) were made to Blogimgs.naver.net and 24% (24 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 953.6 kB (52%)
1.8 MB
864.1 kB
In fact, the total size of Mstockblog.com 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 400 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 400 B or 44% of the original size.
Potential reduce by 31.0 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. Mstockblog images are well optimized though.
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. Mstockblog.com 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 42 (42%)
100
58
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mstockblog. 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.
mstockblog.com
759 ms
miraeasset_m
242 ms
Frameset-981964519.js
42 ms
PrologueList.nhn
440 ms
NBlogHidden.nhn
305 ms
Hidden-597428542.js
51 ms
MusicPlayer-449972894.js
170 ms
LayoutTopCommon-484882993.css
39 ms
player-846d457.css
118 ms
RemoveSubDomain-dea9950.js
122 ms
Jindo152-363950062.js
158 ms
LayoutTopCommon-730083628.js
125 ms
JindoComponent-318925938.js
210 ms
PrologueWebzine-71207160.css
136 ms
gnb_quirks_euckr.nhn
188 ms
allowSwfForChrome-7dd9772.js
113 ms
LayoutBottomCommon-902441421.js
177 ms
spc.gif
154 ms
20160328_%B9%CC%B7%A1%BF%A1%BC%C2_%BD%C4%B4%E7%C3%A2%BE%F702.png
287 ms
btn_confirm2.gif
154 ms
profile.png
151 ms
ico_help.gif
157 ms
20160326_%B9%CC%B7%A1%BF%A1%BC%C2_%C1%F6%BD%C4%C0%CE_%B9%E8%B4%E7%B1%DD_04.png
1146 ms
20160325_%B9%CC%B7%A1%BF%A1%BC%C2%C1%F5%B1%C7_%BA%CE%B5%BF%BB%EA_%C1%D8%C0%FC%BC%BC_06.png
1140 ms
20160324_%B9%CC%B7%A1%BF%A1%BC%C2%C5%F5%B5%A5%C0%CC_%B3%EB%C0%CE_01.png
1138 ms
20160323_%BE%D7%B8%E9%B0%A1_%BD%C3%B0%A1_03.png
1141 ms
20160328_%B9%CC%B7%A1%BF%A1%BC%C2_%BD%C4%B4%E7%C3%A2%BE%F702.png
1141 ms
20160326_%B9%CC%B7%A1%BF%A1%BC%C2_%C1%F6%BD%C4%C0%CE_%B9%E8%B4%E7%B1%DD_04.png
1141 ms
20160322_%BD%C3%BB%E7%B1%DD%C0%B6%BF%EB%BE%EE_%B0%AD%BD%C3%B1%E2%BE%F7_02.png
1145 ms
201603022_%C0%BA%C5%F0_%C8%C4_%B1%E2%BC%FA%C3%A2%BE%F7_01.png
1347 ms
2016314_%B9%CC%B7%A1%BF%A1%BC%C2_%BA%F1%B4%EB%B8%E9_%C0%CC%BA%A5%C6%AE_00_00.png
1196 ms
20160317_%C0%DA%B1%E2%BC%D2%B0%B3%BC%AD_02.png
1290 ms
20160316_%BA%EA%B7%BA%BD%C3%C6%AE_%C0%CC%C0%AF_01.png
1356 ms
201603011_%C0%FD%BC%BC%BD%C3%B4%EB_%C0%CC%BA%A5%C6%AE_%C0%CC%B9%CC%C1%F6_01.png
1529 ms
2016315_%B1%DB%B7%A1%BD%BA%BD%BA%C6%BC%B0%C9%B9%FD_05.png
1659 ms
20160314_ISA_%B0%E8%C1%C2_01.png
1734 ms
20160311_%B9%CC%B7%A1%BF%A1%BC%C2%C1%F5%B1%C7_%BA%CE%B5%BF%BB%EA_114_%C0%FC%BC%BC_00.png
1862 ms
20160309_%BA%CE%B5%BF%BB%EA_%B8%ED%B5%B5_%BC%D2%BC%DB_03.png
1852 ms
20160307_2016%B3%E2_3%BF%F9_%C5%F5%C0%DA%C5%B0%BF%F6%B5%E5_01.png
1924 ms
20160328_%B9%CC%B7%A1%BF%A1%BC%C2%C5%F5%B5%A5%C0%CC_01.png
2255 ms
20160325_%B9%CC%B7%A1%BF%A1%BC%C2%C5%F5%B5%A5%C0%CC01.png
2217 ms
20160324_%B9%CC%B7%A1%BF%A1%BC%C2%C5%F5%B5%A5%C0%CC6.png
2240 ms
20160323_%B8%F0%B9%D9%C0%CF_%B8%DE%BD%C5%C0%FA.png
2375 ms
20160322_%B9%CC%B7%A1%BF%A1%BC%C2%C1%F5%B1%C7_%B1%DD%B8%AE_01.png
2394 ms
20160321_%B9%CC%B7%A1%BF%A1%BC%C2%C5%F5%B5%A5%C0%CC_%C1%DF%B1%B9_01.png
2664 ms
ico_n.gif
140 ms
ico-ccl1-by-nc-nd.gif
143 ms
btn_thin_close.gif
143 ms
btn_close8.gif
138 ms
ico_file.gif
139 ms
btn_download2.gif
257 ms
btn_cancel3.gif
257 ms
btn_close3.gif
260 ms
btn_close5.gif
250 ms
btn_confirm.gif
248 ms
btn_cancel.gif
250 ms
btn_close_1.gif
254 ms
btn_viewexif.gif
253 ms
btn_originaldn.gif
253 ms
spc.gif
254 ms
tit_viewexif.gif
255 ms
ico_notice2.gif
254 ms
btn_close.gif
289 ms
btn_close3.gif
289 ms
btn_close.gif
288 ms
btn_ok.gif
293 ms
btn_close2.gif
293 ms
btn_confirm_pop2.gif
292 ms
btn_cancel_pop2.gif
1099 ms
btn_close.gif
1097 ms
skin.jpg
1130 ms
0009_login.png
232 ms
promo_npay.png
207 ms
profile_top.gif
1076 ms
btn_blogsearch.gif
994 ms
shadow.png
992 ms
shadow02.png
992 ms
bg_not_available_word.gif
986 ms
exchange01_1.gif
137 ms
exchange01_2.gif
144 ms
0102_image.gif
143 ms
WidgetListAsync.nhn
1108 ms
m
745 ms
ExternalWidgetRender.nhn
2367 ms
ExternalWidgetRender.nhn
1629 ms
profile.png
526 ms
0162_icon.gif
68 ms
getLoginStatus.nhn
708 ms
promo_npay_1603.png
53 ms
clickcrD.js
50 ms
0009_menu.png
52 ms
sp_gnb_v10.png
104 ms
151015165530.jpg
1148 ms
151015165536.jpg
1145 ms
151015165542.jpg
1143 ms
151015165549.jpg
1144 ms
151015165556.jpg
1143 ms
151015165603.jpg
1142 ms
151015164201.jpg
902 ms
151015164215.jpg
663 ms
151015164208.jpg
901 ms
mstockblog.com SEO score
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mstockblog.com 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 Mstockblog.com 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.
mstockblog.com
Open Graph description is not detected on the main page of Mstockblog. 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: