Tools & Wizards About Us
zx.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

zx.com

貪玩官方網站_貪玩遊戲,找回年少時貪玩的你

Page Load Speed

5.1 sec in total

First Response

244 ms

Resources Loaded

4.8 sec

Page Rendered

58 ms

zx.com screenshot

About Website

Welcome to zx.com homepage info - get ready to check Zx best content right away, or after learning these important things about zx.com

貪玩作為中國數字互動娛樂行業的市場領導者，以“在數字時代，為終端用户創造快樂，為商業夥伴賦能前行”為使命，秉承“找回年少時貪玩的你”的初心，為全球遊戲玩家提供多元化遊戲產品。貪玩的核心競爭力基於三大支柱，精準數字營銷、深度運營及品牌孵化。

Visit zx.com

Key Findings

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

Performance Metrics

zx.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

zx.com

244 ms

zx.com

2526 ms

common.css

1207 ms

pc.css

1050 ms

index.css

2012 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Zx.com, 96% (44 requests) were made to Image.zx.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Zx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 239.2 kB (14%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Zx.com main page is 1.7 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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 47.6 kB

  • Original 58.4 kB
  • After minification 39.9 kB
  • After compression 10.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.5 kB, which is 32% 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 47.6 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 83.4 kB

  • Original 1.5 MB
  • After minification 1.4 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. Zx images are well optimized though.

CSS Optimization

-88%

Potential reduce by 108.2 kB

  • Original 123.3 kB
  • After minification 117.5 kB
  • After compression 15.0 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. Zx.com needs all CSS files to be minified and compressed as it can save up to 108.2 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

44

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zx.com

zx.com

244 ms

zx.com

zx.com

2526 ms

common.css

common.css

1207 ms

pc.css

pc.css

1050 ms

index.css

index.css

2012 ms

logo.png

logo.png

256 ms

jquery.min.js

jquery.min.js

332 ms

swiper.min.js

swiper.min.js

315 ms

wow.min.js

wow.min.js

278 ms

utils.js

utils.js

289 ms

marquee.min.js

marquee.min.js

299 ms

index.js

index.js

333 ms

uaredirect.js

uaredirect.js

317 ms

6ef2690adc11fb0367dff15d321418f8.png

6ef2690adc11fb0367dff15d321418f8.png

324 ms

20fa536ded299fc86e139dd5d3f7729a.png

20fa536ded299fc86e139dd5d3f7729a.png

327 ms

7324c21c7ed63e9f411cae0929ccf683.png

7324c21c7ed63e9f411cae0929ccf683.png

330 ms

5ad7f17c976e0ab450727ac1f127e040.png

5ad7f17c976e0ab450727ac1f127e040.png

337 ms

32d86020a336110afeff2331789193af.png

32d86020a336110afeff2331789193af.png

337 ms

d968b800337bb7ba5911ac2b3a10dc3c.png

d968b800337bb7ba5911ac2b3a10dc3c.png

335 ms

25b2aeb482dd9267a7a228b2f6513c95.png

25b2aeb482dd9267a7a228b2f6513c95.png

338 ms

80010b7a7985cd8f63877bde6a764a48.png

80010b7a7985cd8f63877bde6a764a48.png

341 ms

373e589a00c653daae88da6760e61bc2.png

373e589a00c653daae88da6760e61bc2.png

339 ms

747053f5d6ba3f8a5686125448ed6e56.png

747053f5d6ba3f8a5686125448ed6e56.png

340 ms

media1_cur.jpg

media1_cur.jpg

341 ms

media2_cur.jpg

media2_cur.jpg

343 ms

media3_cur.jpg

media3_cur.jpg

344 ms

media4_cur.jpg

media4_cur.jpg

345 ms

media5_cur.jpg

media5_cur.jpg

345 ms

media6_cur.jpg

media6_cur.jpg

345 ms

media7_cur.jpg

media7_cur.jpg

345 ms

media8_cur.jpg

media8_cur.jpg

347 ms

media9_cur.jpg

media9_cur.jpg

346 ms

media10_cur.jpg

media10_cur.jpg

347 ms

media11_cur.jpg

media11_cur.jpg

348 ms

media12_cur.jpg

media12_cur.jpg

349 ms

h-play-a0.png

h-play-a0.png

349 ms

txt-2021.png

txt-2021.png

349 ms

h-play-a1.jpg

h-play-a1.jpg

350 ms

h-play-a2.jpg

h-play-a2.jpg

104 ms

h-play-a3.jpg

h-play-a3.jpg

77 ms

h-play-a4.jpg

h-play-a4.jpg

68 ms

txt-zx-core.png

txt-zx-core.png

58 ms

h-eat-a1.png

h-eat-a1.png

57 ms

h-eat-a2.png

h-eat-a2.png

45 ms

h-xlxh-ht.png

h-xlxh-ht.png

36 ms

bg-m2.gif

bg-m2.gif

17 ms

Accessibility Review

zx.com accessibility score

76

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

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

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

zx.com SEO score

100

Search Engine Optimization Advices

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

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 Zx.com 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 Zx.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

zx.com

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