Tools & Wizards About Us

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

reebok.jp

Reebok 公式オンラインショップ

Page Load Speed

20.6 sec in total

First Response

327 ms

Resources Loaded

17.8 sec

Page Rendered

2.5 sec

About Website

Visit reebok.jp now to see the best up-to-date Reebok content for Japan and also check out these interesting facts you probably never knew about reebok.jp

Reebok（リーボック）公式オンラインショップ。スニーカー、トップス、ボトムス、アウターのスポーツファッションで日常をアクティブに。フィットネスシューズ＆ウェア、ランニングシューズのスポーツ仕様でパフォーマンスを最大限に。豊富な品揃え、限定アイテム、会員限定特典はリーボック公式ECサイトならでは。

Visit reebok.jp

Key Findings

We analyzed Reebok.jp page load time and found that the first response time was 327 ms and then it took 20.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

reebok.jp performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value42.8 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value39.4 s

0/100

10%

Network Requests Diagram

reebok.jp

327 ms

reebok.jp

1185 ms

jquery.min.js

40 ms

handlebars.min.js

55 ms

handlebars-templates.js

1169 ms

Our browser made a total of 174 requests to load all elements on the main page. We found that 11% of them (20 requests) were addressed to the original Reebok.jp, 48% (83 requests) were made to Media.aws.locondo.jp and 14% (24 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (12.3 sec) relates to the external source Media.aws.locondo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (17%)

Content Size

14.5 MB

After Optimization

12.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Reebok.jp main page is 14.5 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. Only a small number of websites need less resources to load. Images take 12.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 117.4 kB

  • Original 142.2 kB
  • After minification 123.3 kB
  • After compression 24.8 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 18.9 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 117.4 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 1.2 MB

  • Original 12.9 MB
  • After minification 11.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. Reebok images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 550.9 kB

  • Original 772.6 kB
  • After minification 738.3 kB
  • After compression 221.6 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 550.9 kB or 71% of the original size.

CSS Optimization

-88%

Potential reduce by 596.2 kB

  • Original 679.6 kB
  • After minification 563.6 kB
  • After compression 83.4 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. Reebok.jp needs all CSS files to be minified and compressed as it can save up to 596.2 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (62%)

Requests Now

122

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reebok. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

reebok.jp accessibility score

51

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

reebok.jp best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

reebok.jp SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

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

Social Sharing Optimization

Open Graph data is detected on the main page of Reebok. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: