Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

mtb.shimano.com

Connected to trails, to nature, to friends | Shimano MTB

Page Load Speed

3 sec in total

First Response

32 ms

Resources Loaded

2.3 sec

Page Rendered

667 ms

About Website

Click here to check amazing MTB Shimano content for United States. Otherwise, check out these important facts you probably never knew about mtb.shimano.com

Establishing new pathways for a better ride with the world's most refined MTB components, bringing us closer to the trails, closer to nature, and closer to each other.

Visit mtb.shimano.com

Key Findings

We analyzed Mtb.shimano.com page load time and found that the first response time was 32 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

mtb.shimano.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value59.1 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value2,960 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value63.5 s

0/100

10%

Network Requests Diagram

mtb.shimano.com

32 ms

mtb.shimano.com

126 ms

10041206-10042778.js

123 ms

dg.js

131 ms

css2

195 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 80% of them (92 requests) were addressed to the original Mtb.shimano.com, 5% (6 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Player.youku.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 478.5 kB (6%)

Content Size

8.3 MB

After Optimization

7.8 MB

In fact, the total size of Mtb.shimano.com main page is 8.3 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 7.8 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 153.5 kB

  • Original 169.6 kB
  • After minification 113.3 kB
  • After compression 16.1 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 56.3 kB, which is 33% 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 153.5 kB or 91% of the original size.

Image Optimization

-4%

Potential reduce by 312.1 kB

  • Original 7.8 MB
  • After minification 7.5 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. MTB Shimano images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 12.9 kB

  • Original 268.8 kB
  • After minification 268.8 kB
  • After compression 255.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 27 B

  • Original 68.9 kB
  • After minification 68.9 kB
  • After compression 68.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. Mtb.shimano.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (15%)

Requests Now

104

After Optimization

88

The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MTB Shimano. 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.

Accessibility Review

mtb.shimano.com accessibility score

100

Accessibility Issues

Best Practices

mtb.shimano.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mtb.shimano.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mtb.shimano.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Mtb.shimano.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

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