Tools & Wizards About Us
weizhiyun2011.blog.163.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

8.9 sec in total

First Response

1.6 sec

Resources Loaded

6.5 sec

Page Rendered

768 ms

weizhiyun2011.blog.163.com screenshot

About Website

Click here to check amazing Weizhiyun 2011 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about weizhiyun2011.blog.163.com

Visit weizhiyun2011.blog.163.com

Key Findings

We analyzed Weizhiyun2011.blog.163.com page load time and found that the first response time was 1.6 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

weizhiyun2011.blog.163.com performance score

0

Network Requests Diagram

weizhiyun2011.blog.163.com

1594 ms

c.css

11 ms

b.css

1780 ms

2662190329746652502.jpg

1342 ms

6597340246516713327.jpg

904 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Weizhiyun2011.blog.163.com, 26% (7 requests) were made to B2.bst.126.net and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.9 sec) relates to the external source Img4.ph.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 571.9 kB (41%)

Content Size

1.4 MB

After Optimization

834.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weizhiyun2011.blog.163.com main page is 1.4 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 644.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 104.1 kB

  • Original 131.9 kB
  • After minification 131.8 kB
  • After compression 27.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 104.1 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 8.6 kB

  • Original 644.1 kB
  • After minification 635.5 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. Weizhiyun 2011 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.3 kB

  • Original 448.7 kB
  • After minification 448.7 kB
  • After compression 138.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 310.3 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 148.9 kB

  • Original 181.7 kB
  • After minification 177.7 kB
  • After compression 32.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. Weizhiyun2011.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (12%)

Requests Now

25

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weizhiyun2011.blog.163.com

weizhiyun2011.blog.163.com

1594 ms

c.css

c.css

11 ms

b.css

b.css

1780 ms

2662190329746652502.jpg

2662190329746652502.jpg

1342 ms

6597340246516713327.jpg

6597340246516713327.jpg

904 ms

1358679712600156958.jpg

1358679712600156958.jpg

2975 ms

6597563447377401869.jpg

6597563447377401869.jpg

2321 ms

6597200608541532295.jpg

6597200608541532295.jpg

3208 ms

6597841623819134593.jpg

6597841623819134593.jpg

1899 ms

6597499675702775864.jpg

6597499675702775864.jpg

4921 ms

6597831728214162986.jpg

6597831728214162986.jpg

2220 ms

6630133180817252049.jpg

6630133180817252049.jpg

815 ms

xcode.png

xcode.png

32 ms

1.0.0.js

1.0.0.js

96 ms

pc.js

pc.js

37 ms

ph.js

ph.js

43 ms

6597357838704044712.jpg

6597357838704044712.jpg

1335 ms

6597626119540134568.jpg

6597626119540134568.jpg

976 ms

blog_rec.png

blog_rec.png

134 ms

icon.png

icon.png

129 ms

lnkbar.png

lnkbar.png

124 ms

image.png

image.png

127 ms

arrow24.png

arrow24.png

127 ms

newtopbaricon8.png

newtopbaricon8.png

126 ms

analyse.png

analyse.png

2187 ms

analytics.js

analytics.js

14 ms

collect

collect

15 ms

SEO Factors

weizhiyun2011.blog.163.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weizhiyun2011.blog.163.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Weizhiyun2011.blog.163.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

weizhiyun2011.blog.163.com

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