Tools & Wizards About Us
zzrx.cc screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

zzrx.cc

www.zzrx.cc-官网首页

Page Load Speed

46.6 sec in total

First Response

1.7 sec

Resources Loaded

44.5 sec

Page Rendered

463 ms

zzrx.cc screenshot

About Website

Welcome to zzrx.cc homepage info - get ready to check Zzrx best content right away, or after learning these important things about zzrx.cc

枣庄热线网-12-19年满记录-历史百度权重6

Visit zzrx.cc

Key Findings

We analyzed Zzrx.cc page load time and found that the first response time was 1.7 sec and then it took 44.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. This domain responded with an error, which can significantly jeopardize Zzrx.cc rating and web reputation

Performance Metrics

zzrx.cc performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

99/100

25%

SI (Speed Index)

Value3.1 s

92/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.8 s

100/100

10%

Network Requests Diagram

www.zzrx.cc

1681 ms

style_18_common.css

1921 ms

style.css

838 ms

common.js

1676 ms

portal.js

1099 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 69% of them (93 requests) were addressed to the original Zzrx.cc, 13% (17 requests) were made to Pos.baidu.com and 3% (4 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (15.8 sec) relates to the external source Bbs.weishan.cc.

Page Optimization Overview & Recommendations

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

Content Size

466.4 kB

After Optimization

187.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zzrx.cc main page is 466.4 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. 40% of websites need less resources to load. Javascripts take 299.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 88.3 kB

  • Original 109.0 kB
  • After minification 107.0 kB
  • After compression 20.6 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 88.3 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 873 B

  • Original 58.3 kB
  • After minification 57.4 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. Zzrx images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 190.1 kB

  • Original 299.0 kB
  • After minification 298.8 kB
  • After compression 108.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 190.1 kB or 64% of the original size.

CSS Optimization

-2%

Potential reduce by 4 B

  • Original 208 B
  • After minification 204 B
  • After compression 204 B

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. Zzrx.cc has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (34%)

Requests Now

128

After Optimization

85

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.zzrx.cc

www.zzrx.cc

1681 ms

style_18_common.css

style_18_common.css

1921 ms

style.css

style.css

838 ms

common.js

common.js

1676 ms

portal.js

portal.js

1099 ms

zQH1dSQ

zQH1dSQ

786 ms

logging.js

logging.js

564 ms

c.js

c.js

893 ms

f.js

f.js

913 ms

ping.js

ping.js

2109 ms

discuz_tips.js

discuz_tips.js

464 ms

jquery.SuperSlide.js

jquery.SuperSlide.js

3361 ms

jquery.SuperSlide.js

jquery.SuperSlide.js

1825 ms

bodybg.png

bodybg.png

1543 ms

8acbf6491516797a7ee76175deb61eac.jpg

8acbf6491516797a7ee76175deb61eac.jpg

15778 ms

gzweixin.png

gzweixin.png

349 ms

back.gif

back.gif

336 ms

weixinrwm.jpg

weixinrwm.jpg

677 ms

logo.png

logo.png

540 ms

qq_login.gif

qq_login.gif

588 ms

ad2.png

ad2.png

669 ms

1e10876242b7a99a4f77270e7d1c7d1b.jpg

1e10876242b7a99a4f77270e7d1c7d1b.jpg

1628 ms

0773867a030e4a07f66c25d85f36ef5b.jpg

0773867a030e4a07f66c25d85f36ef5b.jpg

1302 ms

9eb547a19c84bd6e78252a1ee7b6eb4d.jpg

9eb547a19c84bd6e78252a1ee7b6eb4d.jpg

2279 ms

46496d6379dbd1fbfa18beb8648b5b80.jpg

46496d6379dbd1fbfa18beb8648b5b80.jpg

1754 ms

184be0e133c6796930a0dce61d976484.jpg

184be0e133c6796930a0dce61d976484.jpg

1982 ms

dot.gif

dot.gif

2357 ms

f8da03ccc673e373754c24f100ea06cc.jpg

f8da03ccc673e373754c24f100ea06cc.jpg

1811 ms

f5cece2fd12443305def00a44c4cd42e.jpg

f5cece2fd12443305def00a44c4cd42e.jpg

1979 ms

0595d37e82fc84afdcce021d0aff596d.jpg

0595d37e82fc84afdcce021d0aff596d.jpg

2085 ms

fda50c2d1828e93d4183cd61a69d3d2f.jpg

fda50c2d1828e93d4183cd61a69d3d2f.jpg

2095 ms

fe40fb4fa7985889ba0496ac1778061a.jpg

fe40fb4fa7985889ba0496ac1778061a.jpg

2628 ms

01134566631dd83d37436de797f3b9de.jpg

01134566631dd83d37436de797f3b9de.jpg

3424 ms

7d711a12c3ae2bf23992e11da5c5768d.jpg

7d711a12c3ae2bf23992e11da5c5768d.jpg

2909 ms

2e414463c5047ced1ddcad823610a979.jpg

2e414463c5047ced1ddcad823610a979.jpg

3825 ms

cf230628fd3121798df98f4d27f5d231.jpg

cf230628fd3121798df98f4d27f5d231.jpg

3731 ms

be00be1532806033eb0186fa401bd49d.jpg

be00be1532806033eb0186fa401bd49d.jpg

3681 ms

43cbedab6dc7c2436a615cd775950ecb.jpg

43cbedab6dc7c2436a615cd775950ecb.jpg

3180 ms

477c337f01839ab57e40e946ff912dd7.jpg

477c337f01839ab57e40e946ff912dd7.jpg

3453 ms

c1.gif

c1.gif

3689 ms

c2.gif

c2.gif

3847 ms

c3.gif

c3.gif

3960 ms

ncjm

ncjm

713 ms

ncjm

ncjm

918 ms

ncjm

ncjm

888 ms

ncjm

ncjm

867 ms

ncjm

ncjm

912 ms

ncjm

ncjm

891 ms

ncjm

ncjm

1277 ms

MTE4NjMxMDc=.js

MTE4NjMxMDc=.js

320 ms

z_stat.php

z_stat.php

1467 ms

common_extra.js

common_extra.js

4048 ms

c4.gif

c4.gif

3705 ms

c5.gif

c5.gif

3845 ms

ncjm

ncjm

718 ms

ncjm

ncjm

486 ms

ncjm

ncjm

384 ms

ncjm

ncjm

2200 ms

ncjm

ncjm

676 ms

ncjm

ncjm

799 ms

c6.gif

c6.gif

3346 ms

sync.htm

sync.htm

444 ms

ctm3.js

ctm3.js

460 ms

ncjm

ncjm

487 ms

ncjm

ncjm

437 ms

sync.htm

sync.htm

473 ms

c7.gif

c7.gif

3151 ms

stat.htm

stat.htm

248 ms

core.php

core.php

951 ms

c8.gif

c8.gif

3232 ms

sync_pos.htm

sync_pos.htm

342 ms

0f000D3NcMRJfa3hkUN9Q0.jpg

0f000D3NcMRJfa3hkUN9Q0.jpg

2317 ms

0f000DEUfPtZgfoLJj_RRs.jpg

0f000DEUfPtZgfoLJj_RRs.jpg

1846 ms

c9.gif

c9.gif

3239 ms

c10.gif

c10.gif

3215 ms

sync2r.htm

sync2r.htm

1860 ms

noavatar_middle.gif

noavatar_middle.gif

3637 ms

ad7.png

ad7.png

4867 ms

noavatar_middle.gif

noavatar_middle.gif

3624 ms

noavatar_middle.gif

noavatar_middle.gif

3713 ms

noavatar_middle.gif

noavatar_middle.gif

3820 ms

e1e2ce32f2d6fda715783d020ceef784.jpg

e1e2ce32f2d6fda715783d020ceef784.jpg

4270 ms

9.gif

9.gif

1538 ms

pic1.gif

pic1.gif

1234 ms

8f1d31962ff0467184c3ef8cf0317944.jpg

8f1d31962ff0467184c3ef8cf0317944.jpg

4035 ms

noavatar_middle.gif

noavatar_middle.gif

3184 ms

f559bf6baca975bdced15a80b62ba687.jpg

f559bf6baca975bdced15a80b62ba687.jpg

3985 ms

s.htm

s.htm

547 ms

sync.html

sync.html

647 ms

2d503cf3177df65f8dfbcce46676ce71.jpg

2d503cf3177df65f8dfbcce46676ce71.jpg

3894 ms

423a00cfe4b90c3c0b4f8d963804453e.jpg

423a00cfe4b90c3c0b4f8d963804453e.jpg

4209 ms

688df18c0b014f27d94add4b15b7b090.jpg

688df18c0b014f27d94add4b15b7b090.jpg

3765 ms

8ca3b77b8b10a18fea383a4838fd1b51.jpg

8ca3b77b8b10a18fea383a4838fd1b51.jpg

3917 ms

36_avatar_small.jpg

36_avatar_small.jpg

4843 ms

5423423115c8082fd46c547c96689598.jpg

5423423115c8082fd46c547c96689598.jpg

3763 ms

ad_close.gif

ad_close.gif

3828 ms

site_qq.jpg

site_qq.jpg

3878 ms

noavatar_small.gif

noavatar_small.gif

3814 ms

security.png

security.png

3989 ms

noavatar_small.gif

noavatar_small.gif

3927 ms

app.gif

app.gif

1548 ms

dbbj.png

dbbj.png

3754 ms

switch_style.png

switch_style.png

3628 ms

17_avatar_small.jpg

17_avatar_small.jpg

3633 ms

weixinbj.png

weixinbj.png

3780 ms

px.png

px.png

3675 ms

noavatar_small.gif

noavatar_small.gif

3665 ms

noavatar_small.gif

noavatar_small.gif

3622 ms

newarow.gif

newarow.gif

3540 ms

83_avatar_small.jpg

83_avatar_small.jpg

3650 ms

pn.png

pn.png

3660 ms

nv.png

nv.png

3601 ms

noavatar_small.gif

noavatar_small.gif

4001 ms

qmenu.png

qmenu.png

3428 ms

nv_a.png

nv_a.png

3523 ms

01_avatar_small.jpg

01_avatar_small.jpg

3545 ms

18_avatar_small.jpg

18_avatar_small.jpg

3471 ms

sub_nav_bg_1.png

sub_nav_bg_1.png

3021 ms

sub_nav_line.gif

sub_nav_line.gif

2988 ms

nav_icon.png

nav_icon.png

2977 ms

sub_nav_bg_2.png

sub_nav_bg_2.png

2911 ms

search.png

search.png

2929 ms

weiguan_03.jpg

weiguan_03.jpg

2394 ms

baol-tit.jpg

baol-tit.jpg

2360 ms

sm-tit.jpg

sm-tit.jpg

2226 ms

topnub.jpg

topnub.jpg

2165 ms

shtit.jpg

shtit.jpg

2239 ms

pinglu.jpg

pinglu.jpg

2175 ms

yuletit.jpg

yuletit.jpg

2130 ms

qututit.jpg

qututit.jpg

2732 ms

title.png

title.png

2011 ms

scrolltop.png

scrolltop.png

1999 ms

o.htm

o.htm

465 ms

wh.js

wh.js

685 ms

ac.js

ac.js

456 ms

Accessibility Review

zzrx.cc accessibility score

84

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

zzrx.cc best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

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

    EN

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zzrx.cc can be misinterpreted by Google and other search engines. Our service has detected that English 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 Zzrx.cc main page’s claimed encoding is gbk. 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

zzrx.cc

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