6.6 sec in total
696 ms
5.6 sec
345 ms
Welcome to b_sang.blog.me homepage info - get ready to check B Sang Blog best content for United States right away, or after learning these important things about b_sang.blog.me
Visit b_sang.blog.meWe analyzed B_sang.blog.me page load time and found that the first response time was 696 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.
b_sang.blog.me performance score
696 ms
330 ms
7 ms
678 ms
244 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original B_sang.blog.me, 24% (32 requests) were made to Blogimgs.naver.net and 18% (24 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.1 MB (60%)
1.8 MB
738.7 kB
In fact, the total size of B_sang.blog.me 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 381 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 381 B or 44% of the original size.
Potential reduce by 43.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. B Sang Blog images are well optimized though.
Potential reduce by 844.3 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 844.3 kB or 74% of the original size.
Potential reduce by 212.1 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. B_sang.blog.me needs all CSS files to be minified and compressed as it can save up to 212.1 kB or 85% of the original size.
Number of requests can be reduced by 63 (48%)
130
67
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of B Sang 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 4 to 1 for CSS and as a result speed up the page load time.
b_sang.blog.me
696 ms
b_sang
330 ms
Frameset-981964519.js
7 ms
PrologueList.nhn
678 ms
NBlogHidden.nhn
244 ms
Hidden-597428542.js
7 ms
MusicPlayer-449972894.js
18 ms
LayoutTopCommon-484882993.css
12 ms
player-846d457.css
34 ms
RemoveSubDomain-dea9950.js
36 ms
Jindo152-363950062.js
41 ms
LayoutTopCommon-730083628.js
40 ms
JindoComponent-318925938.js
59 ms
PrologueWebzine-71207160.css
38 ms
gnb_quirks_euckr.nhn
58 ms
allowSwfForChrome-7dd9772.js
52 ms
LayoutBottomCommon-902441421.js
191 ms
0273_head.jpg
652 ms
spc.gif
657 ms
promo_npay.png
626 ms
IMG_5465.jpg
652 ms
WidgetView.nhn
630 ms
btn_confirm2.gif
587 ms
IMG_3837.jpg
613 ms
btn_confirm.gif
572 ms
btn_cancel.gif
569 ms
btn_close.gif
570 ms
btn_blogsearch.gif
572 ms
btn_thin_close.gif
571 ms
btn_close8.gif
575 ms
ico_file.gif
577 ms
btn_download2.gif
574 ms
btn_cancel3.gif
577 ms
btn_close3.gif
573 ms
btn_close5.gif
576 ms
shadow.png
578 ms
shadow02.png
579 ms
btn_confirm.gif
577 ms
btn_cancel.gif
578 ms
btn_close_1.gif
578 ms
btn_viewexif.gif
579 ms
btn_originaldn.gif
582 ms
spc.gif
579 ms
tit_viewexif.gif
580 ms
ico_notice2.gif
582 ms
btn_close.gif
580 ms
bg_not_available_word.gif
579 ms
btn_close3.gif
581 ms
btn_close.gif
582 ms
btn_ok.gif
582 ms
btn_close2.gif
583 ms
btn_confirm_pop2.gif
583 ms
btn_cancel_pop2.gif
584 ms
ico_help.gif
553 ms
IMG_6863.jpg
593 ms
IMG_6373.jpg
591 ms
IMG_9158.jpg
750 ms
IMG_2087.jpg
608 ms
IMG_4529.jpg
637 ms
IMG_4244.jpg
1024 ms
IMG_4033.jpg
1002 ms
IMG_9215.jpg
1245 ms
IMG_8299.jpg
1118 ms
IMG_7385.jpg
1408 ms
IMG_1460.jpg
1297 ms
IMG_6962.jpg
1598 ms
IMG_5175.jpg
1768 ms
IMG_6191.jpg
1611 ms
IMG_9418.jpg
1747 ms
IMG_0866.jpg
1872 ms
IMG_9115.jpg
1944 ms
IMG_9967.jpg
2143 ms
IMG_7571.jpg
2131 ms
IMG_5972.jpg
2538 ms
IMG_6007.jpg
2289 ms
IMG_3563.jpg
2393 ms
IMG_3612.jpg
2500 ms
0021_login.png
544 ms
0138_head.gif
545 ms
0138_body.gif
545 ms
0138_footer.gif
546 ms
0116_image.gif
545 ms
WidgetListAsync.nhn
789 ms
m
426 ms
section_connect_widget2-413879d.css
24 ms
jindo.min-78c07e0.js
25 ms
agent.ie11-6694cec.js
32 ms
BuddyConnectWidget-242001126.js
31 ms
BuddyConnectBriefWidget-898830988.js
42 ms
line_skin20_v.gif
33 ms
DSC_3029.JPG
489 ms
ico_arr2.gif
29 ms
Screenshot_2012-10-15-18-18-48-1.png
471 ms
Re_DSC00051-1.jpg
438 ms
iPhone_5.jpg
491 ms
login_basic.gif
26 ms
n-shine_com_20160315_153131.jpg
36 ms
1111.jpeg
49 ms
%B7%CE%B0%ED.jpg
61 ms
b.gif
27 ms
ico_skin23_arr.gif
74 ms
ico_up.gif
29 ms
btn_skin20_pgn.gif
29 ms
btn_skin23_add_2.png
131 ms
btn_skin20_adm_2.png
43 ms
btn_skin20_dnld_2.png
49 ms
ExternalWidgetRender.nhn
1520 ms
ExternalWidgetRender.nhn
1515 ms
ExternalWidgetRender.nhn
1528 ms
ExternalWidgetRender.nhn
1559 ms
ExternalWidgetRender.nhn
1572 ms
ExternalWidgetRender.nhn
1601 ms
ExternalWidgetRender.nhn
2095 ms
ExternalWidgetRender.nhn
2115 ms
ExternalWidgetRender.nhn
2154 ms
ExternalWidgetRender.nhn
2246 ms
ExternalWidgetRender.nhn
2326 ms
1067598.gif
456 ms
0101_icon.gif
20 ms
IMG_3837.jpg
520 ms
getLoginStatus.nhn
437 ms
promo_npay_1603.png
4 ms
clickcrD.js
4 ms
0021_menu.png
20 ms
sp_gnb_v10.png
3 ms
%B0%A1%C1%B7%BD%BA%B3%C0.jpg
600 ms
%B5%B9%BD%BA%B3%C0.jpg
671 ms
%C7%C1%B7%CE%C7%CA%C3%D4%BF%B5.jpg
702 ms
%BF%FE%B5%F9%BD%BA%B3%C0.jpg
649 ms
cats.jpg
664 ms
cats.jpg
685 ms
b_sang.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 B_sang.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 B_sang.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.
b_sang.blog.me
Open Graph description is not detected on the main page of B Sang 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: