Tools & Wizards About Us
go.xungou.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

go.xungou.com

Page Load Speed

8.5 sec in total

First Response

2.3 sec

Resources Loaded

6 sec

Page Rendered

160 ms

go.xungou.com screenshot

About Website

Welcome to go.xungou.com homepage info - get ready to check Go Xungou best content for China right away, or after learning these important things about go.xungou.com

寻购网(原迅购网)是中国领先的网上购物比较购物搜索引擎，是您网络购物的最佳选择

Visit go.xungou.com

Key Findings

We analyzed Go.xungou.com page load time and found that the first response time was 2.3 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

go.xungou.com performance score

0

Network Requests Diagram

go.xungou.com

2345 ms

style.min.css

999 ms

seo.min.css

995 ms

www.min.css

989 ms

header_exp.min.css

986 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 11% of them (2 requests) were addressed to the original Go.xungou.com, 74% (14 requests) were made to Static.xungou.com and 5% (1 request) were made to W.cnzz.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Go.xungou.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.6 kB (70%)

Content Size

208.0 kB

After Optimization

62.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Go.xungou.com main page is 208.0 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. Javascripts take 109.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 30.0 kB

  • Original 38.3 kB
  • After minification 38.0 kB
  • After compression 8.3 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 30.0 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.3 kB
  • After minification 5.3 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. Go Xungou images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 73.4 kB

  • Original 109.8 kB
  • After minification 109.8 kB
  • After compression 36.4 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 73.4 kB or 67% of the original size.

CSS Optimization

-77%

Potential reduce by 42.2 kB

  • Original 54.5 kB
  • After minification 54.5 kB
  • After compression 12.3 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. Go.xungou.com needs all CSS files to be minified and compressed as it can save up to 42.2 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (50%)

Requests Now

18

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

go.xungou.com

go.xungou.com

2345 ms

style.min.css

style.min.css

999 ms

seo.min.css

seo.min.css

995 ms

www.min.css

www.min.css

989 ms

header_exp.min.css

header_exp.min.css

986 ms

jquery.js

jquery.js

988 ms

ajax_func.min.js

ajax_func.min.js

984 ms

json.min.js

json.min.js

993 ms

islogin.min.js

islogin.min.js

1012 ms

weibosearch.min.js

weibosearch.min.js

994 ms

weibo_logo.png

weibo_logo.png

37 ms

xungou_bg_09.gif

xungou_bg_09.gif

33 ms

xungou_bg_018.gif

xungou_bg_018.gif

35 ms

xungou_bt01.gif

xungou_bt01.gif

34 ms

bg.gif

bg.gif

33 ms

c.php

c.php

1621 ms

islogin.php

islogin.php

1371 ms

stat.htm

stat.htm

169 ms

core.php

core.php

1994 ms

SEO Factors

go.xungou.com 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 Go.xungou.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 Go.xungou.com 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

go.xungou.com

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