3.3 sec in total
601 ms
2.6 sec
139 ms
Click here to check amazing Allbran content for Japan. Otherwise, check out these important facts you probably never knew about allbran.jp
腸内環境を改善するシリアル、「ケロッグ オールブラン」がリニューアル!新製品情報やスペシャルコンテンツ、キャンペーンなどの情報はこちら。おいしく続けて、「あがれ、腸能力。」
Visit allbran.jpWe analyzed Allbran.jp page load time and found that the first response time was 601 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
allbran.jp performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value22.5 s
0/100
25%
Value11.0 s
6/100
10%
Value1,200 ms
20/100
30%
Value0.476
18/100
15%
Value18.6 s
3/100
10%
601 ms
527 ms
539 ms
27 ms
533 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 83% of them (33 requests) were addressed to the original Allbran.jp, 5% (2 requests) were made to Ds.serving-sys.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Allbran.jp.
Page size can be reduced by 110.0 kB (4%)
2.5 MB
2.4 MB
In fact, the total size of Allbran.jp main page is 2.5 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. 25% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 11.3 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 2.0 kB, which is 13% 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 11.3 kB or 73% of the original size.
Potential reduce by 54.3 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. Allbran images are well optimized though.
Potential reduce by 35.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 35.0 kB or 54% of the original size.
Potential reduce by 9.4 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. Allbran.jp needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 79% of the original size.
Number of requests can be reduced by 15 (38%)
39
24
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Allbran. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.allbran.jp
601 ms
import.css
527 ms
style.css
539 ms
jquery.min.js
27 ms
jquery.coda-slider-2.0.js
533 ms
jquery.easing.1.3.js
536 ms
mmConversionTag.js
7 ms
style.css
110 ms
base.css
116 ms
bg.jpg
228 ms
15.jpg
329 ms
14.jpg
297 ms
17.jpg
366 ms
16.jpg
199 ms
3.jpg
1187 ms
4.jpg
587 ms
topbn1_1.jpg
633 ms
img3_1.jpg
463 ms
t3.jpg
590 ms
img1_1.jpg
595 ms
t1.jpg
678 ms
img2_1.jpg
866 ms
t2.jpg
745 ms
top_banner_faq2.gif
724 ms
btm.png
813 ms
foot_logo.gif
759 ms
ga.js
25 ms
aksb.min.js
23 ms
logo.gif
839 ms
head_l.jpg
823 ms
head.jpg
1237 ms
bg_in.png
916 ms
i1.gif
965 ms
ActivityServer.bs
61 ms
__utm.gif
25 ms
ebAttribution.js
5 ms
left.png
878 ms
right.png
890 ms
o.jpg
916 ms
o2.jpg
1025 ms
allbran.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
allbran.jp 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
allbran.jp SEO score
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 Allbran.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 Allbran.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.
allbran.jp
Open Graph description is not detected on the main page of Allbran. 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: