12.7 sec in total
1.5 sec
10.8 sec
367 ms
Welcome to h21blog.hani.co.kr homepage info - get ready to check H 21 Blog Hani best content for South Korea right away, or after learning these important things about h21blog.hani.co.kr
Visit h21blog.hani.co.krWe analyzed H21blog.hani.co.kr page load time and found that the first response time was 1.5 sec and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
h21blog.hani.co.kr performance score
1493 ms
242 ms
488 ms
769 ms
460 ms
Our browser made a total of 198 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original H21blog.hani.co.kr, 30% (59 requests) were made to Img.hani.co.kr and 14% (28 requests) were made to S1.2mdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Adtg.widerplanet.com.
Page size can be reduced by 899.8 kB (38%)
2.4 MB
1.5 MB
In fact, the total size of H21blog.hani.co.kr main page is 2.4 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. 85% 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 90.6 kB
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. This page needs HTML code to be minified as it can gain 12.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 90.6 kB or 79% of the original size.
Potential reduce by 37.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. H 21 Blog Hani images are well optimized though.
Potential reduce by 597.5 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 597.5 kB or 66% of the original size.
Potential reduce by 174.6 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. H21blog.hani.co.kr needs all CSS files to be minified and compressed as it can save up to 174.6 kB or 81% of the original size.
Number of requests can be reduced by 118 (62%)
189
71
The browser has sent 189 CSS, Javascripts, AJAX and image requests in order to completely render the main page of H 21 Blog Hani. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
h21blog.hani.co.kr
1493 ms
section.css
242 ms
jquery.1.9.1.js
488 ms
google_analytics.js
769 ms
common.js
460 ms
dable.js
252 ms
hani_common1.js
251 ms
newsrank_header.js
709 ms
base.css
12 ms
common.css
14 ms
opinion.css
15 ms
cartoon.css
16 ms
esc.css
12 ms
toyo.css
16 ms
graphic.css
16 ms
series.css
15 ms
issue.css
18 ms
gudok.css
17 ms
rest.css
15 ms
search.css
19 ms
photo.css
17 ms
etc.css
19 ms
munhak.css
22 ms
exploration.css
21 ms
bar.css
19 ms
banner.css
21 ms
nanumgothic.css
23 ms
newsrank_right.js
298 ms
newsrank_footer.js
304 ms
acecounter_code.js
7 ms
analytics.js
19 ms
plugin.min.js
463 ms
btn_daily_select_on.gif
256 ms
btn_week_select_off.gif
253 ms
btn_monthly_select_off.gif
251 ms
btn_year_select_off.gif
252 ms
btn_search3.gif
273 ms
icon_bar_1x14.gif
242 ms
icon_close.png
240 ms
line_three.gif
493 ms
logo_hani_sub.png
243 ms
icon_top_menu.png
244 ms
icon_top_login.png
243 ms
bubble_top_aw.png
245 ms
icon_top_search.png
244 ms
section_bg.gif
409 ms
bul_2x7_333.gif
408 ms
bul_2x2_444.gif
690 ms
NanumGothic-Regular.woff
31 ms
NanumGothic-Bold.woff
66 ms
NanumGothic-ExtraBold.woff
67 ms
section@Right1
933 ms
native_ad@Position1
985 ms
section-total.js
243 ms
section@Right2
1004 ms
section@Right3
1055 ms
section@x65
1057 ms
section@x66
1075 ms
section@Bottom1
1397 ms
section@Bottom2
1379 ms
section@BottomRight
1516 ms
icon_top_sns_m1.png
32 ms
icon_top_sns_m2.png
35 ms
prefs
155 ms
visit
154 ms
gCh42zJKQe_1.html
411 ms
1458194045_145819402960_20160318.JPG
239 ms
empty.gif
502 ms
145821146132_20160318.JPG
240 ms
145826479238_20160319.JPG
12 ms
53_1458262023_00553414701_20160318.JPG
463 ms
gpt.js
6 ms
icon_friend.png
231 ms
pubads_impl_82.js
6 ms
9481811.1458284270052
245 ms
ads
62 ms
container.html
26 ms
PelicanC.dll
1381 ms
aclk
51 ms
osd.js
11 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
40 ms
lidar.js
31 ms
ad_300x150.html
24 ms
cssanimation.min.js
4 ms
bg1.jpg
5 ms
t1.png
17 ms
bg2.jpg
16 ms
bg3.jpg
36 ms
t2.png
36 ms
bg4.jpg
38 ms
t3.png
34 ms
ks.png
34 ms
lg.png
37 ms
drl.png
39 ms
logo.png
38 ms
cta.png
38 ms
jquery.min.js
31 ms
ba-postmessage.min.js
157 ms
8000368457_20091221.JPG
244 ms
1330477471_133047737824_20120301.JPG
263 ms
03552215_20060911.JPG
270 ms
1458194045_145819402960_20160318.JPG
484 ms
145821431047_20160318.JPG
241 ms
00474414101_20130709.JPG
465 ms
145801749606_20160315.jpg
698 ms
adplex.js
205 ms
ico_ad.gif
409 ms
activeview
17 ms
NAONMP5330_1.js
656 ms
visit
160 ms
logo-text-tiny.png
179 ms
ck_log.html
394 ms
NAONMP5330N.js
200 ms
NAONMP5330_1.css
397 ms
activeview
14 ms
top_left
620 ms
ajs.php
317 ms
adsbygoogle.js
10 ms
collect
6 ms
collect
54 ms
wjs.php
1869 ms
ca-pub-0061834038389973.js
8 ms
zrt_lookup.html
27 ms
show_ads_impl.js
47 ms
ga-audiences
92 ms
ads
317 ms
jquery-1.8.2.min.js
406 ms
jquery.base64.js
394 ms
adbay.controller.v1.10.js
396 ms
base.css
395 ms
slide.css
396 ms
slide.common.js
397 ms
slide.300x250.controller.js
590 ms
adj
56 ms
beacon
38 ms
click
28 ms
pixel
15 ms
pixel
34 ms
pixel
36 ms
ad_250x250.html
9 ms
setuid
47 ms
cssanimation.min.js
18 ms
bg.jpg
21 ms
t1.png
18 ms
t2.png
19 ms
car.png
15 ms
llanta.png
15 ms
aro.png
19 ms
carlights.png
19 ms
lg.png
20 ms
logo.png
21 ms
model.png
21 ms
blight.png
20 ms
cta.png
21 ms
sd
6 ms
activeview
15 ms
top_left
586 ms
top_left
203 ms
PelicanC.dll
512 ms
criteo_passback@BottomRight
238 ms
show_ads.js
6 ms
ads
228 ms
btn_sitemap.gif
231 ms
sdk.js
25 ms
widgets.js
21 ms
footer_logo.png
24 ms
bul_2x4_222.gif
238 ms
bul_1x10_d6d6d6.gif
259 ms
icon_top_facebook.png
24 ms
icon_top_twitter.png
26 ms
btn_select.gif
265 ms
ebizcode_1.js
63 ms
ebizcode_2.js
62 ms
ebizcode_3.js
70 ms
ajs.php
94 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
47 ms
btn_daily_select_off.gif
276 ms
190 ms
PelicanC.dll
506 ms
xd_arbiter.php
40 ms
xd_arbiter.php
78 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ko.html
30 ms
info.json
88 ms
google_passback@BottomRight
268 ms
jot
84 ms
like.php
285 ms
_n2s_hani_3.js
641 ms
ca-pub-4707036430287544.js
32 ms
ads
28 ms
lg.php
25 ms
osd.js
20 ms
wy1X4hBW7e7.js
34 ms
LVx-xkvaJ0b.png
23 ms
match.aspx
21 ms
_n2s_hani_280_550.html
428 ms
jquery.min.js
4 ms
_n2s_banner_common_v4.js
1781 ms
_n2s_adinfo_common.php
739 ms
h21blog.hani.co.kr SEO score
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise H21blog.hani.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that H21blog.hani.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.
h21blog.hani.co.kr
Open Graph description is not detected on the main page of H 21 Blog Hani. 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: