Tools & Wizards About Us
hnlx.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hnlx.cn

www.hnlx.cn-官网首页

Page Load Speed

38.9 sec in total

First Response

7.8 sec

Resources Loaded

30.9 sec

Page Rendered

163 ms

hnlx.cn screenshot

About Website

Welcome to hnlx.cn homepage info - get ready to check Hnlx best content right away, or after learning these important things about hnlx.cn

买域名找4.cn-angel.+地球angel4cn

Visit hnlx.cn

Key Findings

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

Performance Metrics

hnlx.cn performance score

0

Network Requests Diagram

hnlx.cn

7769 ms

css.css

2307 ms

epoch_flat_styles.css

967 ms

function.js

955 ms

epoch_classes.js

8068 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 58% of them (43 requests) were addressed to the original Hnlx.cn, 24% (18 requests) were made to Sysimages.tq.cn and 4% (3 requests) were made to Zzsky.cn. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Hnlx.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.0 kB (24%)

Content Size

979.3 kB

After Optimization

747.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hnlx.cn main page is 979.3 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 728.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 54.9 kB

  • Original 66.4 kB
  • After minification 54.9 kB
  • After compression 11.5 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 11.5 kB, which is 17% 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 54.9 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 26.3 kB

  • Original 728.5 kB
  • After minification 702.2 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. Hnlx images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 145.4 kB

  • Original 177.4 kB
  • After minification 144.5 kB
  • After compression 31.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 145.4 kB or 82% of the original size.

CSS Optimization

-75%

Potential reduce by 5.3 kB

  • Original 7.0 kB
  • After minification 6.1 kB
  • After compression 1.7 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. Hnlx.cn needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (39%)

Requests Now

51

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hnlx.cn

hnlx.cn

7769 ms

css.css

css.css

2307 ms

epoch_flat_styles.css

epoch_flat_styles.css

967 ms

function.js

function.js

955 ms

epoch_classes.js

epoch_classes.js

8068 ms

floatcard

floatcard

1223 ms

all_20100501.js

all_20100501.js

2504 ms

as.js

as.js

2157 ms

stat.php

stat.php

2435 ms

mapservice.js

mapservice.js

35 ms

qqonline.gif

qqonline.gif

20417 ms

online_r1_c1.jpg

online_r1_c1.jpg

9077 ms

bg_c1.png

bg_c1.png

5636 ms

xia.jpg

xia.jpg

20415 ms

logo.jpg

logo.jpg

2582 ms

1.gif

1.gif

1748 ms

index_09.jpg

index_09.jpg

2309 ms

index_1-6.jpg

index_1-6.jpg

3487 ms

index1_06.jpg

index1_06.jpg

960 ms

index_36.jpg

index_36.jpg

1423 ms

index_22.jpg

index_22.jpg

8671 ms

index1_10.jpg

index1_10.jpg

2208 ms

index_28.jpg

index_28.jpg

9399 ms

index1_12.jpg

index1_12.jpg

4172 ms

2012425162414.jpg

2012425162414.jpg

3039 ms

index_39.jpg

index_39.jpg

3497 ms

index_11.jpg

index_11.jpg

6407 ms

index1_03.jpg

index1_03.jpg

8680 ms

index_23.jpg

index_23.jpg

4629 ms

20098194916.jpg

20098194916.jpg

10368 ms

index1_13.jpg

index1_13.jpg

12094 ms

index1_15.jpg

index1_15.jpg

19609 ms

index_4.jpg

index_4.jpg

9148 ms

index_31.jpg

index_31.jpg

10347 ms

2015111793321.jpg

2015111793321.jpg

20411 ms

2015111792956.jpg

2015111792956.jpg

20414 ms

2015111392317.jpg

2015111392317.jpg

20415 ms

201041144927.jpg

201041144927.jpg

20417 ms

201041144837.jpg

201041144837.jpg

20417 ms

20104114471.jpg

20104114471.jpg

20418 ms

index_35.jpg

index_35.jpg

20420 ms

accept_c1.png

accept_c1.png

566 ms

message_c1.png

message_c1.png

2582 ms

call_c1.png

call_c1.png

2865 ms

refuse_c1.png

refuse_c1.png

1720 ms

icooff.gif

icooff.gif

1762 ms

off.gif

off.gif

2148 ms

down.gif

down.gif

2436 ms

btm.gif

btm.gif

2346 ms

mini_l.png

mini_l.png

3448 ms

online_r3_c2.jpg

online_r3_c2.jpg

20417 ms

online_r9_c1.jpg

online_r9_c1.jpg

20417 ms

1_01.jpg

1_01.jpg

20412 ms

index0_02.jpg

index0_02.jpg

20411 ms

index_03.jpg

index_03.jpg

20396 ms

index_25.jpg

index_25.jpg

20370 ms

index1_11.gif

index1_11.gif

20371 ms

index_18.jpg

index_18.jpg

20370 ms

index1_10.gif

index1_10.gif

20370 ms

index_34.jpg

index_34.jpg

20371 ms

head.gif

head.gif

5056 ms

body.gif

body.gif

3659 ms

style.css

style.css

3075 ms

style.css

style.css

3360 ms

float.js

float.js

4495 ms

invite.js

invite.js

6407 ms

index_46.jpg

index_46.jpg

20454 ms

stat.htm

stat.htm

170 ms

core.php

core.php

778 ms

9.gif

9.gif

1828 ms

app.gif

app.gif

935 ms

scriptonline.js

scriptonline.js

3255 ms

button_old_41.gif

button_old_41.gif

454 ms

button_old_41.gif

button_old_41.gif

480 ms

SEO Factors

hnlx.cn SEO score

0

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 Hnlx.cn 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 Hnlx.cn 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

hnlx.cn

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