Tools & Wizards About Us
168reg.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

168reg.cn

404

Page Load Speed

25.6 sec in total

First Response

1.9 sec

Resources Loaded

23.5 sec

Page Rendered

183 ms

168reg.cn screenshot

About Website

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

Visit 168reg.cn

Key Findings

We analyzed 168reg.cn page load time and found that the first response time was 1.9 sec and then it took 23.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

168reg.cn performance score

0

Network Requests Diagram

168reg.cn

1872 ms

style.css

948 ms

top.js

1122 ms

news.js

715 ms

copyright.js

1758 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 93% of them (70 requests) were addressed to the original 168reg.cn, 5% (4 requests) were made to Pub.idqqimg.com and 1% (1 request) were made to Merchant.168reg.cn. The less responsive or slowest element that took the longest time to load (12 sec) belongs to the original domain 168reg.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.0 kB (80%)

Content Size

49.7 kB

After Optimization

9.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of 168reg.cn main page is 49.7 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. HTML takes 37.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 30.8 kB

  • Original 37.6 kB
  • After minification 31.2 kB
  • After compression 6.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 6.4 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 30.8 kB or 82% of the original size.

JavaScript Optimization

-76%

Potential reduce by 8.9 kB

  • Original 11.7 kB
  • After minification 11.5 kB
  • After compression 2.8 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 8.9 kB or 76% of the original size.

CSS Optimization

-67%

Potential reduce by 275 B

  • Original 411 B
  • After minification 306 B
  • After compression 136 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. 168reg.cn needs all CSS files to be minified and compressed as it can save up to 275 B or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (22%)

Requests Now

74

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

168reg.cn

168reg.cn

1872 ms

style.css

style.css

948 ms

top.js

top.js

1122 ms

news.js

news.js

715 ms

copyright.js

copyright.js

1758 ms

partner.asp

partner.asp

1678 ms

getcode.asp

getcode.asp

4023 ms

ads4.gif

ads4.gif

10084 ms

hexi_bg.gif

hexi_bg.gif

720 ms

hexi_title12.gif

hexi_title12.gif

738 ms

hexi_main1.gif

hexi_main1.gif

3258 ms

hexi_main2.gif

hexi_main2.gif

1264 ms

hexi_main3.gif

hexi_main3.gif

1295 ms

hexi_main4.gif

hexi_main4.gif

1712 ms

payvia_01.gif

payvia_01.gif

2148 ms

payvia_02.gif

payvia_02.gif

3156 ms

payvia_04.gif

payvia_04.gif

1846 ms

payvia_07.gif

payvia_07.gif

4194 ms

payvia_08.gif

payvia_08.gif

3874 ms

payvia_17.gif

payvia_17.gif

2606 ms

payvia_12.gif

payvia_12.gif

4254 ms

payvia_13.gif

payvia_13.gif

5145 ms

payvia_14.gif

payvia_14.gif

9780 ms

hexi_main7.gif

hexi_main7.gif

4435 ms

hexi_main11.gif

hexi_main11.gif

6818 ms

hexi_ka.gif

hexi_ka.gif

4697 ms

hexi_main13.gif

hexi_main13.gif

4987 ms

hexi_main14.gif

hexi_main14.gif

5150 ms

hexi_main15.gif

hexi_main15.gif

5548 ms

logo001.gif

logo001.gif

7143 ms

logo_skycn.gif

logo_skycn.gif

6038 ms

logo_sharebank.gif

logo_sharebank.gif

6100 ms

logo_cqvip.gif

logo_cqvip.gif

7710 ms

logo_789vr.gif

logo_789vr.gif

7214 ms

logo_68173.gif

logo_68173.gif

9392 ms

logo009.gif

logo009.gif

8223 ms

logo006.gif

logo006.gif

10326 ms

logo012.gif

logo012.gif

9112 ms

hexi_titlebg.gif

hexi_titlebg.gif

9383 ms

title_01.gif

title_01.gif

9919 ms

title_02.gif

title_02.gif

9814 ms

hexi_title4.gif

hexi_title4.gif

10587 ms

hexi_title3-1.gif

hexi_title3-1.gif

9394 ms

hexi_title3.gif

hexi_title3.gif

12041 ms

hexi_button1.gif

hexi_button1.gif

10006 ms

hexi_button2.gif

hexi_button2.gif

9388 ms

hexi_button3.gif

hexi_button3.gif

9391 ms

hexi_button4.gif

hexi_button4.gif

9593 ms

hexi_button5.gif

hexi_button5.gif

9478 ms

hexi_title5.gif

hexi_title5.gif

9353 ms

hexi_title6_01.gif

hexi_title6_01.gif

10043 ms

hexi_title6_02.gif

hexi_title6_02.gif

8831 ms

hexi_title8.gif

hexi_title8.gif

9586 ms

hexi_title9.gif

hexi_title9.gif

8446 ms

hexi_title10.gif

hexi_title10.gif

9778 ms

hexi_title11.gif

hexi_title11.gif

7764 ms

hexi_main6.gif

hexi_main6.gif

8441 ms

news.gif

news.gif

8036 ms

hexi_main10.gif

hexi_main10.gif

7993 ms

biaoshi.gif

biaoshi.gif

8000 ms

kefu_up.gif

kefu_up.gif

8052 ms

kefu_middle.gif

kefu_middle.gif

8040 ms

kefu_down1.gif

kefu_down1.gif

7594 ms

button_old_41.gif

button_old_41.gif

674 ms

button_old_41.gif

button_old_41.gif

648 ms

button_old_41.gif

button_old_41.gif

969 ms

button_old_41.gif

button_old_41.gif

931 ms

hexi_button1b.gif

hexi_button1b.gif

1184 ms

hexi_button2b.gif

hexi_button2b.gif

549 ms

hexi_button3b.gif

hexi_button3b.gif

2503 ms

hexi_button4b.gif

hexi_button4b.gif

1916 ms

hexi_button5b.gif

hexi_button5b.gif

3312 ms

hexi_main1_02.gif

hexi_main1_02.gif

2036 ms

hexi_main2_02.gif

hexi_main2_02.gif

1095 ms

hexi_main3_02.gif

hexi_main3_02.gif

1649 ms

SEO Factors

168reg.cn SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 168reg.cn 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 168reg.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

168reg.cn

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