5.5 sec in total
603 ms
3.4 sec
1.6 sec
Visit hogirl.kr now to see the best up-to-date Hogirl content and also check out these interesting facts you probably never knew about hogirl.kr
머피의 법칙을 믿는 한 사람의 블로그
Visit hogirl.krWe analyzed Hogirl.kr page load time and found that the first response time was 603 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
hogirl.kr performance score
603 ms
217 ms
8 ms
301 ms
222 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hogirl.kr, 31% (46 requests) were made to Blogimgs.naver.net and 14% (21 requests) were made to T.static.blog.naver.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Postfiles6.naver.net.
Page size can be reduced by 1.3 MB (46%)
2.9 MB
1.5 MB
In fact, the total size of Hogirl.kr main page is 2.9 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.4 MB which makes up the majority of the site volume.
Potential reduce by 434 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 434 B or 44% of the original size.
Potential reduce by 31.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. Hogirl images are well optimized though.
Potential reduce by 1.0 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.0 MB or 74% of the original size.
Potential reduce by 260.9 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. Hogirl.kr needs all CSS files to be minified and compressed as it can save up to 260.9 kB or 85% of the original size.
Number of requests can be reduced by 87 (60%)
146
59
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hogirl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
hogirl.kr
603 ms
enogen83
217 ms
Frameset-981964519.js
8 ms
PostList.nhn
301 ms
NBlogHidden.nhn
222 ms
Hidden-597428542.js
13 ms
MusicPlayer-449972894.js
6 ms
LayoutTopCommon-484882993.css
11 ms
player-846d457.css
21 ms
RemoveSubDomain-dea9950.js
23 ms
Jindo152-363950062.js
30 ms
LayoutTopCommon-730083628.js
24 ms
JindoComponent-318925938.js
28 ms
PostList-1027637939.css
28 ms
gnb_quirks_euckr.nhn
88 ms
likeit_blog.css
82 ms
likeit.css
81 ms
SeViewerBlog-165931490.css
25 ms
PostTopCommon-327917359.js
78 ms
splugin.js
138 ms
PostBottomCommon-1023812380.js
75 ms
PostBottomCommon_utf8-169531666.js
77 ms
likeIt.list.js
78 ms
allowSwfForChrome-7dd9772.js
75 ms
LayoutBottomCommon-902441421.js
75 ms
bg.jpg
781 ms
bg.jpg
742 ms
spc.gif
140 ms
PostList.nhn
305 ms
original_9.png
260 ms
IMG_0910.jpg
1454 ms
IMG_0913.jpg
1431 ms
IMG_0917.jpg
940 ms
DSC07270.jpg
747 ms
DSC07274.jpg
1471 ms
DSC07276.jpg
1186 ms
DSC07277.jpg
1869 ms
DSC07279.jpg
213 ms
DSC07282.jpg
1355 ms
DSC07286.jpg
1009 ms
btn_confirm2.gif
141 ms
%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%83%B7%202015-11-04%20%EC%98%A4%EC%A0%84%201.37.58.png
192 ms
0025_login.png
134 ms
ico_n.gif
135 ms
btn_qk_set.gif
135 ms
btn_what2.gif
134 ms
btn_clse_ly2.gif
133 ms
spc.gif
134 ms
btn_urlcopy.gif
134 ms
ico_new.gif
136 ms
btn_confirm.gif
135 ms
btn_cancel.gif
135 ms
btn_close.gif
135 ms
btn_thin_close.gif
136 ms
btn_close8.gif
136 ms
ico_file.gif
138 ms
btn_download2.gif
139 ms
btn_cancel3.gif
138 ms
btn_close3.gif
137 ms
btn_close5.gif
136 ms
btn_confirm.gif
135 ms
btn_cancel.gif
136 ms
btn_close_1.gif
136 ms
btn_viewexif.gif
138 ms
btn_originaldn.gif
137 ms
tit_viewexif.gif
138 ms
ico_notice2.gif
137 ms
btn_close.gif
138 ms
btn_close3.gif
138 ms
btn_close.gif
178 ms
btn_ok.gif
178 ms
btn_close2.gif
177 ms
btn_confirm_pop2.gif
178 ms
btn_cancel_pop2.gif
178 ms
original_14.png
233 ms
original_2.png
243 ms
DSC07266.jpg
1365 ms
DSC07283.jpg
1797 ms
ico_help.gif
132 ms
post-.jpg
480 ms
promo_npay.png
147 ms
blog-skin.gif
144 ms
0156_966.gif
141 ms
WidgetView.nhn
481 ms
bg_qk_ly2.gif
118 ms
sp_post_btn.png
118 ms
ico_tag.gif
117 ms
sp_arr1.gif
120 ms
bg_likeit2.gif
118 ms
sp_likeit_pc3.png
118 ms
0133_ico1_down.gif
119 ms
AdPostInjectAsync.nhn
398 ms
WidgetListAsync.nhn
408 ms
btn_blogsearch.gif
67 ms
lg_photoviewer.gif
66 ms
btn_left.gif
66 ms
btn_right.gif
67 ms
btn_original2.png
67 ms
btn_close.gif
68 ms
0157_back.gif
69 ms
0102_image.gif
69 ms
shadow.png
66 ms
shadow02.png
67 ms
bg_not_available_word.gif
67 ms
adpost_logo.png
13 ms
section_connect_widget2-413879d.css
144 ms
jindo.min-78c07e0.js
148 ms
agent.ie11-6694cec.js
154 ms
BuddyConnectWidget-242001126.js
154 ms
BuddyConnectBriefWidget-898830988.js
152 ms
%BD%BA%C5%A9%B8%B0%BC%A6+2015-11-04+%BF%C0%C0%FC+1.37.58.png
687 ms
2417245.gif
166 ms
0002_icon.gif
163 ms
btn_rst_clse.gif
163 ms
ico_f_blank.gif
31 ms
ico_n_photo.gif
31 ms
ico_f_closed_l.gif
221 ms
0002_arw.gif
31 ms
ico_depth2_l.gif
31 ms
ico_arr2.gif
15 ms
b.gif
15 ms
line_skin20_v.gif
17 ms
ico_skin22_arr.gif
17 ms
ico_up.gif
16 ms
btn_skin20_pgn.gif
17 ms
btn_skin22_add_2.png
16 ms
btn_skin20_adm_2.png
17 ms
btn_skin20_dnld_2.png
18 ms
profileimage.jpg
494 ms
profileimage.jpg
36 ms
profileImage.jpg
50 ms
Screenshot_2016-02-21-14-09-12.png
36 ms
KakaoTalk_20151201_190940306.jpg
32 ms
ssddffgg.gif
64 ms
DSC_0393.jpg
77 ms
%25C7%25C1%25B7%25CE%25C7%25CA.jpg
165 ms
profileImage.jpg
85 ms
profileImage.jpg
92 ms
Bandphoto_2014_07_18_11_42_43.jpg
127 ms
%C0%CC%B9%CC%C1%F6+1.jpg
152 ms
IMG_8474.PNG
564 ms
IMG_6642.jpg
162 ms
IMG_5604.jpg
197 ms
%C5%D7%C0%CC%BA%ED%B9%D9%C5%C1.png
670 ms
ExternalWidgetRender.nhn
1259 ms
getLoginStatus.nhn
614 ms
170x407.png
60 ms
hogirl.kr SEO score
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hogirl.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hogirl.kr 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.
hogirl.kr
Open Graph description is not detected on the main page of Hogirl. 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: