7.9 sec in total
809 ms
6.7 sec
328 ms
Visit aloe.ne.jp now to see the best up-to-date Aloe content for Japan and also check out these interesting facts you probably never knew about aloe.ne.jp
森永乳業の【森永アロエヨーグルト】公式サイト。商品情報やこだわり、アロエキューブのひみつ、ヒストリーをご紹介。ヨーグルトとアロエの素材の恵みが、カラダにアロエのチカラを与えます。
Visit aloe.ne.jpWe analyzed Aloe.ne.jp page load time and found that the first response time was 809 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
aloe.ne.jp performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value6.3 s
11/100
25%
Value13.5 s
2/100
10%
Value180 ms
92/100
30%
Value0.51
15/100
15%
Value15.7 s
6/100
10%
809 ms
311 ms
968 ms
510 ms
899 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 40% of them (38 requests) were addressed to the original Aloe.ne.jp, 22% (21 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Aloe.ne.jp.
Page size can be reduced by 354.5 kB (18%)
2.0 MB
1.6 MB
In fact, the total size of Aloe.ne.jp main page is 2.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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 14.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 4.5 kB, which is 24% 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 14.6 kB or 77% of the original size.
Potential reduce by 132.6 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. Aloe images are well optimized though.
Potential reduce by 168.6 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 168.6 kB or 59% of the original size.
Potential reduce by 38.7 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. Aloe.ne.jp needs all CSS files to be minified and compressed as it can save up to 38.7 kB or 85% of the original size.
Number of requests can be reduced by 46 (50%)
92
46
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aloe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
aloe.ne.jp
809 ms
style.css
311 ms
jquery.js
968 ms
jquery.easing.1.3.js
510 ms
jquery.cycle.all.js
899 ms
common.js
385 ms
ua.js
633 ms
common.css
560 ms
contents.css
943 ms
aloesterol.css
566 ms
analytics.js
75 ms
tag.js
73 ms
logo_morinaga_01.png
337 ms
logo_aloe.png
503 ms
nav_top_on.png
338 ms
nav_products_off.png
349 ms
nav_about_off.png
393 ms
nav_secret_off.png
391 ms
img_visual_iyashi_1.jpg
1418 ms
img_visual_iyashi_2.jpg
1875 ms
img_visual_iyashi_3.jpg
1411 ms
img_visual_iyashi_4.jpg
1651 ms
img_visual_iyashi_5.jpg
1514 ms
img_visual_iyashi_6.jpg
1426 ms
nav_01_off.png
2224 ms
nav_02_off.png
2200 ms
nav_03_off.png
2377 ms
nav_05_off.png
2160 ms
img_campaign_01_150414.png
3040 ms
ttl_news.png
2727 ms
ttl_facebook.png
2519 ms
img_campaign_02_150701.png
3139 ms
btn_webletter.png
2789 ms
logo_morinaga_02.png
2700 ms
gtm.js
62 ms
all.js
60 ms
fb.html
2874 ms
bg_page.gif
3078 ms
bg_contents.png
4045 ms
bg_slideNav.gif
3107 ms
bg_news.png
3364 ms
bg_facebook.png
3390 ms
widgets.js
133 ms
tag
79 ms
collect
71 ms
ga.js
25 ms
collect
93 ms
collect
58 ms
collect
59 ms
191 ms
button.71000885400e222c3c0eec823f8f93f0.js
134 ms
collect
56 ms
xd_arbiter.php
43 ms
xd_arbiter.php
49 ms
ga-audiences
40 ms
tweet_button.fd774b599f565016d763dd860cb31c79.ja.html
41 ms
jot
90 ms
99 ms
collect
10 ms
collect
8 ms
like_box.php
338 ms
ZGOkkXtw5CU.css
40 ms
CY9MHqPubFR.css
49 ms
zc5SnMeT7nA.css
62 ms
0_DMt8YIdVD.css
53 ms
SRSW8M763HA.js
69 ms
ldIMPsSoKmy.js
85 ms
y97Ig99UVTs.js
64 ms
KHAtULXOQuz.js
64 ms
W4NL_XloU4d.js
98 ms
eACiSk3I2K6.js
63 ms
FOagnU9QnXq.js
66 ms
rR4Qw0p7TFQ.js
105 ms
ULtnh-HfQSw.js
104 ms
6IFzBT9uHU-.js
102 ms
10891625_697373973712324_5666249857742549831_n.jpg
109 ms
558933_187902701326123_994845767_n.jpg
13 ms
12717978_930556540394065_7588954941274000356_n.jpg
119 ms
12961696_930556333727419_8123427303522805533_n.jpg
15 ms
12936526_927590994023953_6821579233059200284_n.jpg
14 ms
10399764_915250185258034_966014120480985706_n.jpg
18 ms
12801553_921167104666342_85135503151393685_n.jpg
17 ms
wL6VQj7Ab77.png
11 ms
1JLnMyDN79z.png
10 ms
gm-8CYVMZ_l.png
7 ms
VXcANLwwL5J.js
19 ms
i8XO-4kv8i7.js
19 ms
ya.js
352 ms
conversion_async.js
31 ms
35 ms
18 ms
like.php
148 ms
3XaI8mzWBSs.js
16 ms
LVx-xkvaJ0b.png
3 ms
pb.js
528 ms
363 ms
aloe.ne.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
aloe.ne.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aloe.ne.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aloe.ne.jp 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 Aloe.ne.jp 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.
aloe.ne.jp
Open Graph description is not detected on the main page of Aloe. 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: