6.4 sec in total
774 ms
5.4 sec
200 ms
Welcome to ohnit.co.kr homepage info - get ready to check Ohnit best content for United States right away, or after learning these important things about ohnit.co.kr
Visit ohnit.co.krWe analyzed Ohnit.co.kr page load time and found that the first response time was 774 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ohnit.co.kr performance score
774 ms
218 ms
9 ms
907 ms
218 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ohnit.co.kr, 24% (33 requests) were made to Blogthumb2.naver.net and 24% (33 requests) were made to Blogimgs.naver.net. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.1 MB (53%)
2.1 MB
1.0 MB
In fact, the total size of Ohnit.co.kr main page is 2.1 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.1 MB which makes up the majority of the site volume.
Potential reduce by 401 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 401 B or 45% of the original size.
Potential reduce by 47.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. Ohnit images are well optimized though.
Potential reduce by 834.0 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 834.0 kB or 74% 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. Ohnit.co.kr 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 66 (47%)
139
73
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ohnit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ohnit.co.kr
774 ms
edenbowl
218 ms
Frameset-981964519.js
9 ms
PrologueList.nhn
907 ms
NBlogHidden.nhn
218 ms
Hidden-597428542.js
5 ms
MusicPlayer-449972894.js
17 ms
LayoutTopCommon-484882993.css
6 ms
player-846d457.css
12 ms
RemoveSubDomain-dea9950.js
11 ms
Jindo152-363950062.js
13 ms
LayoutTopCommon-730083628.js
12 ms
JindoComponent-318925938.js
12 ms
PrologueWebzine-71207160.css
26 ms
gnb_quirks_euckr.nhn
37 ms
0234_body.gif
23 ms
spc.gif
38 ms
0006_login.png
39 ms
promo_npay.png
10 ms
12345.jpg
1006 ms
0117_966.gif
19 ms
0127_back1.gif
62 ms
attachImage_4272005835.jpg
596 ms
%C4%B3%B7%D1%C7%C1%B6%FB.jpg
589 ms
NaverBlog_20160112_165552_00.jpg
551 ms
NaverBlog_20160109_130449_03232323222.jpg
586 ms
NaverBlog_20160106_140141_121212125.jpg
615 ms
attachImage_1265220076.jpg
485 ms
attachImage_215095956.jpeg
1018 ms
attachImage_2263544157.jpeg
2533 ms
attachImage_185257233.jpeg
1085 ms
NaverBlog_20160219_151308_15.jpg
1190 ms
NaverBlog_20160214_180627_18.jpg
1068 ms
NaverBlog_20160212_205729_23.jpg
1184 ms
NaverBlog_20160202_162458_00.jpg
1526 ms
0127_back2.gif
34 ms
0127_back3.gif
35 ms
0127_back4.gif
35 ms
WidgetView.nhn
341 ms
btn_blogsearch.gif
154 ms
btn_confirm2.gif
29 ms
NaverBlog_20150903_165429_1922.jpg
154 ms
allowSwfForChrome-7dd9772.js
23 ms
LayoutBottomCommon-902441421.js
26 ms
btn_thin_close.gif
148 ms
btn_close8.gif
152 ms
ico_file.gif
153 ms
btn_download2.gif
153 ms
btn_cancel3.gif
153 ms
btn_close3.gif
154 ms
btn_close5.gif
154 ms
shadow.png
154 ms
shadow02.png
154 ms
btn_confirm.gif
156 ms
btn_cancel.gif
155 ms
btn_close_1.gif
155 ms
btn_viewexif.gif
155 ms
btn_originaldn.gif
156 ms
spc.gif
156 ms
tit_viewexif.gif
158 ms
ico_notice2.gif
157 ms
btn_close.gif
157 ms
bg_not_available_word.gif
157 ms
btn_close3.gif
158 ms
btn_close.gif
158 ms
btn_ok.gif
158 ms
btn_close2.gif
158 ms
btn_confirm_pop2.gif
158 ms
btn_cancel_pop2.gif
159 ms
btn_close.gif
158 ms
ico_help.gif
139 ms
NaverBlog_20160129_165527_39.jpg
1549 ms
NaverBlog_20160127_170315_01.jpg
1538 ms
NaverBlog_20160118_171811_14.jpg
1828 ms
NaverBlog_20160116_170044_00.jpg
1645 ms
%B9%DF%BB%F6%BA%F1%B1%B3.jpg
2046 ms
NaverBlog_20160106_155004_12.jpg
2005 ms
NaverBlog_20160105_172417_00.jpg
2006 ms
NaverBlog_20160103_144044_04.jpg
2233 ms
NaverBlog_20160103_144041_00.jpg
2426 ms
NaverBlog_20151230_160032_12.jpg
2530 ms
NaverBlog_20151216_183324_14.jpg
2546 ms
NaverBlog_20151208_162835_01.jpg
2599 ms
NaverBlog_20151205_151148_01.jpg
2706 ms
NaverBlog_20151112_162800_12.jpg
2933 ms
NaverBlog_20151104_093203_04.jpg
3057 ms
NaverBlog_20151029_194233_02.jpg
3166 ms
attachImage_3729776207.jpeg
3019 ms
attachImage_2884829166.jpeg
3172 ms
attachImage_352535551.jpeg
3212 ms
attachImage_1067282592.jpeg
3465 ms
0127_back6.gif
136 ms
0127_back7.gif
136 ms
0127_back8_1.gif
138 ms
0127_back9.gif
136 ms
0105_head.gif
149 ms
0105_body.gif
136 ms
0104_image_1.gif
136 ms
0127_image_1.gif
141 ms
0105_footer.gif
144 ms
WidgetListAsync.nhn
372 ms
m
693 ms
section_connect_widget-2fd595e.css
5 ms
jindo.min-78c07e0.js
9 ms
agent.ie11-6694cec.js
13 ms
BuddyConnectWidget-242001126.js
12 ms
bg_skin7.gif
18 ms
b.gif
19 ms
profileImage.jpg
578 ms
4610511157_53995779c9_z.jpg
568 ms
login_basic.gif
5 ms
IMG_9368.jpg
37 ms
20140728_114709.jpg
29 ms
%BD%BD%B6%F3%C0%CC%B5%E53.JPG
524 ms
KakaoTalk_20151112_201337098.jpg
30 ms
20160201_005652.jpg
79 ms
picasso-pablo-don-quixote-9904658.jpg
30 ms
%B5%B7%C5%B0%C8%A3%C5%D7.jpg
35 ms
abs01_IMG_0352-5.jpg
38 ms
2015%2CICELAND_161.png
39 ms
%BB%E7%BA%BB+-img_4115_scpark1214.jpg
40 ms
%C7%C1%B7%CE%C7%CA+%BB%E7%C1%F8_2.jpg
44 ms
b.gif
17 ms
ico_arr2.gif
17 ms
btn_skin7_addn.gif
3 ms
btn_skin9_admin.png
3 ms
btn_skin9_download.png
4 ms
btn_skin9_help.png
4 ms
0153_head.gif
24 ms
NaverBlog_20150903_165429_1922.jpg
498 ms
0153_body.gif
18 ms
0153_icon.gif
17 ms
0153_footer.gif
18 ms
ExternalWidgetRender.nhn
1466 ms
getLoginStatus.nhn
713 ms
%BF%C0%B4%D6_%C0%CE%BD%BA%C5%B8%B1%D7%B7%A5_%BB%E7%C1%F8.jpg
987 ms
promo_npay_1603.png
9 ms
clickcrD.js
7 ms
0006_menu.png
19 ms
sp_gnb_v10.png
3 ms
ohnit.co.kr 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 Ohnit.co.kr 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 Ohnit.co.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.
ohnit.co.kr
Open Graph description is not detected on the main page of Ohnit. 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: