8.5 sec in total
567 ms
7.7 sec
249 ms
Click here to check amazing Healthybank content for Japan. Otherwise, check out these important facts you probably never knew about healthybank.com
ダイエット食品なのに美容液?美容液ダイエットシェイクは痩せてキレイになれるから楽天市場でも大人気!
Visit healthybank.comWe analyzed Healthybank.com page load time and found that the first response time was 567 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
healthybank.com performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value15.1 s
0/100
25%
Value16.2 s
0/100
10%
Value780 ms
38/100
30%
Value0.953
3/100
15%
Value23.4 s
1/100
10%
567 ms
786 ms
1106 ms
182 ms
546 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 90% of them (130 requests) were addressed to the original Healthybank.com, 3% (4 requests) were made to Googletagmanager.com and 1% (2 requests) were made to Statics.a8.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Healthybank.com.
Page size can be reduced by 683.8 kB (22%)
3.1 MB
2.4 MB
In fact, the total size of Healthybank.com main page is 3.1 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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 315.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. This page needs HTML code to be minified as it can gain 75.4 kB, which is 23% 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 315.1 kB or 95% of the original size.
Potential reduce by 313.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. Obviously, Healthybank needs image optimization as it can save up to 313.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 24.4 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 24.4 kB or 19% of the original size.
Potential reduce by 31.2 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. Healthybank.com needs all CSS files to be minified and compressed as it can save up to 31.2 kB or 58% of the original size.
Number of requests can be reduced by 35 (25%)
139
104
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Healthybank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
healthybank.com
567 ms
healthybank.com
786 ms
www.healthybank.com
1106 ms
import.css
182 ms
jquery.js
546 ms
jquery.scrollTo.js
544 ms
jquery.rollover.js
559 ms
common.js
560 ms
jquery.tile.js
561 ms
jquery.bxslider.js
575 ms
jquery.easing.js
725 ms
jquery.vgrid.js
726 ms
a8sales.js
19 ms
a8crossDomain.js
22 ms
calendar.js
742 ms
referer.js
741 ms
tag.js
30 ms
default.css
567 ms
layout.css
587 ms
content.css
909 ms
jquery.fancybox.css
727 ms
layout_tablet.css
752 ms
content_tablet.css
752 ms
layout_sp.css
754 ms
content_sp.css
779 ms
gtm.js
145 ms
body_bg.png
210 ms
sp_menu_colse.png
209 ms
skip.gif
210 ms
logo.png
208 ms
head_cart.png
209 ms
head_account.png
210 ms
products_01.png
396 ms
products_02.png
397 ms
products_05.png
401 ms
products_06.png
399 ms
products_03.png
397 ms
sp_logo.png
398 ms
sp_menu_btn.png
573 ms
sp_account_btn.png
573 ms
sp_cart_btn.png
581 ms
slide47.jpg
1325 ms
slide01.jpg
965 ms
slide03.jpg
1545 ms
maine_02.png
758 ms
maine_03.png
757 ms
maine_04.png
957 ms
maine_05.png
945 ms
maine_06.png
946 ms
news_title.png
1126 ms
maine_08.png
1308 ms
maine_09.png
1148 ms
maine_29.png
1156 ms
maine_20.png
1494 ms
maine_11.png
1336 ms
maine_12.png
1534 ms
maine_13.png
1495 ms
maine_15.png
1513 ms
maine_16.png
1712 ms
maine_17.png
1676 ms
maine_18.png
1681 ms
ga.js
127 ms
maine_21.png
1701 ms
tag.js
60 ms
adv.js
74 ms
__utm.gif
46 ms
destination
61 ms
destination
94 ms
ytag.js
746 ms
destination
90 ms
bat.js
88 ms
collect
84 ms
7
2263 ms
maine_22.png
1531 ms
maine_23.png
1653 ms
maine_24.png
1658 ms
maine_25.png
1683 ms
maine_26.png
1693 ms
maine_27.png
1536 ms
maine_28.png
1647 ms
sp_bnr.png
1654 ms
sptel_tell_01.png
1681 ms
sptel_tell_02.png
1691 ms
sptel_tell_03.png
1723 ms
sp_main_01.png
1652 ms
sp_main_sub_hl1.png
1658 ms
sp_main_sub01.png
1686 ms
sp_main_sub02.png
1518 ms
sp_main_sub03.png
1556 ms
sp_main_sub08.png
1460 ms
sp_main_sub05.png
1466 ms
sp_main_sub04.png
1495 ms
sp_main_sub07.png
1498 ms
sp_main_02.png
1380 ms
sp_main_sub_hl2.png
1439 ms
sp_main_05.png
1437 ms
sp_main_sub_hl5.png
1331 ms
sp_main_06.png
1326 ms
sp_main_sub_hl6.png
1320 ms
sp_main_03.png
1204 ms
sp_main_sub_hl3.png
1273 ms
sp_bnr02.png
1442 ms
sp_bnr03.png
1481 ms
sp_sub01.png
1293 ms
sp_sub08.png
1167 ms
sp_sub02.png
1207 ms
sp_sub04.png
1246 ms
sp_sub05.png
1312 ms
sp_sub06.png
1295 ms
sp_sub09.png
1222 ms
sp_sub07.png
1267 ms
sp_maine_23.png
1246 ms
sp_maine_24.png
1301 ms
sp_maine_25.png
1282 ms
sp_maine_26.png
1177 ms
sp_maine_27.png
1224 ms
sp_maine_28.png
1235 ms
card_logo1.png
1232 ms
tell_no.png
1267 ms
tell_no2.png
1174 ms
rapidssl_seal.gif
1176 ms
calendar_title.png
1199 ms
payment_title.png
1219 ms
card_logo.png
1189 ms
24hours_title.png
1168 ms
personal_title.png
1173 ms
frow_title.png
1142 ms
footer_logo.png
1194 ms
side_contact_btn.png
1204 ms
pagetop.png
1178 ms
sub_menu_top.png
1177 ms
sub_menu_btm.png
1179 ms
news_bg.png
1143 ms
footer_top.png
1197 ms
footer_btm.png
1200 ms
head_cart_on.png
1166 ms
head_account_on.png
1182 ms
maine_04_on.png
1125 ms
maine_05_on.png
1127 ms
maine_06_on.png
1152 ms
maine_09_on.png
1091 ms
maine_29_on.png
1092 ms
prev.png
1121 ms
next.png
1125 ms
healthybank.com accessibility score
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
healthybank.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
healthybank.com 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 Healthybank.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 Healthybank.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.
healthybank.com
Open Graph description is not detected on the main page of Healthybank. 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: