Tools & Wizards About Us
wanye.cc screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wanye.cc

安全注册

Page Load Speed

72 sec in total

First Response

10.5 sec

Resources Loaded

61.2 sec

Page Rendered

327 ms

wanye.cc screenshot

About Website

Welcome to wanye.cc homepage info - get ready to check Wanye best content for China right away, or after learning these important things about wanye.cc

404 Not Found

Visit wanye.cc

Key Findings

We analyzed Wanye.cc page load time and found that the first response time was 10.5 sec and then it took 61.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 52 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

wanye.cc performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

wanye.cc

10457 ms

index.css

3599 ms

js.js

19900 ms

scrolljs.js

1118 ms

qq.js

1354 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 90% of them (97 requests) were addressed to the original Wanye.cc, 9% (10 requests) were made to Pub.idqqimg.com and 1% (1 request) were made to Cpwz.wanye.cc. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Wanye.cc.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.4 kB (18%)

Content Size

704.8 kB

After Optimization

575.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wanye.cc main page is 704.8 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. Images take 599.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 67.7 kB

  • Original 84.8 kB
  • After minification 82.3 kB
  • After compression 17.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. 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 67.7 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 45.7 kB

  • Original 599.6 kB
  • After minification 554.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. Wanye images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 6.8 kB

  • Original 8.8 kB
  • After minification 7.2 kB
  • After compression 2.0 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 6.8 kB or 77% of the original size.

CSS Optimization

-79%

Potential reduce by 9.2 kB

  • Original 11.6 kB
  • After minification 10.1 kB
  • After compression 2.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. Wanye.cc needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (21%)

Requests Now

53

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wanye.cc

wanye.cc

10457 ms

index.css

index.css

3599 ms

js.js

js.js

19900 ms

scrolljs.js

scrolljs.js

1118 ms

qq.js

qq.js

1354 ms

stat.js

stat.js

470 ms

201562310122241741.jpg

201562310122241741.jpg

7471 ms

20156231011090356.jpg

20156231011090356.jpg

10479 ms

20156231010818456.jpg

20156231010818456.jpg

19993 ms

20156239422476141.jpg

20156239422476141.jpg

1474 ms

201562392487811.gif

201562392487811.gif

4532 ms

201561516225511264.gif

201561516225511264.gif

4405 ms

4772 ms

2014491263720157.jpg

2014491263720157.jpg

12185 ms

201449124240310.gif

201449124240310.gif

7053 ms

20144811273029802.jpg

20144811273029802.jpg

10158 ms

20144811123288991.jpg

20144811123288991.jpg

7819 ms

20144718464720786.jpg

20144718464720786.jpg

9596 ms

2015631445054123.gif

2015631445054123.gif

11904 ms

201633131709337.jpg

201633131709337.jpg

11362 ms

201633131705665.jpg

201633131705665.jpg

19992 ms

201633131609461.jpg

201633131609461.jpg

18685 ms

20155960913605.jpg

20155960913605.jpg

18138 ms

201633131540337.jpg

201633131540337.jpg

19993 ms

20163318465215131.jpg

20163318465215131.jpg

18868 ms

201633021555541198.gif

201633021555541198.gif

19105 ms

201633014172320597.jpg

201633014172320597.jpg

19993 ms

201632816414751040.jpg

201632816414751040.jpg

19994 ms

201632312163520449.jpg

201632312163520449.jpg

19892 ms

20163211761171024.jpg

20163211761171024.jpg

19994 ms

20163211653479706.jpg

20163211653479706.jpg

19994 ms

20163201552566354.gif

20163201552566354.gif

19995 ms

20163181783715663.gif

20163181783715663.gif

19996 ms

201631812444992619.gif

201631812444992619.gif

19996 ms

20163181212243609.gif

20163181212243609.gif

19996 ms

20163181204567467.gif

20163181204567467.gif

19997 ms

201631811552173063.gif

201631811552173063.gif

19997 ms

20163181014958015.gif

20163181014958015.gif

19998 ms

2016318956473399.gif

2016318956473399.gif

19997 ms

20163189173516230.gif

20163189173516230.gif

19998 ms

duilian.jpg

duilian.jpg

10690 ms

ggzz.jpg

ggzz.jpg

19998 ms

logo.gif

logo.gif

415 ms

ggt.gif

ggt.gif

7517 ms

kl.jpg

kl.jpg

6080 ms

www.whlqy.com.jpg

www.whlqy.com.jpg

19997 ms

2.jpg

2.jpg

8073 ms

123.jpg

123.jpg

19997 ms

ad.jpg

ad.jpg

18275 ms

njs.jpg

njs.jpg

19999 ms

dx.jpg

dx.jpg

20000 ms

35.gif

35.gif

20000 ms

34.gif

34.gif

20001 ms

33.gif

33.gif

20000 ms

32.gif

32.gif

20001 ms

31.gif

31.gif

20002 ms

30.gif

30.gif

20003 ms

29.gif

29.gif

20003 ms

28.gif

28.gif

20003 ms

27.gif

27.gif

20004 ms

26.gif

26.gif

20004 ms

25.gif

25.gif

20004 ms

24.gif

24.gif

20005 ms

23.gif

23.gif

20006 ms

22.gif

22.gif

20005 ms

21.gif

21.gif

20006 ms

20.gif

20.gif

20006 ms

19.gif

19.gif

20006 ms

18.gif

18.gif

20006 ms

17.gif

17.gif

20007 ms

16.gif

16.gif

20006 ms

15.gif

15.gif

20007 ms

14.gif

14.gif

20007 ms

13.gif

13.gif

20007 ms

12.gif

12.gif

20007 ms

login.gif

login.gif

19997 ms

tt.jpg

tt.jpg

19602 ms

gg3.gif

gg3.gif

19902 ms

advvv.jpg

advvv.jpg

20466 ms

dh.gif

dh.gif

16617 ms

search.gif

search.gif

14312 ms

button_121.gif

button_121.gif

456 ms

button_121.gif

button_121.gif

455 ms

button_121.gif

button_121.gif

484 ms

button_121.gif

button_121.gif

452 ms

button_121.gif

button_121.gif

454 ms

button_121.gif

button_121.gif

1273 ms

button_121.gif

button_121.gif

229 ms

button_121.gif

button_121.gif

242 ms

button_121.gif

button_121.gif

507 ms

button_121.gif

button_121.gif

227 ms

search2.gif

search2.gif

15698 ms

dh2.gif

dh2.gif

5450 ms

l1.gif

l1.gif

5894 ms

c1.gif

c1.gif

6338 ms

pivbg.gif

pivbg.gif

19982 ms

b-r.gif

b-r.gif

6700 ms

r1.gif

r1.gif

7058 ms

r0.gif

r0.gif

7416 ms

arrow.gif

arrow.gif

10161 ms

c2.gif

c2.gif

8703 ms

c_t.gif

c_t.gif

9065 ms

c_tj.gif

c_tj.gif

9426 ms

d_t.gif

d_t.gif

12227 ms

fbg.gif

fbg.gif

10519 ms

link.gif

link.gif

10879 ms

dh3.gif

dh3.gif

11238 ms

ewm.jpg

ewm.jpg

19973 ms

Accessibility Review

wanye.cc accessibility score

59

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

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

Best Practices

wanye.cc 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

SEO Factors

wanye.cc SEO score

83

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

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wanye.cc 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 Wanye.cc main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

wanye.cc

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