7.9 sec in total
1.5 sec
5.8 sec
608 ms
Click here to check amazing Fcseoulstory content. Otherwise, check out these important facts you probably never knew about fcseoulstory.com
Visit fcseoulstory.comWe analyzed Fcseoulstory.com page load time and found that the first response time was 1.5 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fcseoulstory.com performance score
1465 ms
243 ms
8 ms
404 ms
221 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fcseoulstory.com, 30% (41 requests) were made to Blogimgs.naver.net and 12% (16 requests) were made to T.static.blog.naver.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Postfiles4.naver.net.
Page size can be reduced by 1.6 MB (61%)
2.6 MB
1.0 MB
In fact, the total size of Fcseoulstory.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 420 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 420 B or 46% of the original size.
Potential reduce by 76.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. Obviously, Fcseoulstory needs image optimization as it can save up to 76.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 72% of the original size.
Potential reduce by 463.9 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. Fcseoulstory.com needs all CSS files to be minified and compressed as it can save up to 463.9 kB or 84% of the original size.
Number of requests can be reduced by 90 (67%)
135
45
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fcseoulstory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
fcseoulstory.com
1465 ms
fcseoul_gs
243 ms
Frameset-981964519.js
8 ms
PostList.nhn
404 ms
NBlogHidden.nhn
221 ms
Hidden-597428542.js
4 ms
MusicPlayer-449972894.js
28 ms
LayoutTopCommon-484882993.css
26 ms
player-846d457.css
53 ms
RemoveSubDomain-dea9950.js
57 ms
Jindo152-363950062.js
58 ms
LayoutTopCommon-730083628.js
68 ms
JindoComponent-318925938.js
67 ms
PostList-1027637939.css
78 ms
gnb_quirks_euckr.nhn
164 ms
likeit_blog.css
197 ms
likeit.css
196 ms
SeViewerBlog-165931490.css
157 ms
PostTopCommon-327917359.js
156 ms
splugin.js
258 ms
PostBottomCommon-1023812380.js
152 ms
PostBottomCommon_utf8-169531666.js
152 ms
likeIt.list.js
250 ms
allowSwfForChrome-7dd9772.js
249 ms
LayoutBottomCommon-902441421.js
249 ms
spc.gif
231 ms
12805941_952348998152861_3854539859396866595_n.jpg
1385 ms
12801702_952417174812710_629867242576134832_n.jpg
941 ms
12804834_951964001524694_5134169188208016011_n.jpg
1651 ms
btn_confirm2.gif
208 ms
lunacher_512x512.png
722 ms
ico_help.gif
208 ms
0029_login.png
195 ms
btn_qk_set.gif
196 ms
btn_what2.gif
197 ms
btn_clse_ly2.gif
197 ms
spc.gif
197 ms
btn_urlcopy.gif
198 ms
btn_thin_close.gif
197 ms
btn_close8.gif
198 ms
ico_file.gif
198 ms
btn_download2.gif
198 ms
btn_cancel3.gif
199 ms
btn_close3.gif
199 ms
btn_close5.gif
201 ms
btn_confirm.gif
197 ms
btn_cancel.gif
201 ms
btn_close_1.gif
202 ms
btn_viewexif.gif
197 ms
btn_originaldn.gif
197 ms
tit_viewexif.gif
198 ms
ico_notice2.gif
201 ms
btn_close.gif
201 ms
btn_close3.gif
201 ms
btn_close.gif
199 ms
btn_ok.gif
200 ms
btn_close2.gif
201 ms
btn_confirm_pop2.gif
201 ms
btn_cancel_pop2.gif
202 ms
btn_close.gif
199 ms
promo_npay.png
355 ms
%BC%F6%C1%A42-12717900_941706882550406_6039155515718059934_n+copy.jpg
1328 ms
0134_966.gif
344 ms
bg_qk_ly2.gif
103 ms
sp_post_btn.png
103 ms
ico_tag.gif
271 ms
xYpe8fh9BdQ
170 ms
U7Ih8RsiWcM
173 ms
btn_blogsearch.gif
68 ms
shadow.png
77 ms
shadow02.png
76 ms
bg_not_available_word.gif
76 ms
lg_photoviewer.gif
80 ms
btn_left.gif
78 ms
btn_right.gif
78 ms
btn_original2.png
78 ms
btn_close.gif
78 ms
0102_image.gif
77 ms
WidgetListAsync.nhn
363 ms
www-embed-player-vflfNyN_r.css
78 ms
www-embed-player.js
114 ms
base.js
158 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
138 ms
ad_status.js
135 ms
lunacher_512x512.png
706 ms
0156_head.gif
116 ms
btn_rst_clse.gif
99 ms
ico_f_blank.gif
43 ms
ico_f_closed_l.gif
59 ms
ico_f_open_l.gif
59 ms
0156_body.gif
59 ms
0156_icon.gif
59 ms
0156_footer.gif
58 ms
0002_arw.gif
57 ms
ico_depth2_l.gif
58 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
144 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
145 ms
ExternalWidgetRender.nhn
1515 ms
ExternalWidgetRender.nhn
1517 ms
ExternalWidgetRender.nhn
1521 ms
ExternalWidgetRender.nhn
1555 ms
ExternalWidgetRender.nhn
1558 ms
getLoginStatus.nhn
835 ms
promo_npay_1603.png
3 ms
clickcrD.js
8 ms
0029_menu.png
6 ms
sp_gnb_v10.png
6 ms
spi_standard_20160222.css
68 ms
BlogTagListInfo.nhn
291 ms
index.html
196 ms
icon_set.gif
61 ms
m
508 ms
likeIt.list.main.js
32 ms
sp_spi_pc.png
36 ms
likeit.css
22 ms
likeit_blog.css
23 ms
fc%BC%AD%BF%EF_banner_01.jpg
897 ms
fc%BC%AD%BF%EF_banner_02.jpg
964 ms
fc%BC%AD%BF%EF_banner_03.jpg
968 ms
fc%BC%AD%BF%EF_banner_04.jpg
903 ms
likebox.php
184 ms
kyEKgjk51ZE.css
27 ms
xgj7bXhJNEH.css
29 ms
ZeuPykSxSED.css
43 ms
q68gy-v_YMF.js
59 ms
FJmpeSpHpjS.js
58 ms
0wM5s1Khldu.js
55 ms
1bNoFZUdlYZ.js
57 ms
8415_959876290733465_6247756431170821406_n.png
453 ms
12187664_928020217252406_2639691450263787964_n.png
68 ms
10387558_665221446901313_4098387715218428315_n.jpg
68 ms
944911_468791529993699_4468134938084062913_n.jpg
67 ms
12821435_1738730409691395_2740764720990934435_n.jpg
166 ms
HEyyDkPknAC.png
51 ms
wL6VQj7Ab77.png
51 ms
s7jcwEQH7Sx.png
50 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
7 ms
fcseoulstory.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 Fcseoulstory.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 Fcseoulstory.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.
fcseoulstory.com
Open Graph description is not detected on the main page of Fcseoulstory. 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: