7 sec in total
480 ms
5.8 sec
628 ms
Welcome to report.ajinomoto-kenko.com homepage info - get ready to check Report Ajinomoto Kenko best content for Japan right away, or after learning these important things about report.ajinomoto-kenko.com
あなたの悩みを解決!「いきいき健康研究所」へようこそ。健康に関する役立つ情報をお伝えいたします。
Visit report.ajinomoto-kenko.comWe analyzed Report.ajinomoto-kenko.com page load time and found that the first response time was 480 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
report.ajinomoto-kenko.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value4.6 s
34/100
25%
Value6.4 s
41/100
10%
Value950 ms
29/100
30%
Value0
100/100
15%
Value16.9 s
5/100
10%
480 ms
294 ms
27 ms
298 ms
592 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 64% of them (88 requests) were addressed to the original Report.ajinomoto-kenko.com, 7% (10 requests) were made to Google.com and 7% (10 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Report.ajinomoto-kenko.com.
Page size can be reduced by 300.5 kB (30%)
1.0 MB
706.5 kB
In fact, the total size of Report.ajinomoto-kenko.com main page is 1.0 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. 45% of websites need less resources to load. Images take 695.0 kB which makes up the majority of the site volume.
Potential reduce by 38.7 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 38.7 kB or 78% of the original size.
Potential reduce by 78.2 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. Obviously, Report Ajinomoto Kenko needs image optimization as it can save up to 78.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 94.7 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 94.7 kB or 58% of the original size.
Potential reduce by 89.0 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. Report.ajinomoto-kenko.com needs all CSS files to be minified and compressed as it can save up to 89.0 kB or 89% of the original size.
Number of requests can be reduced by 36 (29%)
123
87
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Report Ajinomoto Kenko. 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 as a result speed up the page load time.
report.ajinomoto-kenko.com
480 ms
import.css
294 ms
jquery.min.js
27 ms
jquery.easing.1.3.js
298 ms
jquery.bxslider.js
592 ms
base.css
151 ms
layout.css
608 ms
logo.gif
151 ms
header_title.gif
154 ms
bn01.jpg
446 ms
bn02.jpg
447 ms
bn03.jpg
592 ms
bn04.jpg
596 ms
bn05.jpg
759 ms
bn06.jpg
458 ms
banner_top.gif
594 ms
banner01.jpg
594 ms
banner02.jpg
611 ms
banner_taisou.jpg
740 ms
banner_end.jpg
744 ms
category_list_title.gif
744 ms
category_list_txt.gif
745 ms
suimin_title.gif
762 ms
list_nayami_suimin.gif
902 ms
suimin_ph_nayami.jpg
903 ms
list_kaiketsu_suimin.gif
904 ms
suimin_ph_kaiketsu.gif
904 ms
list_seibun_suimin.gif
924 ms
suimin_ph_seibun.gif
925 ms
list_advice_suimin.gif
1039 ms
himan_title.gif
1038 ms
list_nayami_himan.gif
1040 ms
himan_ph_nayami.jpg
1040 ms
list_kaiketsu_himan.gif
1058 ms
himan_ph_kaiketsu.gif
1065 ms
list_seibun_himan.gif
1187 ms
himan_ph_seibun.gif
1186 ms
list_advice_himan.gif
1183 ms
hie_title.gif
1187 ms
list_nayami_hie.gif
1210 ms
hie_ph_nayami.jpg
1217 ms
list_kaiketsu_hie.gif
1331 ms
hie_ph_kaiketsu.gif
1306 ms
entry.js
745 ms
list_seibun_hie.gif
1196 ms
hie_ph_seibun.gif
1193 ms
list_advice_hie.gif
928 ms
kaze_title.gif
934 ms
list_nayami_kaze.gif
1033 ms
kaze_ph_nayami.jpg
901 ms
list_kaiketsu_kaze.gif
900 ms
kaze_ph_kaiketsu.gif
899 ms
list_seibun_kaze.gif
932 ms
kaze_ph_seibun.gif
921 ms
list_advice_kaze.gif
902 ms
hatsuiku_title.gif
895 ms
list_nayami_hatsuiku.gif
897 ms
hatsuiku_ph_nayami.jpg
898 ms
list_kaiketsu_hatsuiku.gif
924 ms
hatsuiku_ph_kaiketsu.gif
922 ms
actag
540 ms
DIGITALICE_REC.js
485 ms
tag.js
34 ms
list_seibun_hatsuiku.gif
884 ms
hatsuiku_ph_seibun.gif
885 ms
ashikoshi_title.gif
883 ms
tag
7 ms
list_nayami_ashikoshi.gif
865 ms
ashikoshi_ph_nayami.jpg
909 ms
list_kaiketsu_ashikoshi.gif
913 ms
ashikoshi_ph_kaiketsu.gif
895 ms
list_seibun_ashikoshi.gif
895 ms
ashikoshi_ph_seibun.gif
895 ms
list_advice_ashikoshi.gif
895 ms
container_top_bg.jpg
928 ms
header_bg.png
924 ms
gnav.png
895 ms
gnav_sub.png
1040 ms
carousel_top_bg.png
895 ms
section_bg.png
894 ms
category_nav.gif
926 ms
suimin_arrow_bg.gif
922 ms
advice_ph_suimin.jpg
899 ms
himan_arrow_bg.gif
895 ms
advice_ph_himan.jpg
894 ms
hie_arrow_bg.gif
952 ms
336 ms
advice_ph_hie.jpg
930 ms
kaze_arrow_bg.gif
1003 ms
advice_ph_kaze.jpg
895 ms
hatsuiku_arrow_bg.gif
895 ms
ashikoshi_arrow_bg.gif
894 ms
advice_ph_ashikoshi.jpg
955 ms
prev.png
929 ms
next.png
999 ms
48f42f3bc0c3e47b_315.js
146 ms
ya.js
343 ms
conversion_async.js
63 ms
41 ms
46 ms
dc.js
31 ms
fbds.js
83 ms
rtg.js.php
315 ms
rep
304 ms
__utm.gif
12 ms
94 ms
pb.js
558 ms
351 ms
combo
156 ms
visit.js
257 ms
pb.html
30 ms
pixel
21 ms
309 ms
610 ms
156 ms
v
618 ms
r.js
89 ms
150 ms
tag
5 ms
24 ms
52 ms
27 ms
46 ms
33 ms
33 ms
45 ms
39 ms
34 ms
27 ms
33 ms
27 ms
26 ms
42 ms
18 ms
48 ms
28 ms
16 ms
report.ajinomoto-kenko.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
report.ajinomoto-kenko.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
report.ajinomoto-kenko.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Report.ajinomoto-kenko.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Report.ajinomoto-kenko.com 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.
report.ajinomoto-kenko.com
Open Graph description is not detected on the main page of Report Ajinomoto Kenko. 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: