6.6 sec in total
683 ms
4.1 sec
1.8 sec
Welcome to endem.blog.me homepage info - get ready to check Endem Blog best content for United States right away, or after learning these important things about endem.blog.me
Visit endem.blog.meWe analyzed Endem.blog.me page load time and found that the first response time was 683 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
endem.blog.me performance score
683 ms
211 ms
8 ms
353 ms
236 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Endem.blog.me, 28% (43 requests) were made to Blogimgs.naver.net and 17% (27 requests) were made to Blogimgs.naver.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Postfiles13.naver.net.
Page size can be reduced by 1.2 MB (75%)
1.6 MB
391.0 kB
In fact, the total size of Endem.blog.me main page is 1.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. 70% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 398 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 398 B or 45% of the original size.
Potential reduce by 22.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. Obviously, Endem Blog needs image optimization as it can save up to 22.0 kB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 915.4 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 915.4 kB or 74% of the original size.
Potential reduce by 248.3 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. Endem.blog.me needs all CSS files to be minified and compressed as it can save up to 248.3 kB or 85% of the original size.
Number of requests can be reduced by 81 (53%)
153
72
The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Endem Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
endem.blog.me
683 ms
endem
211 ms
Frameset-981964519.js
8 ms
PostList.nhn
353 ms
NBlogHidden.nhn
236 ms
Hidden-597428542.js
4 ms
MusicPlayer-449972894.js
10 ms
LayoutTopCommon-484882993.css
17 ms
player-846d457.css
23 ms
RemoveSubDomain-dea9950.js
23 ms
Jindo152-363950062.js
24 ms
LayoutTopCommon-730083628.js
31 ms
JindoComponent-318925938.js
30 ms
PostList-1027637939.css
43 ms
gnb_quirks_euckr.nhn
92 ms
likeit_blog.css
92 ms
likeit.css
91 ms
SeViewerBlog-165931490.css
87 ms
PostTopCommon-327917359.js
86 ms
splugin.js
85 ms
PostBottomCommon-1023812380.js
82 ms
PostBottomCommon_utf8-169531666.js
83 ms
likeIt.list.js
83 ms
allowSwfForChrome-7dd9772.js
81 ms
LayoutBottomCommon-902441421.js
81 ms
spc.gif
176 ms
560.jpg
1606 ms
3586103-0146914899-gatot.jpg
1126 ms
124795_7.jpg
1775 ms
imagesCADU0Q9Z.jpg
1153 ms
%C4%CB%BD%C5%BE%F3%B4%CF%BD%C3%C0%FD.jpg
1345 ms
b0061465_4e64e5e151105.jpg
1521 ms
c0050489_23132335-1.jpg
1481 ms
IMAG0027.jpg
1456 ms
%B9%D9BB7F1.JPG
1353 ms
%C4%B8%C3%B3.JPG
936 ms
%C0%FC%BF%F8%BB%FD%C8%B0.JPG
1385 ms
%BC%D2%B5%B5.JPG
1137 ms
a0009177_13421254.jpg
1372 ms
%BE%C7%BF%AA%B0%A9.JPG
726 ms
original_15.png
452 ms
3745434191_wtyoslo8_img_2277970781340.jpg
1490 ms
dthumb.phinf.naver.net
617 ms
blank.gif
166 ms
btn_confirm2.gif
165 ms
%EC%8A%A4%EC%A6%88.png
695 ms
%C5%E4%B8%F0%BF%A1.JPG
1353 ms
%BD%C5%BC%B1%C1%B6.JPG
1500 ms
b0051210_54b546b8caf74.jpg
1806 ms
m201304050948107001365124155.jpg
1537 ms
0000_login.png
163 ms
btn_qk_set.gif
163 ms
btn_what2.gif
163 ms
btn_clse_ly2.gif
164 ms
spc.gif
166 ms
icon_mobile_F.gif
163 ms
btn_urlcopy.gif
163 ms
btn_confirm.gif
163 ms
btn_cancel.gif
163 ms
btn_close.gif
163 ms
ico-ccl1-by-nc-sa.gif
164 ms
btn_thin_close.gif
164 ms
btn_close8.gif
163 ms
ico_file.gif
164 ms
btn_download2.gif
163 ms
btn_cancel3.gif
164 ms
btn_close3.gif
162 ms
btn_close5.gif
164 ms
btn_confirm.gif
163 ms
btn_cancel.gif
162 ms
btn_close_1.gif
164 ms
btn_viewexif.gif
163 ms
btn_originaldn.gif
163 ms
tit_viewexif.gif
165 ms
ico_notice2.gif
162 ms
btn_close.gif
163 ms
btn_close3.gif
162 ms
btn_close.gif
163 ms
btn_ok.gif
163 ms
btn_close2.gif
162 ms
btn_confirm_pop2.gif
163 ms
btn_cancel_pop2.gif
162 ms
%C3%B3%B4%DC.JPG
1527 ms
89146e3c71243662d3b8f99ab957b576_xksYU1tD6fXWGjtGahEc.png
2402 ms
414088_4.jpg
1095 ms
%C3%DF%BE%EF%C6%ED.jpg
954 ms
%B9%CC%B7%A1.JPG
960 ms
%C0%FC%BF%F82.JPG
1531 ms
imagesCA0PF6NF.jpg
902 ms
%A4%B7.JPG
1125 ms
%B8%ED%C0%E5%B8%E9.JPG
1363 ms
%C5%B0%BF%E4%BB%E7%C5%E4.JPG
1356 ms
%C3%DF%BE%EF%C6%ED_%BF%E4%BE%E0.jpg
1460 ms
%BD%C3%BD%C5.JPG
1108 ms
AEEqXds.jpg
1853 ms
images.jpg
1667 ms
414095_8.jpg
1605 ms
239374_3.jpg
1428 ms
2audio_rurouni_kenshin_tsuioku_hen_ep01_xvid_ac3-mrgk_avi_001409451_yurakiya.jpg
1516 ms
69574431_3.jpg
976 ms
414095_9.jpg
1338 ms
%BF%A1%B4%CF%BD%C3.jpg
1119 ms
fd0696e81ae003a47db02a9040890af7.jpg
1088 ms
ico_help.gif
158 ms
%BF%A1%B4%CF%BD%C3.jpg
1404 ms
CBw53e9444e25197.png
2181 ms
%BC%D2%C1%F6%B7%CE.jpg
1100 ms
06-minu0907-j2lee73.jpg
1153 ms
1003_966.gif
398 ms
AdPostInjectAsync.nhn
395 ms
WidgetListAsync.nhn
308 ms
bg_qk_ly2.gif
71 ms
sp_post_btn.png
71 ms
spr_blogapp_2014_v1.png
72 ms
promo_npay.png
72 ms
ico_tag.gif
72 ms
sp_arr1.gif
72 ms
bg_likeit2.gif
73 ms
sp_likeit_pc3.png
73 ms
0123_back1.gif
328 ms
0123_back2.gif
328 ms
0123_back3.gif
328 ms
0123_back4.gif
327 ms
0123_back6.gif
327 ms
0123_back7.gif
329 ms
0123_back8.gif
329 ms
0123_back9.gif
328 ms
0123_ico1_down.gif
329 ms
lg_photoviewer.gif
330 ms
btn_left.gif
329 ms
btn_right.gif
329 ms
btn_original2.png
330 ms
btn_close.gif
330 ms
0149_head.gif
330 ms
0149_body.gif
331 ms
0149_footer.gif
330 ms
0101_image.gif
331 ms
0103_image_1.gif
331 ms
btn_blogsearch.gif
28 ms
shadow.png
27 ms
shadow02.png
26 ms
bg_not_available_word.gif
27 ms
1486119.gif
483 ms
btn_rst_clse.gif
22 ms
ico_f_blank.gif
17 ms
0157_head.gif
18 ms
0157_body.gif
21 ms
0157_icon.gif
18 ms
0157_footer.gif
19 ms
0149_arw.gif
17 ms
ico_f_closed_l.gif
18 ms
ico_depth2_l.gif
19 ms
%BD%BA%C1%EE.png
577 ms
adpost_logo.png
15 ms
getLoginStatus.nhn
1279 ms
endem.blog.me 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 Endem.blog.me 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 Endem.blog.me 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.
endem.blog.me
Open Graph description is not detected on the main page of Endem Blog. 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: