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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

50.1 sec in total

First Response

12.8 sec

Resources Loaded

35.7 sec

Page Rendered

1.7 sec

witters.blog.163.com screenshot

About Website

Visit witters.blog.163.com now to see the best up-to-date Witters Blog 163 content for China and also check out these interesting facts you probably never knew about witters.blog.163.com

Visit witters.blog.163.com

Key Findings

We analyzed Witters.blog.163.com page load time and found that the first response time was 12.8 sec and then it took 37.3 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 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

witters.blog.163.com performance score

0

Network Requests Diagram

witters.blog.163.com

12766 ms

c.css

166 ms

b.css

3053 ms

6597614024912886920.jpg

2922 ms

6597851519424482953.jpg

19916 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Witters.blog.163.com, 31% (21 requests) were made to Img.bimg.126.net and 15% (10 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img3.ph.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.7 kB (46%)

Content Size

1.2 MB

After Optimization

675.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 94.2 kB

  • Original 124.4 kB
  • After minification 124.4 kB
  • After compression 30.2 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 94.2 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 9.2 kB

  • Original 482.1 kB
  • After minification 472.9 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. Witters 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 152.0 kB

  • Original 185.7 kB
  • After minification 181.6 kB
  • After compression 33.6 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. Witters.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (53%)

Requests Now

62

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Witters 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

witters.blog.163.com

witters.blog.163.com

12766 ms

c.css

c.css

166 ms

b.css

b.css

3053 ms

6597614024912886920.jpg

6597614024912886920.jpg

2922 ms

6597851519424482953.jpg

6597851519424482953.jpg

19916 ms

6597995555447725564.jpg

6597995555447725564.jpg

4349 ms

2614902533659807281.jpg

2614902533659807281.jpg

2784 ms

186336434600264996.jpg

186336434600264996.jpg

2035 ms

2547630014225961452.jpg

2547630014225961452.jpg

1628 ms

3095098843928182821.jpg

3095098843928182821.jpg

1669 ms

2523986116182254676.jpg

2523986116182254676.jpg

893 ms

1542764347368910452.jpg

1542764347368910452.jpg

687 ms

1585830018805644353.jpg

1585830018805644353.jpg

20451 ms

1273674269633534973.jpg

1273674269633534973.jpg

20451 ms

5770799972522187428.jpg

5770799972522187428.jpg

671 ms

5779244221823515636.jpg

5779244221823515636.jpg

661 ms

5779244221823515635.jpg

5779244221823515635.jpg

789 ms

5776992422009831185.jpg

5776992422009831185.jpg

2438 ms

5776992422009831184.jpg

5776992422009831184.jpg

914 ms

5776992422009831186.jpg

5776992422009831186.jpg

6090 ms

5780088646753648775.jpg

5780088646753648775.jpg

1013 ms

5776992422009831187.jpg

5776992422009831187.jpg

8333 ms

5776992422009831188.jpg

5776992422009831188.jpg

1164 ms

5776992422009831189.jpg

5776992422009831189.jpg

1363 ms

5776992422009831191.jpg

5776992422009831191.jpg

6895 ms

5776992422009831190.jpg

5776992422009831190.jpg

2443 ms

5791347645822068511.jpg

5791347645822068511.jpg

4032 ms

5791347645822068509.jpg

5791347645822068509.jpg

2896 ms

5791347645822068513.jpg

5791347645822068513.jpg

2842 ms

5780933071683780524.jpg

5780933071683780524.jpg

7245 ms

icon.png

icon.png

54 ms

6630133180817252049.jpg

6630133180817252049.jpg

10626 ms

xcode.png

xcode.png

148 ms

1.0.0.js

1.0.0.js

545 ms

pc.js

pc.js

197 ms

ph.js

ph.js

197 ms

5791347645822068515.jpg

5791347645822068515.jpg

917 ms

5791347645822068517.jpg

5791347645822068517.jpg

435 ms

5791347645822068546.jpg

5791347645822068546.jpg

784 ms

5791347645822068549.jpg

5791347645822068549.jpg

1243 ms

5791347645822068547.jpg

5791347645822068547.jpg

820 ms

lnkbar.png

lnkbar.png

103 ms

image.png

image.png

108 ms

arrow24.png

arrow24.png

107 ms

newtopbaricon8.png

newtopbaricon8.png

108 ms

crossdomain.html

crossdomain.html

845 ms

crossdomain.html

crossdomain.html

1615 ms

request.s

request.s

2870 ms

analyse.png

analyse.png

2114 ms

crossdomain.html

crossdomain.html

12822 ms

analyse.png

analyse.png

1872 ms

analytics.js

analytics.js

104 ms

collect

collect

57 ms

BlogBeanNew.getBlogClasses.dwr

BlogBeanNew.getBlogClasses.dwr

2206 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

2161 ms

blogPhotoAd

blogPhotoAd

766 ms

close_01.png

close_01.png

39 ms

top_bg.png

top_bg.png

90 ms

bottom_bg.png

bottom_bg.png

88 ms

left_bg.png

left_bg.png

94 ms

right_bg.png

right_bg.png

91 ms

left_top.png

left_top.png

93 ms

right_top.png

right_top.png

89 ms

left_bottom.png

left_bottom.png

127 ms

right_bottom.png

right_bottom.png

126 ms

shadow.png

shadow.png

38 ms

r

r

20003 ms

close2.png

close2.png

64 ms

SEO Factors

witters.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 Witters.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 Witters.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

witters.blog.163.com

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