6.6 sec in total
677 ms
5.3 sec
579 ms
Welcome to tangkong16.blog.me homepage info - get ready to check Tangkong 16 Blog best content for United States right away, or after learning these important things about tangkong16.blog.me
Visit tangkong16.blog.meWe analyzed Tangkong16.blog.me page load time and found that the first response time was 677 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.
tangkong16.blog.me performance score
677 ms
262 ms
5 ms
890 ms
240 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tangkong16.blog.me, 23% (35 requests) were made to Blogimgs.naver.net and 22% (33 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.7 MB (48%)
3.6 MB
1.9 MB
In fact, the total size of Tangkong16.blog.me main page is 3.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. 75% 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.9 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 45% of the original size.
Potential reduce by 89.5 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. Tangkong 16 Blog images are well optimized though.
Potential reduce by 1.4 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.4 MB or 75% of the original size.
Potential reduce by 248.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. Tangkong16.blog.me needs all CSS files to be minified and compressed as it can save up to 248.1 kB or 86% of the original size.
Number of requests can be reduced by 58 (39%)
150
92
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tangkong 16 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 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tangkong16.blog.me
677 ms
tangkong16
262 ms
Frameset-981964519.js
5 ms
PrologueList.nhn
890 ms
NBlogHidden.nhn
240 ms
Hidden-597428542.js
3 ms
MusicPlayer-449972894.js
10 ms
LayoutTopCommon-484882993.css
25 ms
player-846d457.css
36 ms
RemoveSubDomain-dea9950.js
40 ms
Jindo152-363950062.js
41 ms
LayoutTopCommon-730083628.js
51 ms
JindoComponent-318925938.js
59 ms
PrologueWebzine-71207160.css
73 ms
gnb_quirks_euckr.nhn
124 ms
allowSwfForChrome-7dd9772.js
117 ms
LayoutBottomCommon-902441421.js
117 ms
%BF%C3%B8%B2%C7%C8%B0%F8%BF%F8+1.JPG
2199 ms
spc.gif
170 ms
DSC_0008.jpg
845 ms
btn_confirm2.gif
168 ms
sad.jpg
183 ms
IMG_3951.jpg
864 ms
IMG_7577.jpg
841 ms
DSC_0412.jpg
840 ms
IMG_1378.jpg
841 ms
IMG_2607.jpg
842 ms
DSC_9959.jpg
1230 ms
IMG_0851.jpg
972 ms
IMG_2209.jpg
1352 ms
IMG_0647.jpg
1163 ms
IMG_0303.jpg
1409 ms
DSC_9841.jpg
1224 ms
IMG_2575.jpg
1635 ms
20160201220952_IMG_1908.JPG
1819 ms
IMG_1149.jpg
1785 ms
%B4%DC%C3%BC%BB%E7%C1%F81%287%C0%E5%29.jpg
1745 ms
IMG_4292.jpg
1759 ms
IMG_9845.jpg
1982 ms
IMG_2458.jpg
2080 ms
DSC_0917.jpg
2188 ms
img_1454654805674.jpg
2180 ms
IMG_9749.jpg
2284 ms
IMG_1054.jpg
2290 ms
IMG_9776.jpg
2471 ms
IMG_0681.jpg
2522 ms
IMG_3637.jpg
2697 ms
IMG_2996.jpg
2666 ms
IMG_2925.jpg
2772 ms
IMG_6132.jpg
2837 ms
IMG_7397.jpg
3016 ms
20141018-IMG_5173.jpg
3012 ms
20141018-IMG_5430.jpg
3373 ms
IMG_2262.jpg
3159 ms
ico_help.gif
152 ms
1005_login.png
151 ms
btn_thin_close.gif
152 ms
btn_close8.gif
152 ms
ico_file.gif
152 ms
btn_download2.gif
152 ms
btn_cancel3.gif
153 ms
btn_close3.gif
153 ms
btn_close5.gif
153 ms
btn_confirm.gif
154 ms
btn_cancel.gif
154 ms
btn_close_1.gif
154 ms
btn_viewexif.gif
154 ms
btn_originaldn.gif
155 ms
spc.gif
154 ms
tit_viewexif.gif
156 ms
ico_notice2.gif
156 ms
btn_close.gif
156 ms
btn_close3.gif
157 ms
btn_close.gif
155 ms
btn_ok.gif
156 ms
btn_close2.gif
155 ms
btn_confirm_pop2.gif
156 ms
btn_cancel_pop2.gif
156 ms
btn_close.gif
156 ms
promo_npay.png
209 ms
WidgetView.nhn
742 ms
0118_back.gif
167 ms
blog2.nhn
759 ms
WidgetListAsync.nhn
959 ms
btn_blogsearch.gif
110 ms
shadow.png
110 ms
shadow02.png
110 ms
bg_not_available_word.gif
110 ms
0124_image_1.png
112 ms
0104_image_1.gif
110 ms
m
446 ms
section_connect_widget-2fd595e.css
73 ms
jindo.min-78c07e0.js
76 ms
agent.ie11-6694cec.js
85 ms
BuddyConnectWidget-242001126.js
85 ms
sp_postwidget_150409.png
480 ms
mug_obj_20160314005649402.jpg
2438 ms
post_base.js
444 ms
jindo_component.js
476 ms
mug.pubcenter.postWidget.js
442 ms
bg_skin9.gif
40 ms
b.gif
39 ms
login_basic.gif
40 ms
07261.JPG
538 ms
%C6%F7%B8%CB%BA%AF%C8%AF_miles-akoustic.jpg
34 ms
%BF%E4%B8%AE.png
32 ms
2015%2CICELAND_161.png
32 ms
b.gif
26 ms
ico_arr2.gif
26 ms
btn_skin9_addn.gif
28 ms
btn_skin9_admin.png
27 ms
btn_skin9_download.png
28 ms
btn_skin9_help.png
28 ms
ExternalWidgetRender.nhn
677 ms
ExternalWidgetRender.nhn
678 ms
ExternalWidgetRender.nhn
689 ms
ExternalWidgetRender.nhn
690 ms
ExternalWidgetRender.nhn
692 ms
ExternalWidgetRender.nhn
848 ms
ExternalWidgetRender.nhn
1280 ms
ExternalWidgetRender.nhn
1275 ms
ExternalWidgetRender.nhn
1301 ms
ExternalWidgetRender.nhn
1316 ms
ExternalWidgetRender.nhn
1355 ms
ExternalWidgetRender.nhn
1460 ms
ExternalWidgetRender.nhn
1963 ms
1108427.gif
59 ms
0153_head.gif
50 ms
sp_widget_map_v4.png
46 ms
sad.jpg
861 ms
0153_body.gif
34 ms
0153_icon.gif
15 ms
0153_footer.gif
36 ms
bg_country_v3.gif
8 ms
getLoginStatus.nhn
448 ms
170.jpg
1120 ms
%B3%AA%B4%AE%C0%BB%C0%D5%B4%D9_%BF%A5%BA%ED%B7%B3_%C3%D6%C1%BE.jpg
1044 ms
a%A4%A4%A4%B7%A4%B1%A4%A4%A4%B7.jpg
911 ms
a%B1%D7%B8%B22.jpg
959 ms
a%B1%D7%B8%B21.jpg
970 ms
B_blogbanner04.png
703 ms
promo_npay_1603.png
5 ms
clickcrD.js
10 ms
1005_menu.png
5 ms
sp_gnb_v10.png
4 ms
K2_%C0%A7%C1%AC_%BB%E7%BF%EB.png
901 ms
a1111.jpg
672 ms
%B1%D7%B8%B22.jpg
862 ms
%B1%D7%B8%B24.jpg
848 ms
%B1%D7%B8%B23.jpg
999 ms
%C8%FA%C6%D1_%BC%AD%C6%F7%C5%CD%C1%EE_%C0%A7%C1%AC.png
154 ms
tangkong16.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 Tangkong16.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 Tangkong16.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.
tangkong16.blog.me
Open Graph description is not detected on the main page of Tangkong 16 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: