Tools & Wizards About Us
htzx.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

htzx.org

【华图政信网】政府信赖的民间智库！-华智库,中国智库,调查咨询

Page Load Speed

59.8 sec in total

First Response

1.6 sec

Resources Loaded

58 sec

Page Rendered

187 ms

htzx.org screenshot

About Website

Click here to check amazing Htzx content. Otherwise, check out these important facts you probably never knew about htzx.org

Visit htzx.org

Key Findings

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

Performance Metrics

htzx.org performance score

0

Network Requests Diagram

htzx.org

1610 ms

style.css

2253 ms

index.css

3100 ms

scroll_image_mini.js

2286 ms

jquery-1.7.1.min.js

4069 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 77% of them (58 requests) were addressed to the original Htzx.org, 1% (1 request) were made to Isdspeed.qq.com and 1% (1 request) were made to I.gtimg.cn. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source U1.huatu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.1 kB (44%)

Content Size

418.8 kB

After Optimization

234.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Htzx.org main page is 418.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. 20% of websites need less resources to load. Images take 204.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 31.8 kB

  • Original 37.6 kB
  • After minification 24.9 kB
  • After compression 5.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 12.6 kB, which is 34% 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 31.8 kB or 85% of the original size.

Image Optimization

-16%

Potential reduce by 33.3 kB

  • Original 204.9 kB
  • After minification 171.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, Htzx needs image optimization as it can save up to 33.3 kB or 16% 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 92.4 kB

  • Original 142.9 kB
  • After minification 140.0 kB
  • After compression 50.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 92.4 kB or 65% of the original size.

CSS Optimization

-79%

Potential reduce by 26.6 kB

  • Original 33.5 kB
  • After minification 27.9 kB
  • After compression 6.9 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. Htzx.org needs all CSS files to be minified and compressed as it can save up to 26.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (25%)

Requests Now

67

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

htzx.org

htzx.org

1610 ms

style.css

style.css

2253 ms

index.css

index.css

3100 ms

scroll_image_mini.js

scroll_image_mini.js

2286 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

4069 ms

163css.js

163css.js

2646 ms

jquery-ht.js

jquery-ht.js

3007 ms

pc.js

pc.js

3378 ms

topMenu.js

topMenu.js

3469 ms

mylog.php

mylog.php

643 ms

stat.php

stat.php

894 ms

pinglun.css

pinglun.css

1489 ms

20131227.jpg

20131227.jpg

5854 ms

bj_02.jpg

bj_02.jpg

3695 ms

topmenu.gif

topmenu.gif

1176 ms

bj_03.png

bj_03.png

2325 ms

hzk.jpg

hzk.jpg

2017 ms

shipintp1.jpg

shipintp1.jpg

1280 ms

shipintp2.jpg

shipintp2.jpg

1356 ms

shipintp3.jpg

shipintp3.jpg

3904 ms

wzg.jpg

wzg.jpg

1689 ms

4.jpg

4.jpg

1789 ms

7.jpg

7.jpg

2125 ms

8.jpg

8.jpg

2200 ms

22.jpg

22.jpg

2397 ms

13.jpg

13.jpg

2634 ms

14.jpg

14.jpg

3812 ms

15.jpg

15.jpg

2698 ms

21.jpg

21.jpg

2789 ms

17.jpg

17.jpg

3052 ms

19.jpg

19.jpg

3071 ms

20.jpg

20.jpg

3176 ms

23.jpg

23.jpg

3446 ms

24.jpg

24.jpg

3433 ms

33.jpg

33.jpg

3549 ms

27.jpg

27.jpg

3794 ms

29.jpg

29.jpg

3836 ms

31.jpg

31.jpg

3931 ms

35.jpg

35.jpg

4047 ms

36.jpg

36.jpg

4164 ms

34.jpg

34.jpg

4202 ms

1-6.jpg

1-6.jpg

4228 ms

18.jpg

18.jpg

4299 ms

5.jpg

5.jpg

4313 ms

37.jpg

37.jpg

4424 ms

footer_img%20(1).jpg

footer_img%20(1).jpg

4537 ms

footer_img%20(2).jpg

footer_img%20(2).jpg

4602 ms

footer_img%20(3).jpg

footer_img%20(3).jpg

4664 ms

icon_s.png

icon_s.png

744 ms

footer_img%20(4).jpg

footer_img%20(4).jpg

4667 ms

stat.htm

stat.htm

290 ms

core.php

core.php

1048 ms

9.gif

9.gif

924 ms

pic.gif

pic.gif

794 ms

loginIframe.php

loginIframe.php

1023 ms

htzxwx.jpg

htzxwx.jpg

4523 ms

bj_23.jpg

bj_23.jpg

3537 ms

bj_26.jpg

bj_26.jpg

3560 ms

bj_32.jpg

bj_32.jpg

3305 ms

dian.jpg

dian.jpg

3257 ms

LeftHandle.jpg

LeftHandle.jpg

3038 ms

app.gif

app.gif

1000 ms

RightHandle.jpg

RightHandle.jpg

3037 ms

untitled.png

untitled.png

3062 ms

left.jpg

left.jpg

4271 ms

right.jpg

right.jpg

3034 ms

20131227.jpg

20131227.jpg

20006 ms

r.cgi

r.cgi

1095 ms

ping.js

ping.js

442 ms

cdn_djl.js

cdn_djl.js

465 ms

collect

collect

15475 ms

pingd

pingd

472 ms

cdn_dianjiliu.js

cdn_dianjiliu.js

702 ms

bz.gif

bz.gif

413 ms

0

0

19966 ms

SEO Factors

htzx.org SEO score

0

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 Htzx.org 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 Htzx.org 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

htzx.org

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