7.9 sec in total
557 ms
7.1 sec
207 ms
Visit weider-jp.com now to see the best up-to-date Weider Jp content for Japan and also check out these interesting facts you probably never knew about weider-jp.com
ウイダープロテインをはじめとした商品情報、栄養・運動講座、プロテインについてなど幅広く紹介しています。
Visit weider-jp.comWe analyzed Weider-jp.com page load time and found that the first response time was 557 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
weider-jp.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value8.6 s
1/100
25%
Value6.6 s
37/100
10%
Value540 ms
55/100
30%
Value0.066
97/100
15%
Value8.4 s
39/100
10%
557 ms
1280 ms
555 ms
29 ms
496 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 48% of them (46 requests) were addressed to the original Weider-jp.com, 21% (20 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Weider-jp.com.
Page size can be reduced by 316.4 kB (18%)
1.8 MB
1.5 MB
In fact, the total size of Weider-jp.com main page is 1.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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 24.4 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 24.4 kB or 74% of the original size.
Potential reduce by 179.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. Obviously, Weider Jp needs image optimization as it can save up to 179.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 44.3 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 44.3 kB or 54% of the original size.
Potential reduce by 68.1 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. Weider-jp.com needs all CSS files to be minified and compressed as it can save up to 68.1 kB or 86% of the original size.
Number of requests can be reduced by 45 (48%)
93
48
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weider Jp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
weider-jp.com
557 ms
www.weider-jp.com
1280 ms
index.css
555 ms
jquery.min.js
29 ms
bookmark_button.js
496 ms
line-button.js
503 ms
shared.js
354 ms
jquery.flatheights.js
368 ms
top.js
372 ms
jelly01_118.png
692 ms
protein01_a_01_118.png
702 ms
bar01_118.png
369 ms
drink03_b_118.png
739 ms
tablet01_a_118.png
743 ms
goods01_118.png
743 ms
thumb_640_06.jpg
1593 ms
thumb_640_05.jpg
1539 ms
thumb_640_04.jpg
1618 ms
thumb_210_01.jpg
1430 ms
thumb_210_02.jpg
1446 ms
thumb_210_03.jpg
1473 ms
thumb_210_04.jpg
2111 ms
main_image.jpg
3123 ms
main_image.jpg
3048 ms
main_image.jpg
3344 ms
main_image.jpg
3115 ms
main_image.png
3202 ms
title_01.png
2446 ms
goods02_118.png
2795 ms
title_02.png
3150 ms
title_03.png
3395 ms
title_01.png
3470 ms
img_bnr_17.jpg
3828 ms
img_bnr_01.png
3486 ms
img_bnr_07.jpg
3572 ms
img_bnr_13.png
3689 ms
title_05.png
3736 ms
title_06.png
3822 ms
button-only@2x.png
225 ms
sdk.js
272 ms
bg_gnav.png
3809 ms
gnav.png
4228 ms
header_icon_search.png
4028 ms
bg_wrapper_01.jpg
4060 ms
blank.gif
4146 ms
icon_link_01.png
4171 ms
icon_blank_01.png
4177 ms
widgets.js
5 ms
like.php
92 ms
643 ms
sync_suggest.js
331 ms
vpc6VNjRPXV.js
477 ms
LVx-xkvaJ0b.png
542 ms
93 ms
xd_arbiter.php
208 ms
xd_arbiter.php
415 ms
icon_link_blank.png
4041 ms
gtm.js
61 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
17 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
13 ms
analytics.js
22 ms
like_box.php
165 ms
collect
15 ms
collect
55 ms
jot
95 ms
CA_as7rLQla.css
112 ms
OEt2CsoTM9t.css
179 ms
YLIWaFzOgE1.css
204 ms
XLZJDgeZlmm.css
273 ms
_rx8naC75Dy.js
337 ms
x5F9OMjKyLw.js
353 ms
ICDbTSzjQEg.js
207 ms
TTCre3391I0.js
244 ms
njO1TPvGzoR.js
270 ms
b_6HNn_J2BZ.js
286 ms
7cm7D75Y0Sf.js
311 ms
rFmE1g6Dkoz.js
537 ms
btn_pagetop.png
3719 ms
icon_blank_03.png
4162 ms
reset.css
9 ms
entry-button.css
10 ms
footer_link_01.png
3793 ms
bbtn-l_v3.png
2 ms
11407256_985891414776058_5359747075343915312_n.jpg
134 ms
11265404_967893083242558_121747734279243708_n.jpg
129 ms
12744701_1118887758143089_6243853875345446098_n.jpg
129 ms
10297679_1118316678200197_9160668017615866760_n.jpg
132 ms
12745730_1117736801591518_2322815656994029726_n.jpg
134 ms
10423273_1117192214979310_9164843462996913370_n.jpg
132 ms
12728866_1114886278543237_5405356053491948968_n.jpg
134 ms
wL6VQj7Ab77.png
123 ms
s7jcwEQH7Sx.png
122 ms
QDwYpIaRyfG.png
122 ms
a-ZN6WoEOje.png
122 ms
I6-MnjEovm5.js
70 ms
vlXaquuXMrr.js
72 ms
weider-jp.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
weider-jp.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
General
Impact
Issue
Detected JavaScript libraries
weider-jp.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weider-jp.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 Weider-jp.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.
weider-jp.com
Open Graph description is not detected on the main page of Weider Jp. 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: