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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

20.3 sec in total

First Response

1.5 sec

Resources Loaded

18.4 sec

Page Rendered

362 ms

163caipiao.blog.163.com screenshot

About Website

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

Visit 163caipiao.blog.163.com

Key Findings

We analyzed 163caipiao.blog.163.com page load time and found that the first response time was 1.5 sec and then it took 18.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

163caipiao.blog.163.com performance score

0

Network Requests Diagram

163caipiao.blog.163.com

1538 ms

c.css

10 ms

b.css

13950 ms

6597394122588760334.png

1252 ms

6630133180817252049.jpg

544 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original 163caipiao.blog.163.com, 26% (6 requests) were made to B2.bst.126.net and 17% (4 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (14 sec) relates to the external source Os.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 524.2 kB (35%)

Content Size

1.5 MB

After Optimization

984.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 56.4 kB

  • Original 74.0 kB
  • After minification 74.0 kB
  • After compression 17.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 56.4 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 8.4 kB

  • Original 803.6 kB
  • After minification 795.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. 163 Caipiao Blog 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 149.2 kB

  • Original 182.1 kB
  • After minification 178.1 kB
  • After compression 32.9 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. 163caipiao.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.2 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

22

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 163 Caipiao Blog. 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

163caipiao.blog.163.com

163caipiao.blog.163.com

1538 ms

c.css

c.css

10 ms

b.css

b.css

13950 ms

6597394122588760334.png

6597394122588760334.png

1252 ms

6630133180817252049.jpg

6630133180817252049.jpg

544 ms

xcode.png

xcode.png

11 ms

1.0.0.js

1.0.0.js

90 ms

pc.js

pc.js

16 ms

ph.js

ph.js

18 ms

2190156793885653077.jpg

2190156793885653077.jpg

1596 ms

6598180273401554069.png

6598180273401554069.png

3552 ms

5788251421078518547.jpg

5788251421078518547.jpg

506 ms

icon.png

icon.png

56 ms

5778681271870483770.jpg

5778681271870483770.jpg

3373 ms

5781777496614168722.jpg

5781777496614168722.jpg

523 ms

5778399796893777939.jpg

5778399796893777939.jpg

3200 ms

lnkbar.png

lnkbar.png

53 ms

image.png

image.png

55 ms

arrow24.png

arrow24.png

52 ms

newtopbaricon8.png

newtopbaricon8.png

53 ms

analyse.png

analyse.png

470 ms

analytics.js

analytics.js

12 ms

collect

collect

37 ms

SEO Factors

163caipiao.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 163caipiao.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 163caipiao.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

163caipiao.blog.163.com

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