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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

14.3 sec in total

First Response

1.9 sec

Resources Loaded

12.2 sec

Page Rendered

210 ms

investigation107.blog.163.com screenshot

About Website

Welcome to investigation107.blog.163.com homepage info - get ready to check Investigation 107 Blog 163 best content for China right away, or after learning these important things about investigation107.blog.163.com

Visit investigation107.blog.163.com

Key Findings

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

Performance Metrics

investigation107.blog.163.com performance score

0

Network Requests Diagram

investigation107.blog.163.com

1896 ms

c.css

11 ms

b.css

793 ms

6598090113506608366.jpeg

1968 ms

6631394320657120911.jpeg

1101 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Investigation107.blog.163.com, 20% (10 requests) were made to B.bst.126.net and 18% (9 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (7.6 sec) relates to the external source Os.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 595.9 kB (50%)

Content Size

1.2 MB

After Optimization

603.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Investigation107.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. 40% of websites need less resources to load. Javascripts take 521.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 76.7 kB

  • Original 102.0 kB
  • After minification 102.0 kB
  • After compression 25.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 76.7 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 10.3 kB

  • Original 392.3 kB
  • After minification 382.1 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. Investigation 107 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.6 kB

  • Original 521.7 kB
  • After minification 521.7 kB
  • After compression 163.1 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 358.6 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 150.3 kB

  • Original 183.2 kB
  • After minification 179.2 kB
  • After compression 33.0 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. Investigation107.blog.163.com needs all CSS files to be minified and compressed as it can save up to 150.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (52%)

Requests Now

48

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

investigation107.blog.163.com

investigation107.blog.163.com

1896 ms

c.css

c.css

11 ms

b.css

b.css

793 ms

6598090113506608366.jpeg

6598090113506608366.jpeg

1968 ms

6631394320657120911.jpeg

6631394320657120911.jpeg

1101 ms

6630133180817252049.jpg

6630133180817252049.jpg

1139 ms

6598251741715890882.jpeg

6598251741715890882.jpeg

2590 ms

6598163780785669747.jpeg

6598163780785669747.jpeg

942 ms

6631201906122257023.jpeg

6631201906122257023.jpeg

1591 ms

xcode.png

xcode.png

11 ms

1.0.0.js

1.0.0.js

394 ms

pc.js

pc.js

17 ms

ph.js

ph.js

17 ms

5124814900987959740.jpg

5124814900987959740.jpg

2613 ms

blog_rec.png

blog_rec.png

72 ms

icon.png

icon.png

68 ms

lnkbar.png

lnkbar.png

68 ms

image.png

image.png

67 ms

arrow24.png

arrow24.png

68 ms

newtopbaricon8.png

newtopbaricon8.png

68 ms

crossdomain.html

crossdomain.html

844 ms

crossdomain.html

crossdomain.html

1225 ms

crossdomain.html

crossdomain.html

1085 ms

request.s

request.s

999 ms

analyse.png

analyse.png

3379 ms

ava.s

ava.s

7572 ms

loftericon.png

loftericon.png

395 ms

analyse.png

analyse.png

2105 ms

analytics.js

analytics.js

12 ms

collect

collect

12 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

892 ms

BlogBeanNew.getRecentCommentsByOffset.dwr

BlogBeanNew.getRecentCommentsByOffset.dwr

3348 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1010 ms

blogPhotoAd

blogPhotoAd

1091 ms

close_01.png

close_01.png

4 ms

top_bg.png

top_bg.png

9 ms

bottom_bg.png

bottom_bg.png

15 ms

left_bg.png

left_bg.png

14 ms

right_bg.png

right_bg.png

12 ms

left_top.png

left_top.png

14 ms

right_top.png

right_top.png

16 ms

left_bottom.png

left_bottom.png

17 ms

right_bottom.png

right_bottom.png

15 ms

shadow.png

shadow.png

16 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

2069 ms

r

r

1289 ms

close2.png

close2.png

3 ms

ad

ad

2363 ms

jquery-1.4.2.js

jquery-1.4.2.js

814 ms

0316ykt-300-250.jpg

0316ykt-300-250.jpg

2679 ms

SEO Factors

investigation107.blog.163.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    ZH

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Investigation107.blog.163.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), while the claimed language is Chinese. Our system also found out that Investigation107.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

investigation107.blog.163.com

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