6.2 sec in total
915 ms
5 sec
298 ms
Visit boohungcapital.com now to see the best up-to-date Boohungcapital content and also check out these interesting facts you probably never knew about boohungcapital.com
Visit boohungcapital.comWe analyzed Boohungcapital.com page load time and found that the first response time was 915 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
boohungcapital.com performance score
915 ms
221 ms
18 ms
290 ms
219 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Boohungcapital.com, 36% (46 requests) were made to Blogimgs.naver.net and 14% (18 requests) were made to Blogimgs.naver.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Blogfiles11.naver.net.
Page size can be reduced by 1.2 MB (66%)
1.8 MB
618.6 kB
In fact, the total size of Boohungcapital.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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 389 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 389 B or 45% of the original size.
Potential reduce by 35.7 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, Boohungcapital needs image optimization as it can save up to 35.7 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 930.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 930.6 kB or 74% of the original size.
Potential reduce by 261.2 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. Boohungcapital.com needs all CSS files to be minified and compressed as it can save up to 261.2 kB or 84% of the original size.
Number of requests can be reduced by 82 (65%)
126
44
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Boohungcapital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
boohungcapital.com
915 ms
boohung114
221 ms
Frameset-981964519.js
18 ms
PostList.nhn
290 ms
NBlogHidden.nhn
219 ms
Hidden-597428542.js
3 ms
MusicPlayer-449972894.js
12 ms
LayoutTopCommon-484882993.css
11 ms
player-846d457.css
19 ms
RemoveSubDomain-dea9950.js
20 ms
Jindo152-363950062.js
21 ms
LayoutTopCommon-730083628.js
32 ms
JindoComponent-318925938.js
31 ms
PostList-1027637939.css
30 ms
gnb_quirks_euckr.nhn
82 ms
likeit_blog.css
72 ms
likeit.css
71 ms
SeViewerBlog-165931490.css
67 ms
PostTopCommon-327917359.js
67 ms
splugin.js
71 ms
PostBottomCommon-1023812380.js
66 ms
PostBottomCommon_utf8-169531666.js
66 ms
likeIt.list.js
69 ms
allowSwfForChrome-7dd9772.js
65 ms
LayoutBottomCommon-902441421.js
66 ms
buhung006.jpg
2175 ms
spc.gif
119 ms
PostList.nhn
287 ms
%BA%CE%C8%EF%BA%ED%B7%CE%B1%D7%281%29.jpg
1153 ms
btn_confirm2.gif
129 ms
%EA%B8%88%EC%9C%B5%EB%8B%AC%EC%9D%B8%EC%BA%90%EB%A6%AD%ED%84%B002.jpg
183 ms
0000_login.png
117 ms
ico_n.gif
116 ms
btn_qk_set.gif
117 ms
btn_what2.gif
118 ms
btn_clse_ly2.gif
117 ms
spc.gif
119 ms
btn_urlcopy.gif
121 ms
btn_confirm.gif
121 ms
btn_cancel.gif
123 ms
btn_close.gif
120 ms
btn_thin_close.gif
120 ms
btn_close8.gif
122 ms
ico_file.gif
124 ms
btn_download2.gif
124 ms
btn_cancel3.gif
124 ms
btn_close3.gif
124 ms
btn_close5.gif
124 ms
btn_confirm.gif
125 ms
btn_cancel.gif
172 ms
btn_close_1.gif
170 ms
btn_viewexif.gif
173 ms
btn_originaldn.gif
171 ms
tit_viewexif.gif
168 ms
ico_notice2.gif
172 ms
btn_close.gif
173 ms
btn_close3.gif
173 ms
btn_close.gif
175 ms
btn_ok.gif
174 ms
btn_close2.gif
174 ms
btn_confirm_pop2.gif
175 ms
btn_cancel_pop2.gif
175 ms
ico_help.gif
122 ms
promo_npay.png
153 ms
0008_ico1_down.gif
141 ms
AdPostInjectAsync.nhn
381 ms
WidgetListAsync.nhn
395 ms
bg_qk_ly2.gif
76 ms
sp_post_btn.png
75 ms
btn_blogsearch.gif
76 ms
shadow.png
76 ms
ico_tag.gif
75 ms
sp_arr1.gif
77 ms
bg_likeit2.gif
77 ms
sp_likeit_pc3.png
76 ms
lg_photoviewer.gif
76 ms
btn_left.gif
77 ms
btn_right.gif
77 ms
btn_original2.png
77 ms
btn_close.gif
77 ms
0121_image.gif
78 ms
0503_head.gif
80 ms
0503_body.gif
79 ms
0503_footer.gif
78 ms
0113_back.gif
252 ms
0112_image.gif
79 ms
shadow02.png
73 ms
bg_not_available_word.gif
73 ms
ico_nidlogin.png
13 ms
adpost_logo.png
13 ms
%B1%DD%C0%B6%B4%DE%C0%CE%C4%B3%B8%AF%C5%CD02.jpg
634 ms
0145_head.gif
630 ms
btn_rst_clse.gif
627 ms
0145_body.gif
46 ms
0145_icon.gif
89 ms
0145_footer.gif
46 ms
0003_arw.gif
30 ms
ico_depth2_l.gif
31 ms
ico_f_blank.gif
28 ms
ico_new.gif
28 ms
ico_f_closed_l.gif
30 ms
ico_n_photo.gif
29 ms
ExternalWidgetRender.nhn
795 ms
ExternalWidgetRender.nhn
899 ms
ExternalWidgetRender.nhn
901 ms
ExternalWidgetRender.nhn
930 ms
ExternalWidgetRender.nhn
949 ms
getLoginStatus.nhn
619 ms
1515151.jpg
631 ms
122493824493606.784.356697154.png
230 ms
boohung_copy.jpg
612 ms
%BA%CE%C8%EF%C4%B3%C7%C7%C5%BB%C0%A7%C1%AC.jpg
702 ms
promo_npay_1603.png
4 ms
clickcrD.js
11 ms
0000_menu.png
10 ms
sp_gnb_v10.png
10 ms
122493824493606.784.356697154.png
197 ms
spi_standard_20160222.css
54 ms
BlogTagListInfo.nhn
298 ms
index.html
209 ms
icon_set.gif
53 ms
m
636 ms
likeIt.list.main.js
27 ms
sp_spi_pc.png
24 ms
likeit.css
22 ms
likeit_blog.css
20 ms
likeItServiceContentList.jsonp
201 ms
boohungcapital.com 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 Boohungcapital.com 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 Boohungcapital.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.
boohungcapital.com
Open Graph description is not detected on the main page of Boohungcapital. 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: