10.9 sec in total
2.4 sec
7.9 sec
515 ms
Click here to check amazing M Story content. Otherwise, check out these important facts you probably never knew about m-story.org
Visit m-story.orgWe analyzed M-story.org page load time and found that the first response time was 2.4 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
m-story.org performance score
2420 ms
220 ms
453 ms
644 ms
219 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original M-story.org, 28% (32 requests) were made to Blogimgs.naver.net and 24% (27 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Blogfiles2.naver.net.
Page size can be reduced by 965.5 kB (49%)
2.0 MB
1.0 MB
In fact, the total size of M-story.org main page is 2.0 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. 65% of websites need less resources to load. Javascripts take 980.3 kB which makes up the majority of the site volume.
Potential reduce by 406 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 406 B or 45% of the original size.
Potential reduce by 42.9 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. M Story 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. M-story.org 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 52 (46%)
113
61
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Story. 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.
m-story.org
2420 ms
hellomstory
220 ms
Frameset-981964519.js
453 ms
PrologueList.nhn
644 ms
NBlogHidden.nhn
219 ms
Hidden-597428542.js
4 ms
MusicPlayer-449972894.js
13 ms
LayoutTopCommon-484882993.css
18 ms
player-846d457.css
31 ms
RemoveSubDomain-dea9950.js
35 ms
Jindo152-363950062.js
39 ms
LayoutTopCommon-730083628.js
55 ms
JindoComponent-318925938.js
51 ms
PrologueWebzine-71207160.css
51 ms
gnb_quirks_euckr.nhn
245 ms
allowSwfForChrome-7dd9772.js
49 ms
LayoutBottomCommon-902441421.js
49 ms
N%BD%BA%C5%B2-8.jpg
3116 ms
spc.gif
1024 ms
sprout-316127_960_720.jpg
1056 ms
btn_confirm2.gif
297 ms
%EB%8C%80%EC%84%B1%EC%A0%84_%EA%B0%80%EC%9A%B4%EB%8D%B0(%ED%94%84%EB%A1%9C%ED%95%84%EC%9A%A9_wh).jpg
1052 ms
%B8%DE%C0%CE.jpg
1055 ms
image.JPEG
1050 ms
%B8%DE%C0%CE%2B.jpg
1050 ms
%B8%B8%B9%CE.%B4%EB%C0%D4.%BC%F6%BD%C3%C7%D5%B0%DD.jpg
1051 ms
%B8%B8%B9%CE%C1%DF%BE%D3%B1%B3%C8%B8.%B1%C7%BC%F8%C8%F1%C1%FD%BB%E7.jpg
1048 ms
%C6%AF%BA%B0%C5%E4%C2%F9.jpg
1319 ms
title%2B_%BA%B9%BB%E7.jpg
2282 ms
title%2B.jpg
2283 ms
title.jpg
2285 ms
%B8%B8%B9%CE%BC%B1%B1%B3%BF%F8.JPG
2289 ms
%B4%AB%B2%C9.jpg
2286 ms
IMG_8031.jpg
2292 ms
BDC33.JPG
2293 ms
%BF%EC%B8%B2%BA%CF.%C7%CF%B3%AA%B4%D4%C0%C7%B9%FE.%C0%CC%BA%A5%C6%AE.jpg
2297 ms
image.JPEG
2295 ms
%B8%B8%B9%CE%BC%B1%B1%B3%BF%F8.JPG
2297 ms
BDC33.JPG
2299 ms
%BF%EC%B8%B2%BA%CF.%C7%CF%B3%AA%B4%D4%C0%C7%B9%FE.%C0%CC%BA%A5%C6%AE.jpg
2305 ms
%B8%DE%C0%CE.jpg
2363 ms
%C7%CF%B3%AA%B4%D4%C0%C7%B9%FE_%BE%C6%BA%EA%B6%F3%C7%D4.jpg
2368 ms
%B8%DE%C0%CE%2B.jpg
2386 ms
%B8%B8%B9%CE%C1%DF%BE%D3%B1%B3%C8%B8.%B1%C7%BC%F8%C8%F1%C1%FD%BB%E7.jpg
2554 ms
title.jpg
2719 ms
%B8%B8%B9%CE.%C1%F8%C1%D6%C1%DF%C3%A2%B4%DC.%B9%DA%BC%F8%BF%C1%B1%C7%BB%E7.jpg
2798 ms
%BF%AC%BE%EE%B9%AB%BD%D3%B8%BB%C0%CC%B8%B8%B5%E9%B1%E2.jpg
2858 ms
%C0%CC%B0%F8%C1%D6%B8%DE%C0%CE.jpg
2816 ms
ico_help.gif
287 ms
0034_login.png
1012 ms
btn_confirm.gif
1010 ms
btn_cancel.gif
1006 ms
btn_close.gif
1008 ms
btn_thin_close.gif
1009 ms
btn_close8.gif
1009 ms
ico_file.gif
1012 ms
btn_download2.gif
1012 ms
btn_cancel3.gif
1009 ms
btn_close3.gif
1016 ms
btn_close5.gif
1010 ms
btn_confirm.gif
1015 ms
btn_cancel.gif
1014 ms
btn_close_1.gif
1017 ms
btn_viewexif.gif
1016 ms
btn_originaldn.gif
1018 ms
spc.gif
1015 ms
tit_viewexif.gif
1017 ms
ico_notice2.gif
1018 ms
btn_close.gif
1018 ms
btn_close3.gif
1018 ms
btn_close.gif
1018 ms
btn_ok.gif
1019 ms
btn_close2.gif
1019 ms
btn_confirm_pop2.gif
1019 ms
btn_cancel_pop2.gif
1020 ms
promo_npay.png
876 ms
0153_966.gif
826 ms
btn_blogsearch.gif
819 ms
shadow.png
818 ms
shadow02.png
819 ms
bg_not_available_word.gif
821 ms
0138_head.gif
791 ms
0138_body.gif
787 ms
0138_footer.gif
789 ms
0103_image_1.gif
821 ms
0101_image.gif
789 ms
WidgetListAsync.nhn
1010 ms
m
1331 ms
ExternalWidgetRender.nhn
1570 ms
ExternalWidgetRender.nhn
1572 ms
ExternalWidgetRender.nhn
1575 ms
ExternalWidgetRender.nhn
1601 ms
ExternalWidgetRender.nhn
1607 ms
ExternalWidgetRender.nhn
1613 ms
ExternalWidgetRender.nhn
2219 ms
ExternalWidgetRender.nhn
2234 ms
ExternalWidgetRender.nhn
2169 ms
ExternalWidgetRender.nhn
2212 ms
%B4%EB%BC%BA%C0%FC_%B0%A1%BF%EE%B5%A5%28%C7%C1%B7%CE%C7%CA%BF%EB_wh%29.jpg
943 ms
6018.gif
939 ms
0129_head.gif
930 ms
0129_body.gif
31 ms
0129_icon.gif
29 ms
0129_footer.gif
31 ms
getLoginStatus.nhn
1120 ms
%C0%CE%C5%CD%BA%E4%2B.png
958 ms
%C7%D0%BB%FD%2B.png
845 ms
%BB%E7%C1%F8%2B.png
581 ms
%B6%F3%C0%CC%C7%C1%2B.png
633 ms
%B3%EB%C7%CF%BF%EC%2B.png
513 ms
promo_npay_1603.png
8 ms
clickcrD.js
5 ms
0034_menu.png
6 ms
sp_gnb_v10.png
5 ms
m-story.org SEO score
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M-story.org 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 M-story.org 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.
m-story.org
Open Graph description is not detected on the main page of M Story. 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: