Tools & Wizards About Us
winzhong.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

winzhong.com

WELL. 唯奥,国内领先的体验创新设计咨询公司-客户服务体验设计-UI,UX,界面交互设计公司-用户产品与服务体验设计-品牌体验策略咨询-数字化界面-空间体验店设计

Page Load Speed

35.3 sec in total

First Response

4 sec

Resources Loaded

30.6 sec

Page Rendered

637 ms

winzhong.com screenshot

About Website

Visit winzhong.com now to see the best up-to-date Winzhong content and also check out these interesting facts you probably never knew about winzhong.com

WELL，唯奥是国内知名的体验创新设计咨询公司。专注消费领域与智能领域，10年来，为200多家合伙伙伴提供过体验创新方案，帮助客户打造围绕品牌及数字化产品、服务和空间于一体的体验创新，创造了超出用户预期的体验，为千万用户带来真实的体验提升！

Visit winzhong.com

Key Findings

We analyzed Winzhong.com page load time and found that the first response time was 4 sec and then it took 31.2 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. Unfortunately, there were 13 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

winzhong.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.3 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

winzhong.com

4046 ms

style.css

2667 ms

jquery.jslides.js

831 ms

jquery-1.7.1.min.js

6563 ms

jquery.lightbox.min.js

2542 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 79% of them (38 requests) were addressed to the original Winzhong.com, 13% (6 requests) were made to Hm.baidu.com and 8% (4 requests) were made to Lxbjs.baidu.com. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Winzhong.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.9 kB (60%)

Content Size

216.1 kB

After Optimization

86.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Winzhong.com main page is 216.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 120.2 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 8.4 kB

  • Original 12.2 kB
  • After minification 11.3 kB
  • After compression 3.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. 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 8.4 kB or 69% of the original size.

Image Optimization

-30%

Potential reduce by 15.2 kB

  • Original 51.3 kB
  • After minification 36.0 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, Winzhong needs image optimization as it can save up to 15.2 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 79.7 kB

  • Original 120.2 kB
  • After minification 118.7 kB
  • After compression 40.5 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 79.7 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 26.6 kB

  • Original 32.4 kB
  • After minification 28.7 kB
  • After compression 5.8 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. Winzhong.com needs all CSS files to be minified and compressed as it can save up to 26.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (26%)

Requests Now

31

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

winzhong.com

winzhong.com

4046 ms

style.css

style.css

2667 ms

jquery.jslides.js

jquery.jslides.js

831 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

6563 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

2542 ms

caseindex.js

caseindex.js

1331 ms

hm.js

hm.js

889 ms

hm.js

hm.js

1301 ms

topbg.png

topbg.png

436 ms

logo.png

logo.png

1748 ms

indeximg.jpg

indeximg.jpg

19768 ms

index_icon1.png

index_icon1.png

2417 ms

index_icon2.png

index_icon2.png

442 ms

index_icon3.png

index_icon3.png

3632 ms

index_icon4.png

index_icon4.png

2077 ms

fwline.gif

fwline.gif

866 ms

tab1.png

tab1.png

2180 ms

tab3.png

tab3.png

2164 ms

tab2.png

tab2.png

2548 ms

tab4.png

tab4.png

2590 ms

indexcase03.jpg

indexcase03.jpg

15088 ms

indexcase01.jpg

indexcase01.jpg

19764 ms

indexcase02.jpg

indexcase02.jpg

19364 ms

indexcase05.jpg

indexcase05.jpg

13185 ms

indexcase06.jpg

indexcase06.jpg

19765 ms

indexcase04.jpg

indexcase04.jpg

19770 ms

page_l.gif

page_l.gif

15450 ms

page_r.gif

page_r.gif

16957 ms

navline.png

navline.png

19774 ms

footerbg.png

footerbg.png

19777 ms

tagwb.png

tagwb.png

19787 ms

tagtc.png

tagtc.png

19809 ms

tagqq.png

tagqq.png

19810 ms

tagtel.png

tagtel.png

19814 ms

txt.svg

txt.svg

19821 ms

h.js

h.js

1070 ms

hm.gif

hm.gif

427 ms

lxb.js

lxb.js

1702 ms

jquery.lightbox.css

jquery.lightbox.css

19467 ms

loading.gif

loading.gif

19457 ms

prev.gif

prev.gif

19481 ms

next.gif

next.gif

19572 ms

blank.gif

blank.gif

19571 ms

hm.gif

hm.gif

1049 ms

hm.gif

hm.gif

476 ms

log.gif

log.gif

338 ms

_l.js

_l.js

788 ms

log.gif

log.gif

353 ms

Accessibility Review

winzhong.com accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

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

winzhong.com best practices score

83

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

winzhong.com SEO score

90

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Winzhong.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Winzhong.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

winzhong.com

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