6.9 sec in total
956 ms
5.7 sec
273 ms
Click here to check amazing Innolife content for South Korea. Otherwise, check out these important facts you probably never knew about innolife.net
韓国情報発信基地!innolife.net
Visit innolife.netWe analyzed Innolife.net page load time and found that the first response time was 956 ms and then it took 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.
innolife.net performance score
956 ms
468 ms
462 ms
62 ms
514 ms
Our browser made a total of 207 requests to load all elements on the main page. We found that 25% of them (51 requests) were addressed to the original Innolife.net, 12% (25 requests) were made to S1.2mdn.net and 8% (17 requests) were made to Contents.innolife.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Innolife.net.
Page size can be reduced by 1.1 MB (35%)
3.2 MB
2.1 MB
In fact, the total size of Innolife.net main page is 3.2 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 49.1 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. 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 49.1 kB or 79% of the original size.
Potential reduce by 57.8 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. Innolife images are well optimized though.
Potential reduce by 445.2 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 445.2 kB or 60% of the original size.
Potential reduce by 564.5 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. Innolife.net needs all CSS files to be minified and compressed as it can save up to 564.5 kB or 87% of the original size.
Number of requests can be reduced by 108 (53%)
202
94
The browser has sent 202 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Innolife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
innolife.net
956 ms
default150903.css
468 ms
topmenu1065_index.js
462 ms
show_ads.js
62 ms
yads.js
514 ms
adsbygoogle.js
53 ms
analytics.js
48 ms
214517_m.jpg
711 ms
index_nw.png
535 ms
8498_0.jpg
670 ms
16937.jpg
519 ms
3057.png
515 ms
more.png
528 ms
index_tr.png
541 ms
index_re.png
542 ms
3.jpg
529 ms
6.jpg
549 ms
7.jpg
758 ms
20.jpg
757 ms
45.jpg
808 ms
44.jpg
809 ms
10.jpg
809 ms
14.jpg
808 ms
29.jpg
1173 ms
line40.png
1196 ms
214519_m.jpg
704 ms
4.gif
502 ms
p_icon.gif
516 ms
7.gif
504 ms
14856_r.jpg
521 ms
14828_r.jpg
722 ms
14895_r.jpg
1166 ms
14855_r.jpg
802 ms
14857_r.jpg
803 ms
14867_r.jpg
1009 ms
14888_r.jpg
1008 ms
14859_r.jpg
1015 ms
14863_r.jpg
1162 ms
news_search.gif
1162 ms
3058.png
510 ms
3056.png
510 ms
3059.png
502 ms
3060.png
497 ms
3081.gif
514 ms
3082.gif
1160 ms
n0.gif
271 ms
n1.gif
266 ms
n2.gif
270 ms
n3.gif
490 ms
n4.gif
493 ms
n5.gif
489 ms
n6.gif
495 ms
n7.gif
495 ms
n8.gif
503 ms
n9.gif
738 ms
n_bottom.jpg
709 ms
co_66cc33.gif
730 ms
co_spacer.gif
709 ms
inews24.gif
710 ms
kita.gif
739 ms
newsis.gif
1003 ms
netallica.png
1154 ms
top_01.gif
1145 ms
top_02.gif
2606 ms
top_03.gif
1696 ms
top_04.gif
1931 ms
top_05.gif
1378 ms
top_06.gif
1377 ms
top_07.gif
1377 ms
top_08.gif
1676 ms
top_09.gif
1675 ms
top_10.gif
1674 ms
top_11.gif
1870 ms
top_12.gif
1869 ms
top_13.gif
1871 ms
top_14.gif
1901 ms
ca-pub-0339856795432340.js
143 ms
zrt_lookup.html
137 ms
show_ads_impl.js
69 ms
collect
37 ms
ajs.php
677 ms
ads
248 ms
osd.js
88 ms
207 ms
adj
175 ms
beacon
163 ms
68 ms
0
95 ms
surly.js
280 ms
dvbs_src.js
141 ms
verify_selector.js
506 ms
blank.gif
480 ms
nnews_i_0.gif
442 ms
hotkeyword.jpg
442 ms
lg.php
1003 ms
n_top.jpg
390 ms
n_left.jpg
392 ms
n_right.jpg
392 ms
ajs.php
136 ms
bst2tv3.html
379 ms
verify.js
367 ms
ba.html
236 ms
pixel
256 ms
4.gif
278 ms
lg.php
272 ms
lidar.js
229 ms
sbhK2lTE.js
298 ms
ajs.php
265 ms
pixel
209 ms
pixel
210 ms
4311.js
131 ms
lg.php
31 ms
ajs.php
234 ms
cTrvNaRi.html
35 ms
click%253Fd%253DAPEucNVFXxpy0n5D61LKpkboIDQhvkEBbBjdqf9BG_Z_hH2vwLhc2q7QA6ZHqGbuWktvYmMTtmbB7S5Zcs3MGuQGtF9zpc9L3A%2526r1%253D;ord=1460118691;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=
171 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
49 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
260 ms
dvtp_src.js
67 ms
98907fdbb447a8be2daf36b8aa81bb4e.jpg
712 ms
lg.php
296 ms
ads
257 ms
yads_vimps-1.4.1.js
1029 ms
tag
591 ms
sd
26 ms
dvtp_src_internal28.js
103 ms
t2tv7.html
102 ms
visit.js
230 ms
index.html
235 ms
adition.js
796 ms
js
462 ms
adj
84 ms
beacon
66 ms
verifyr.js
71 ms
beacon.js
86 ms
0
35 ms
bg.png
55 ms
adchoices.en.png
122 ms
event.gif
110 ms
avs587.js
60 ms
event.gif
122 ms
CSSPlugin.min.js
106 ms
EasePack.min.js
118 ms
TweenLite.min.js
133 ms
TimelineLite.min.js
151 ms
EBLoader.js
30 ms
script.js
71 ms
main.css
78 ms
main.js
77 ms
event.jpg
61 ms
EBLoader.js
141 ms
end.jpg
53 ms
11.png
44 ms
cta.png
44 ms
10.jpg
58 ms
wear.png
56 ms
moisture.png
50 ms
comfort.png
56 ms
colour.png
62 ms
6.png
63 ms
5c.png
66 ms
5b.png
68 ms
5.png
65 ms
4.jpg
65 ms
revolution.png
74 ms
lipstick.png
82 ms
logo.png
86 ms
1b.jpg
84 ms
1a.jpg
123 ms
ready.png
85 ms
are-you.png
123 ms
yads-iframe.html
218 ms
banner
128 ms
ajs.php
40 ms
uid.html
119 ms
lg.php
59 ms
ads
254 ms
box_19_top-right.png
44 ms
ci.png
36 ms
WM_300x600.html
894 ms
surly.js
66 ms
activeview
30 ms
pixel
26 ms
tag
700 ms
pixel
47 ms
scream_V3_photo_url.css
49 ms
scream_V3_photo_url.js
91 ms
layout_engine.js
119 ms
abg.js
119 ms
googlelogo_color_112x36dp.png
77 ms
2249325085399409806
56 ms
s
38 ms
x_button_blue2.png
35 ms
push
39 ms
oi
456 ms
Pix-1x1.gif
47 ms
pixel
25 ms
css.css
327 ms
easeljs-0.7.1.min.js
63 ms
tweenjs-0.5.1.min.js
64 ms
movieclip-0.7.1.min.js
65 ms
preloadjs-0.4.1.min.js
62 ms
WM_300x600_v001.js
866 ms
activeview
23 ms
activeview
27 ms
QC_300_250.jpg
763 ms
_300x600.jpg
237 ms
ui
42 ms
innolife.net SEO score
EN
N/A
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Innolife.net can be misinterpreted by Google and other search engines. Our service has detected that English 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 Innolife.net main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
innolife.net
Open Graph description is not detected on the main page of Innolife. 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: