Tools & Wizards About Us
weider-jp.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

weider-jp.com

プロテイン・栄養運動情報【ウイダー公式　森永製菓株式会社】

Page Load Speed

4.6 sec in total

First Response

31 ms

Resources Loaded

4.1 sec

Page Rendered

418 ms

weider-jp.com screenshot

About Website

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.com

Key Findings

We analyzed Weider-jp.com page load time and found that the first response time was 31 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

weider-jp.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

weider-jp.com

31 ms

weider-jp.com

701 ms

otSDKStub.js

47 ms

OtAutoBlock.js

85 ms

common_2018.css

926 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 82% of them (28 requests) were addressed to the original Weider-jp.com, 9% (3 requests) were made to Cdn-au.onetrust.com and 3% (1 request) were made to Geolocation.onetrust.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Weider-jp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.7 kB (7%)

Content Size

1.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weider-jp.com main page is 1.9 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. 30% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 11.2 kB

  • Original 14.6 kB
  • After minification 12.0 kB
  • After compression 3.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 2.6 kB, which is 18% 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.2 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 57.2 kB

  • Original 1.8 MB
  • After minification 1.7 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. Weider Jp images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 30.4 kB

  • Original 87.7 kB
  • After minification 82.0 kB
  • After compression 57.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 30.4 kB or 35% of the original size.

CSS Optimization

-84%

Potential reduce by 29.9 kB

  • Original 35.7 kB
  • After minification 27.5 kB
  • After compression 5.7 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 29.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (28%)

Requests Now

32

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 32 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 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

weider-jp.com

weider-jp.com

31 ms

weider-jp.com

weider-jp.com

701 ms

otSDKStub.js

otSDKStub.js

47 ms

OtAutoBlock.js

OtAutoBlock.js

85 ms

common_2018.css

common_2018.css

926 ms

top.css

top.css

692 ms

header_logo_02.png

header_logo_02.png

709 ms

header_icon_cart02.svg

header_icon_cart02.svg

613 ms

kv_img_01.jpg

kv_img_01.jpg

1410 ms

kv_img_02.png

kv_img_02.png

1161 ms

product_01.png

product_01.png

2056 ms

product_02.png

product_02.png

1721 ms

product_10.png

product_10.png

1715 ms

product_04.png

product_04.png

1930 ms

product_05_02.png

product_05_02.png

2002 ms

product_03.png

product_03.png

2445 ms

product_06.png

product_06.png

3088 ms

btn_product.svg

btn_product.svg

2400 ms

84c9d952-c6c8-4abc-be12-6c81fab13e05.json

84c9d952-c6c8-4abc-be12-6c81fab13e05.json

41 ms

location

location

58 ms

jquery.min.js

jquery.min.js

18 ms

jquery.easing-1.3.min.js

jquery.easing-1.3.min.js

1945 ms

picturefill.min.js

picturefill.min.js

2019 ms

gnav.js

gnav.js

2591 ms

shared.js

shared.js

2618 ms

top.js

top.js

2701 ms

title_news.svg

title_news.svg

2904 ms

btn_pagetop.svg

btn_pagetop.svg

2455 ms

sync_suggest.js

sync_suggest.js

876 ms

blank.svg

blank.svg

2366 ms

product_bg_00.png

product_bg_00.png

2508 ms

panel_bg_01.jpg

panel_bg_01.jpg

2348 ms

panel_bg_02.png

panel_bg_02.png

2124 ms

bg_newsInfo.jpg

bg_newsInfo.jpg

2628 ms

Accessibility Review

weider-jp.com accessibility score

98

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

weider-jp.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

weider-jp.com SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: