6.8 sec in total
694 ms
5.7 sec
416 ms
Welcome to kun-lee.blog.me homepage info - get ready to check Kun Lee Blog best content for United States right away, or after learning these important things about kun-lee.blog.me
Visit kun-lee.blog.meWe analyzed Kun-lee.blog.me page load time and found that the first response time was 694 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kun-lee.blog.me performance score
694 ms
209 ms
8 ms
1306 ms
367 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kun-lee.blog.me, 27% (38 requests) were made to Blogthumb2.naver.net and 23% (32 requests) were made to Blogimgs.naver.net. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.7 MB (40%)
4.3 MB
2.5 MB
In fact, the total size of Kun-lee.blog.me main page is 4.3 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. Images take 2.1 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 44% of the original size.
Potential reduce by 78.6 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. Kun Lee 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. Kun-lee.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 62 (44%)
140
78
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kun Lee 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.
kun-lee.blog.me
694 ms
kun-lee
209 ms
Frameset-981964519.js
8 ms
PrologueList.nhn
1306 ms
NBlogHidden.nhn
367 ms
Hidden-597428542.js
6 ms
MusicPlayer-449972894.js
16 ms
LayoutTopCommon-484882993.css
11 ms
player-846d457.css
17 ms
RemoveSubDomain-dea9950.js
18 ms
Jindo152-363950062.js
19 ms
LayoutTopCommon-730083628.js
25 ms
JindoComponent-318925938.js
28 ms
PrologueWebzine-71207160.css
35 ms
gnb_quirks_euckr.nhn
60 ms
allowSwfForChrome-7dd9772.js
54 ms
%C5%B8%C0%CC%C6%B2+here+i.jpg
515 ms
spc.gif
129 ms
1007_login.png
142 ms
1455875250634.jpeg
477 ms
btn_confirm2.gif
125 ms
KakaoTalk_20160120_225213537.jpg
147 ms
ico_n.gif
128 ms
btn_thin_close.gif
126 ms
btn_close8.gif
127 ms
ico_file.gif
129 ms
btn_download2.gif
129 ms
btn_cancel3.gif
128 ms
btn_close3.gif
129 ms
btn_close5.gif
129 ms
btn_confirm.gif
131 ms
btn_cancel.gif
131 ms
btn_close_1.gif
130 ms
btn_viewexif.gif
130 ms
btn_originaldn.gif
131 ms
spc.gif
131 ms
tit_viewexif.gif
132 ms
ico_notice2.gif
133 ms
btn_close.gif
132 ms
btn_close3.gif
133 ms
btn_close.gif
134 ms
btn_ok.gif
134 ms
btn_close2.gif
134 ms
btn_confirm_pop2.gif
135 ms
btn_cancel_pop2.gif
135 ms
btn_close.gif
135 ms
1455859203847.jpeg
474 ms
1455796572740.jpeg
476 ms
1.jpg
470 ms
1231231231.jpg
482 ms
%C0%CE%BF%CE%BD%CC.jpg
533 ms
%BC%D2%C0%CC%C4%B5%B5%E9.jpg
961 ms
%BA%B8%C1%B6%B9%E8%C5%CD%B8%AE.jpg
969 ms
2S%BD%BA%C5%E4%BE%EE.jpg
956 ms
112121212.jpg
1008 ms
%BD%E6%B3%D7%C0%CF2.jpg
1033 ms
11111.jpg
1108 ms
%BD%E6%B3%D7%C0%CF2.jpg
1403 ms
00000.jpg
1461 ms
%B5%F0%B9%D9%B5%A5%B9%D9_%BE%C6%C0%CC%BC%BC%B7%B3.jpg
1564 ms
%BE%E7%B9%E8%C3%DF%C1%F3.jpg
1556 ms
%BD%E6%B3%D7%C0%CF2.jpg
1492 ms
%B4%EB%B5%B5%B1%E8%C4%A1.jpg
1698 ms
1.jpg
1889 ms
%BD%BA%C0%AD%C6%D1%C5%E4%B8%AE.jpg
1972 ms
%BD%E6%B3%D7%C0%CF2.jpg
2108 ms
00000.jpg
2045 ms
%B5%B9%B1%E8%BC%B1%B9%B0%BC%BC%C6%AE_%C0%FC%B6%F3%B5%B5%B1%E8_%B9%AB%BE%C8%BC%F6%BB%EA_%281%29.jpg
2041 ms
11111.jpg
2195 ms
000.jpg
2397 ms
000%BF%A9%C1%D6%C8%AF.jpg
2540 ms
%BA%EA%B7%CE%C4%DD%B8%AE%BC%B6%B3%D7%C0%CF.jpg
2579 ms
00.jpg
2577 ms
00.jpg
2663 ms
%B0%DF%B0%FA%B7%F9_%C6%C4%BD%BA%C5%B8%C4%A1%BF%C0_%C7%CF%B7%E7%B0%DF%B0%FA_%2815%29.jpg
2672 ms
20160317_091736.jpg
2830 ms
Screenshot_2016-03-18-08-47-29_edit.jpg
3073 ms
1458281134694.jpeg
3037 ms
20160317_123720.jpg
3078 ms
1458134635131.jpeg
3147 ms
20160315_170304.jpg
3215 ms
promo_npay.png
117 ms
WidgetView.nhn
327 ms
blog2.nhn
460 ms
btn_blogsearch.gif
83 ms
shadow.png
84 ms
shadow02.png
84 ms
bg_not_available_word.gif
83 ms
0111_back1.gif
82 ms
0111_back3.gif
84 ms
0111_back7.gif
84 ms
0111_back9.gif
84 ms
0103_image_1.gif
85 ms
0101_image.gif
85 ms
ico_help.gif
202 ms
LayoutBottomCommon-902441421.js
6 ms
WidgetListAsync.nhn
412 ms
m
404 ms
section_connect_widget-2fd595e.css
3 ms
jindo.min-78c07e0.js
7 ms
agent.ie11-6694cec.js
15 ms
BuddyConnectWidget-242001126.js
15 ms
bg_skin3_2.gif
17 ms
b.gif
16 ms
%B0%A1%C0%BB.jpg
71 ms
KakaoTalk_20160222_190908813.jpg
80 ms
KakaoTalk_20160126_130830418.jpg
404 ms
%BD%C5%B3%E23.jpg
75 ms
profileImage.jpg
77 ms
logo.png
77 ms
profileimage.jpg
98 ms
croppedImage_VERSION2.jpg
111 ms
%B7%AF%BA%EA%B7%B9%C5%CD.jpg
81 ms
book_main2.jpg
114 ms
TG8A2002%2B%25BB%25E7%25BA%25BB.jpg
103 ms
%B3%BB%BB%E7%C1%F81-1249-ljk2109.jpg
94 ms
b.gif
3 ms
ico_arr2.gif
4 ms
btn_skin3_addn_2.gif
5 ms
btn_skin3_admin.png
5 ms
btn_skin3_download.png
4 ms
btn_skin3_help.png
5 ms
1457954791365.jpeg
2871 ms
1457954729116.jpeg
3109 ms
sp_postwidget_150409.png
15 ms
IjSvxqzG4cc8fan8KHAYXZ9om1kQ.jpg
127 ms
post_base.js
33 ms
jindo_component.js
29 ms
mug.pubcenter.postWidget.js
14 ms
5250.gif
42 ms
0148_icon.gif
15 ms
KakaoTalk_20160120_225213537.jpg
66 ms
ExternalWidgetRender.nhn
590 ms
ExternalWidgetRender.nhn
672 ms
%C0%CE%BD%BA%C5%B8%C0%A7%C1%AC.jpg
56 ms
333333333.jpg
52 ms
getLoginStatus.nhn
480 ms
promo_npay_1603.png
5 ms
clickcrD.js
8 ms
1007_menu.png
26 ms
sp_gnb_v10.png
6 ms
kun-lee.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 Kun-lee.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 Kun-lee.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.
kun-lee.blog.me
Open Graph description is not detected on the main page of Kun Lee 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: