9.7 sec in total
878 ms
8.6 sec
182 ms
Visit haleo.jp now to see the best up-to-date HALEO content for Japan and also check out these interesting facts you probably never knew about haleo.jp
HALEO エリートアスリート専用革新的スポーツサプリメント。
Visit haleo.jpWe analyzed Haleo.jp page load time and found that the first response time was 878 ms and then it took 8.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.
haleo.jp performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value102.0 s
0/100
25%
Value6.3 s
41/100
10%
Value520 ms
56/100
30%
Value0.103
89/100
15%
Value6.8 s
55/100
10%
878 ms
339 ms
510 ms
527 ms
25 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 83% of them (63 requests) were addressed to the original Haleo.jp, 5% (4 requests) were made to Google-analytics.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Haleo.jp.
Page size can be reduced by 1.4 MB (52%)
2.8 MB
1.3 MB
In fact, the total size of Haleo.jp main page is 2.8 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. 40% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 20.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. 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 20.6 kB or 76% of the original size.
Potential reduce by 1.2 MB
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, HALEO needs image optimization as it can save up to 1.2 MB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 133.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 133.0 kB or 60% of the original size.
Potential reduce by 24.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. Haleo.jp needs all CSS files to be minified and compressed as it can save up to 24.0 kB or 79% of the original size.
Number of requests can be reduced by 28 (37%)
75
47
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HALEO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
haleo.jp
878 ms
import.css
339 ms
common.css
510 ms
index.css
527 ms
css
25 ms
jquery.fancybox.css
546 ms
jquery.js
1122 ms
scripts.js
830 ms
easyselectbox.js
999 ms
jquery.fancybox.pack.js
1184 ms
movie.js
1038 ms
respond.src.js
1083 ms
default.css
859 ms
general.css
1194 ms
analytics.js
12 ms
ga.js
12 ms
movie_image2.jpg
675 ms
logo.png
324 ms
btn_haleoblog.png
346 ms
btn_haleotv.png
354 ms
getreal_af.png
552 ms
product_selecter_img_1.png
1446 ms
product_selecter_img_2.png
1724 ms
product_selecter_img_3.png
1671 ms
btn_animate_next.png
710 ms
btn_animate_prev.png
888 ms
btn_moreview02.png
1007 ms
header_copy.png
1405 ms
blue_dragon_alpha.png
2044 ms
blue_dragon.png
2168 ms
hyper_reload.png
2665 ms
chase.png
2647 ms
isocore_black_ops.png
2550 ms
hyperdrive_eng.png
2589 ms
mach6.png
3353 ms
t-jack.png
3162 ms
hyper_drive_tabs.png
3730 ms
ignite.png
3769 ms
alphalean.png
3333 ms
gcs750.png
3829 ms
phenom.png
3988 ms
creavol_black_ops.png
4546 ms
c3x.png
4261 ms
creavol.png
4911 ms
creavol_infused.png
4950 ms
up.png
4671 ms
vivo.png
4954 ms
clear.png
5496 ms
new_joint_s.png
5239 ms
amino_spike.png
5897 ms
bnr_haleoblog.png
5461 ms
sdk.js
76 ms
logo_bodyplus_bbs2.png
5472 ms
widgets.js
59 ms
collect
47 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
27 ms
__utm.gif
27 ms
227 ms
xd_arbiter.php
72 ms
xd_arbiter.php
134 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
13 ms
jot
86 ms
logo_cybertrainer.png
4978 ms
logo_bulksports.png
5221 ms
bnr_shopping.jpg
5451 ms
ttl_mailmag.png
5249 ms
btn_regist.png
5159 ms
video_bg.png
5143 ms
blue_arrow.png
5032 ms
movie_slide_mask.png
5136 ms
header_copy_bg.png
4762 ms
product_list_bg1.png
4720 ms
footer_back.png
4688 ms
select-box-arrow.png
4517 ms
product_selecter_is_select_on.png
4227 ms
product_selecter_is_select_off.png
4308 ms
haleo.jp 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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
haleo.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
haleo.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haleo.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 Haleo.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.
haleo.jp
Open Graph data is detected on the main page of HALEO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: