Tools & Wizards About Us
yonex.cn screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

yonex.cn

Yonex

Page Load Speed

15.5 sec in total

First Response

2.1 sec

Resources Loaded

12.8 sec

Page Rendered

560 ms

yonex.cn screenshot

About Website

Visit yonex.cn now to see the best up-to-date Yonex content for China and also check out these interesting facts you probably never knew about yonex.cn

Yonex

Visit yonex.cn

Key Findings

We analyzed Yonex.cn page load time and found that the first response time was 2.1 sec and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

yonex.cn performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value46.9 s

0/100

25%

SI (Speed Index)

Value25.7 s

0/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

yonex.cn

2135 ms

module.css

243 ms

style.css

969 ms

swiper.css

728 ms

swiper.min.js

1703 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 94% of them (45 requests) were addressed to the original Yonex.cn, 4% (2 requests) were made to Hm.baidu.com and 2% (1 request) were made to Img2.yonex.cn. The less responsive or slowest element that took the longest time to load (8.9 sec) belongs to the original domain Yonex.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 836.6 kB (5%)

Content Size

18.5 MB

After Optimization

17.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yonex.cn main page is 18.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 17.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 28.8 kB

  • Original 34.2 kB
  • After minification 24.4 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 9.8 kB, which is 29% 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 28.8 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 348.5 kB

  • Original 17.9 MB
  • After minification 17.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. Yonex images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 320.5 kB

  • Original 396.6 kB
  • After minification 325.2 kB
  • After compression 76.1 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 320.5 kB or 81% of the original size.

CSS Optimization

-86%

Potential reduce by 138.8 kB

  • Original 161.6 kB
  • After minification 151.3 kB
  • After compression 22.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. Yonex.cn needs all CSS files to be minified and compressed as it can save up to 138.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (13%)

Requests Now

46

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yonex.cn

yonex.cn

2135 ms

module.css

module.css

243 ms

style.css

style.css

969 ms

swiper.css

swiper.css

728 ms

swiper.min.js

swiper.min.js

1703 ms

jquery.min.js

jquery.min.js

1504 ms

lib.js

lib.js

488 ms

animate.min.css

animate.min.css

977 ms

hm.js

hm.js

3182 ms

ico_jxs.png

ico_jxs.png

244 ms

search-icon.png

search-icon.png

245 ms

fd-logo.png

fd-logo.png

243 ms

ico_jxs2.png

ico_jxs2.png

245 ms

so.png

so.png

245 ms

icon-close.png

icon-close.png

246 ms

icon-down.png

icon-down.png

485 ms

1599742059514f211c680cb7bd346ef8.jpg

1599742059514f211c680cb7bd346ef8.jpg

4852 ms

246f051ff608db2c61b97cb37f896e79.jpg

246f051ff608db2c61b97cb37f896e79.jpg

1217 ms

9f68740b95729776028284b727558425.jpg

9f68740b95729776028284b727558425.jpg

1461 ms

cf776a2429c5e6ea0348758f1d23bf4f.jpg

cf776a2429c5e6ea0348758f1d23bf4f.jpg

5937 ms

2e273e66839aaafea21ed4d941a270ba.jpg

2e273e66839aaafea21ed4d941a270ba.jpg

3418 ms

24f433d612f317a10e28bd60034076e0.jpg

24f433d612f317a10e28bd60034076e0.jpg

1493 ms

7f5fbad1ac5168b0b38ebaea73d85e6a.jpg

7f5fbad1ac5168b0b38ebaea73d85e6a.jpg

1462 ms

9623d30b74c5bae33452e94f03986bc5.jpg

9623d30b74c5bae33452e94f03986bc5.jpg

4175 ms

75c8ca128b1f60869377b143dde9a14b.jpg

75c8ca128b1f60869377b143dde9a14b.jpg

6607 ms

bd712cfcea09165b961f9ccb77faf5d6.jpg

bd712cfcea09165b961f9ccb77faf5d6.jpg

3185 ms

14ffa74ad0116c40f9e6f10a194a2ab3.jpg

14ffa74ad0116c40f9e6f10a194a2ab3.jpg

3669 ms

b51bfffc172ff5ee206b400e56023284.jpg

b51bfffc172ff5ee206b400e56023284.jpg

3662 ms

07766bde7c6b5c1dcd2ee415a9bccafc.jpg

07766bde7c6b5c1dcd2ee415a9bccafc.jpg

5685 ms

44a63e9ef7decb751a5d1bac47c2cb91.jpg

44a63e9ef7decb751a5d1bac47c2cb91.jpg

6330 ms

d1aaf331687ac173c94a81665f73ebfa.png

d1aaf331687ac173c94a81665f73ebfa.png

8067 ms

icon-btn1.png

icon-btn1.png

5093 ms

2d72f3439e2288676806d1dd6bac1dbf.png

2d72f3439e2288676806d1dd6bac1dbf.png

5335 ms

89432ae61600a6284dd7e550fa78fac7.jpg

89432ae61600a6284dd7e550fa78fac7.jpg

5578 ms

75e152f6063d0ab06f1804092516a355.jpg

75e152f6063d0ab06f1804092516a355.jpg

5822 ms

e3d37a4fc39f43c29bff140edea16265.jpg

e3d37a4fc39f43c29bff140edea16265.jpg

5930 ms

0a18632bb50cf741c5c8a60572926ded.jpg

0a18632bb50cf741c5c8a60572926ded.jpg

6065 ms

4a31914e619bc0b7991c885597157f71.png

4a31914e619bc0b7991c885597157f71.png

7150 ms

7034634676e9561229712ea29f0d1174.jpg

7034634676e9561229712ea29f0d1174.jpg

8886 ms

goTop.png

goTop.png

6308 ms

fd-link.png

fd-link.png

6550 ms

phone_icon.png

phone_icon.png

6571 ms

beian.png

beian.png

6793 ms

f44d95ad9d56a36538f7c4a9dfbe6c36.jpg

f44d95ad9d56a36538f7c4a9dfbe6c36.jpg

6813 ms

FZLTXHK.TTF

FZLTXHK.TTF

5580 ms

btn_empty.png

btn_empty.png

6777 ms

btn_current.png

btn_current.png

6797 ms

hm.gif

hm.gif

334 ms

Accessibility Review

yonex.cn accessibility score

87

Accessibility Issues

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.

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

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

yonex.cn best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yonex.cn SEO score

71

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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

yonex.cn

Open Graph description is not detected on the main page of Yonex. 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: