16.9 sec in total
569 ms
16 sec
342 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 569 ms and then it took 16.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
healthybank.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value11.6 s
0/100
25%
Value12.6 s
3/100
10%
Value3,790 ms
1/100
30%
Value1.657
0/100
15%
Value22.3 s
1/100
10%
569 ms
1388 ms
367 ms
1267 ms
382 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 73% of them (124 requests) were addressed to the original Healthybank.com, 11% (19 requests) were made to Static.xx.fbcdn.net and 4% (7 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Healthybank.com.
Page size can be reduced by 630.9 kB (19%)
3.4 MB
2.7 MB
In fact, the total size of Healthybank.com main page is 3.4 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 92.5 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 13.5 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 92.5 kB or 86% of the original size.
Potential reduce by 229.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. Healthybank images are well optimized though.
Potential reduce by 180.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 180.4 kB or 63% of the original size.
Potential reduce by 128.9 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 128.9 kB or 85% of the original size.
Number of requests can be reduced by 56 (34%)
165
109
The browser has sent 165 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 34 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
healthybank.com
569 ms
www.healthybank.com
1388 ms
import.css
367 ms
jquery.js
1267 ms
jquery.scrollTo.js
382 ms
jquery.rollover.js
382 ms
common.js
382 ms
jquery.tile.js
718 ms
jquery.bxslider.js
1118 ms
jquery.easing.js
948 ms
jquery.vgrid.js
963 ms
login_tmp
816 ms
default.css
724 ms
layout.css
952 ms
content.css
1769 ms
jquery.fancybox.css
1142 ms
layout_tablet.css
1076 ms
content_tablet.css
1486 ms
layout_sp.css
1441 ms
content_sp.css
1663 ms
calendar.js
1427 ms
referer.js
1105 ms
tag.js
521 ms
338 ms
bl_track.js
336 ms
login_tmp
1235 ms
body_bg.png
180 ms
sp_menu_colse.png
353 ms
skip.gif
372 ms
logo.png
780 ms
head_cart.png
398 ms
head_account.png
424 ms
products_01.png
758 ms
products_02.png
883 ms
products_03.png
943 ms
products_05.png
985 ms
products_04.png
967 ms
sp_logo.png
1307 ms
sp_menu_btn.png
1139 ms
sp_account_btn.png
1257 ms
sp_cart_btn.png
1288 ms
slide08.jpg
2737 ms
slide01.jpg
2530 ms
slide03.jpg
2948 ms
maine_02.png
2174 ms
maine_03.png
2044 ms
maine_04.png
2223 ms
maine_05.png
2968 ms
maine_06.png
3122 ms
news_title.png
2759 ms
maine_08.png
3684 ms
maine_09.png
3635 ms
maine_10.png
3708 ms
maine_20.png
4232 ms
maine_11.png
3734 ms
maine_12.png
4170 ms
maine_13.png
4676 ms
maine_14.png
4935 ms
maine_15.png
4687 ms
ga.js
30 ms
maine_16.png
4992 ms
maine_17.png
4877 ms
__utm.gif
39 ms
maine_18.png
5227 ms
347 ms
bl_track.cgi
380 ms
tag.js
33 ms
likebox.php
364 ms
tag
8 ms
7
4913 ms
sp_bnr.png
5337 ms
sptel_tell_01.png
5267 ms
sptel_tell_02.png
5330 ms
sptel_tell_03.png
5140 ms
roNeOY-tz5Y.css
33 ms
UHhaxo8Cs3k.css
38 ms
dbNRhrdsQao.css
37 ms
1ssvpqNRk1L.css
41 ms
_rx8naC75Dy.js
40 ms
x5F9OMjKyLw.js
62 ms
ICDbTSzjQEg.js
61 ms
TTCre3391I0.js
61 ms
njO1TPvGzoR.js
72 ms
b_6HNn_J2BZ.js
75 ms
7cm7D75Y0Sf.js
76 ms
rFmE1g6Dkoz.js
83 ms
336JejShbZp.js
82 ms
1622263_729498673750604_1041006400_n.jpg
94 ms
523186_529792617054545_245806058_n.png
14 ms
10153654_1126926247341176_4709840869788986050_n.jpg
15 ms
12654552_1117470468286754_6497123838094382102_n.jpg
17 ms
6863_1110886112278523_8764192163411793675_n.jpg
15 ms
12509270_1104877096212758_5143337906554422256_n.jpg
20 ms
1934399_1097851460248655_3536668488332240530_n.jpg
17 ms
wL6VQj7Ab77.png
6 ms
s7jcwEQH7Sx.png
10 ms
QDwYpIaRyfG.png
6 ms
a-ZN6WoEOje.png
9 ms
I6-MnjEovm5.js
2 ms
vlXaquuXMrr.js
4 ms
sp_main_01.png
4904 ms
sp_main_sub_hl1.png
5059 ms
sp_main_sub01.png
5214 ms
sp_main_sub02.png
5236 ms
sp_main_sub03.png
5054 ms
sp_main_sub04.png
5081 ms
sp_main_02.png
5134 ms
sp_main_sub_hl2.png
4967 ms
sp_main_03.png
5245 ms
sp_main_sub_hl3.png
5148 ms
sp_main_05.png
4582 ms
sp_main_sub_hl5.png
4351 ms
sp_main_04.png
4568 ms
sp_main_sub_hl4.png
4129 ms
sp_bnr02.png
5023 ms
sp_bnr03.png
5087 ms
sp_sub01.png
4125 ms
sp_sub08.png
4254 ms
sp_sub02.png
3887 ms
sp_sub03.png
3507 ms
sp_sub04.png
3664 ms
sp_sub05.png
3724 ms
sp_sub06.png
3790 ms
sp_sub07.png
3600 ms
card_logo1.png
3888 ms
card_logo2.png
3131 ms
card_logo3.png
3189 ms
yamato.png
3228 ms
tell_no.png
3395 ms
tell_no2.png
3372 ms
rapidssl_seal.gif
3311 ms
calendar_title.png
2917 ms
payment_title.png
2933 ms
card_logo.png
3452 ms
24hours_title.png
2956 ms
personal_title.png
3025 ms
frow_title.png
3000 ms
footer_logo.png
3089 ms
side_contact_btn.png
3052 ms
pagetop.png
2890 ms
sub_menu_top.png
3505 ms
login_bg.png
3488 ms
login_mail.png
3253 ms
login_pass.png
3025 ms
login_re.png
2986 ms
login_new.png
2932 ms
login_btn.png
3124 ms
sub_menu_btm.png
3163 ms
news_bg.png
3172 ms
footer_top.png
3065 ms
footer_btm.png
2951 ms
head_cart_on.png
2926 ms
head_account_on.png
2873 ms
maine_04_on.png
3502 ms
maine_05_on.png
3368 ms
maine_06_on.png
3360 ms
maine_09_on.png
3126 ms
maine_10_on.png
2997 ms
prev.png
2584 ms
next.png
2929 ms
analytics.js
11 ms
rs.do
520 ms
ya.js
384 ms
linkid.js
10 ms
collect
12 ms
pb.js
906 ms
347 ms
pv.js
302 ms
so_sg.js
1041 ms
healthybank.com accessibility score
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
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: