Tools & Wizards About Us
caizhaizu.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

caizhaizu.com

403 Not Found

Page Load Speed

78.3 sec in total

First Response

12.1 sec

Resources Loaded

65.4 sec

Page Rendered

828 ms

caizhaizu.com screenshot

About Website

Click here to check amazing Caizhaizu content. Otherwise, check out these important facts you probably never knew about caizhaizu.com

首页

Visit caizhaizu.com

Key Findings

We analyzed Caizhaizu.com page load time and found that the first response time was 12.1 sec and then it took 66.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 27 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

caizhaizu.com performance score

0

Network Requests Diagram

www.caizhaizu.com

12096 ms

style_2_common.css

4219 ms

style_2_portal_index.css

627 ms

common.js

5398 ms

portal.js

5683 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 65% of them (70 requests) were addressed to the original Caizhaizu.com, 7% (8 requests) were made to W220798.s16.myverydz.com and 6% (6 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Caizhaizu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 382.4 kB (32%)

Content Size

1.2 MB

After Optimization

810.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Caizhaizu.com main page is 1.2 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. 25% of websites need less resources to load. Images take 758.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 87.7 kB

  • Original 107.4 kB
  • After minification 105.9 kB
  • After compression 19.7 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 87.7 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 84.4 kB

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

JavaScript Optimization

-65%

Potential reduce by 210.3 kB

  • Original 325.8 kB
  • After minification 303.4 kB
  • After compression 115.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 210.3 kB or 65% of the original size.

CSS Optimization

-1%

Potential reduce by 22 B

  • Original 2.1 kB
  • After minification 2.1 kB
  • After compression 2.1 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. Caizhaizu.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (44%)

Requests Now

79

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.caizhaizu.com

www.caizhaizu.com

12096 ms

style_2_common.css

style_2_common.css

4219 ms

style_2_portal_index.css

style_2_portal_index.css

627 ms

common.js

common.js

5398 ms

portal.js

portal.js

5683 ms

logging.js

logging.js

1351 ms

comiis.css

comiis.css

7336 ms

comiis.js

comiis.js

2166 ms

c.js

c.js

1110 ms

ping.js

ping.js

546 ms

discuz_tips.js

discuz_tips.js

742 ms

be077bda-83e5-42a1-9cae-6da5abf99dac.js

be077bda-83e5-42a1-9cae-6da5abf99dac.js

5489 ms

type-button-5.jpg

type-button-5.jpg

1156 ms

mainbg6.jpg

mainbg6.jpg

1820 ms

comiis_tbg.jpg

comiis_tbg.jpg

1818 ms

comiis_logo.gif

comiis_logo.gif

4224 ms

201351x9zyfffytyc9q293.jpg

201351x9zyfffytyc9q293.jpg

19040 ms

ad06.gif

ad06.gif

1778 ms

ad07.gif

ad07.gif

3506 ms

jiuwangzhuang.jpg

jiuwangzhuang.jpg

4517 ms

5cd861fd796633f84a9de95792c614f3.jpg

5cd861fd796633f84a9de95792c614f3.jpg

19883 ms

b6fdece0d61ba6b066698d28f2eccf45.jpg

b6fdece0d61ba6b066698d28f2eccf45.jpg

19883 ms

f152e0a4438e279a9efbbdbfa09984db.jpg

f152e0a4438e279a9efbbdbfa09984db.jpg

10465 ms

0faf38a39b5331660bfc982bd348c8c4.jpg

0faf38a39b5331660bfc982bd348c8c4.jpg

11064 ms

94dd8bea18eca650c1a5dfae9fc703c4.jpg

94dd8bea18eca650c1a5dfae9fc703c4.jpg

11423 ms

7603c2270d3720f2a2f05e926b3fd705.jpg

7603c2270d3720f2a2f05e926b3fd705.jpg

10951 ms

ad010.gif

ad010.gif

15562 ms

ad011.gif

ad011.gif

11581 ms

ad012.jpg

ad012.jpg

11915 ms

ad013.gif

ad013.gif

16181 ms

4eb1c1c127d0e1c4036cb61f899c83fa.jpg

4eb1c1c127d0e1c4036cb61f899c83fa.jpg

19879 ms

3e08ce0520d73a32c1f7f24a338446c3.jpg

3e08ce0520d73a32c1f7f24a338446c3.jpg

19879 ms

4bb8bf067928efc16aceafc6de567389.jpg

4bb8bf067928efc16aceafc6de567389.jpg

19885 ms

4a69cf1a91dd640b5deb02c8f7127cf8.jpg

4a69cf1a91dd640b5deb02c8f7127cf8.jpg

19888 ms

650280fe055716cfc2dc607b90966a94.jpg

650280fe055716cfc2dc607b90966a94.jpg

19890 ms

3da80b687f9a9ae0e916d0e910856058.jpg

3da80b687f9a9ae0e916d0e910856058.jpg

19893 ms

405dde5aa3253b8fec6d4d1493510d5b.jpg

405dde5aa3253b8fec6d4d1493510d5b.jpg

19898 ms

a95e306f5b0bae76bf90e6c721772558.jpg

a95e306f5b0bae76bf90e6c721772558.jpg

19899 ms

4ecb478f0e78165a6521a76b1438b0bf.jpg

4ecb478f0e78165a6521a76b1438b0bf.jpg

19901 ms

af498b1e3a39fb8ce79147d92c174533.jpg

af498b1e3a39fb8ce79147d92c174533.jpg

19902 ms

57b2a2d45e598e1b5d2b235a40d0c6ac.jpg

57b2a2d45e598e1b5d2b235a40d0c6ac.jpg

19902 ms

adl.jpg

adl.jpg

19904 ms

adr.jpg

adr.jpg

19904 ms

ad019.gif

ad019.gif

19904 ms

0c8a8e0a252a224b1042b142ed0aabb4.jpg

0c8a8e0a252a224b1042b142ed0aabb4.jpg

19905 ms

361278e891cfd764ff24430d4435da61.jpg

361278e891cfd764ff24430d4435da61.jpg

19905 ms

79faad6f82721745090d4f255db0c917.jpg

79faad6f82721745090d4f255db0c917.jpg

19907 ms

ad020.jpg

ad020.jpg

19892 ms

noavatar_small.gif

noavatar_small.gif

1492 ms

noavatar_small.gif

noavatar_small.gif

1804 ms

28_avatar_small.jpg

28_avatar_small.jpg

1804 ms

noavatar_small.gif

noavatar_small.gif

2104 ms

common_extra.js

common_extra.js

20219 ms

ocdm

ocdm

772 ms

shell_v2.js

shell_v2.js

388 ms

ad021.gif

ad021.gif

18834 ms

ad024.gif

ad024.gif

20070 ms

ocdm

ocdm

982 ms

security.png

security.png

20057 ms

noavatar_small.gif

noavatar_small.gif

5720 ms

noavatar_small.gif

noavatar_small.gif

1703 ms

bds_s_v2.js

bds_s_v2.js

953 ms

noavatar_small.gif

noavatar_small.gif

1823 ms

ocdm

ocdm

613 ms

toss_11.gif

toss_11.gif

299 ms

MjI4OTMyNjI=.js

MjI4OTMyNjI=.js

633 ms

h.js

h.js

809 ms

ocdm

ocdm

612 ms

sync.htm

sync.htm

2249 ms

ctm3.js

ctm3.js

574 ms

bdsstyle.css

bdsstyle.css

395 ms

getnum

getnum

1830 ms

www.ailab.org.gif

www.ailab.org.gif

20378 ms

sc.png

sc.png

505 ms

21.gif

21.gif

777 ms

hm.gif

hm.gif

1705 ms

noavatar_small.gif

noavatar_small.gif

4955 ms

logger.js

logger.js

865 ms

0f000a-Jue0OKE6TOLDxOs.jpg

0f000a-Jue0OKE6TOLDxOs.jpg

1042 ms

comiis_bodybg.jpg

comiis_bodybg.jpg

17432 ms

px.png

px.png

20363 ms

sync_pos.htm

sync_pos.htm

380 ms

sync2r.htm

sync2r.htm

940 ms

newarow.gif

newarow.gif

15118 ms

comiis_dlan.gif

comiis_dlan.gif

11580 ms

nv.png

nv.png

11514 ms

qmenu.png

qmenu.png

11232 ms

nv_a.png

nv_a.png

11693 ms

comiis_navbg.jpg

comiis_navbg.jpg

11389 ms

nav_ico01.jpg

nav_ico01.jpg

8456 ms

nav_ico02.jpg

nav_ico02.jpg

17900 ms

nav_ico03.jpg

nav_ico03.jpg

5619 ms

nav_ico04.jpg

nav_ico04.jpg

4868 ms

search.png

search.png

19998 ms

arrwd.gif

arrwd.gif

5527 ms

body.gif

body.gif

14820 ms

boxbg.jpg

boxbg.jpg

6187 ms

borderbg.jpg

borderbg.jpg

6847 ms

tabs01.jpg

tabs01.jpg

19976 ms

borderbg01.jpg

borderbg01.jpg

7463 ms

titlebg.jpg

titlebg.jpg

8367 ms

borderbg03.jpg

borderbg03.jpg

10074 ms

scrolltop.png

scrolltop.png

11949 ms

o.htm

o.htm

1217 ms

hm.gif

hm.gif

759 ms

ac.js

ac.js

675 ms

wh.js

wh.js

1856 ms

SEO Factors

caizhaizu.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Caizhaizu.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Caizhaizu.com 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

caizhaizu.com

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