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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

11.9 sec in total

First Response

2.9 sec

Resources Loaded

8.7 sec

Page Rendered

346 ms

wodenvhair.blog.163.com screenshot

About Website

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

Visit wodenvhair.blog.163.com

Key Findings

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

Performance Metrics

wodenvhair.blog.163.com performance score

0

Network Requests Diagram

wodenvhair.blog.163.com

2851 ms

c.css

477 ms

b.css

3009 ms

6630133180817252049.jpg

1437 ms

xcode.png

492 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 Wodenvhair.blog.163.com, 41% (11 requests) were made to Img.bimg.126.net and 22% (6 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Img.bimg.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 529.1 kB (63%)

Content Size

846.0 kB

After Optimization

316.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wodenvhair.blog.163.com main page is 846.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. 35% of websites need less resources to load. Javascripts take 448.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 60.5 kB

  • Original 76.1 kB
  • After minification 76.1 kB
  • After compression 15.6 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 60.5 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 8.4 kB

  • Original 138.3 kB
  • After minification 129.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. Wodenvhair Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.4 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.4 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.8 kB

  • Original 182.9 kB
  • After minification 179.0 kB
  • After compression 33.1 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. Wodenvhair.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (62%)

Requests Now

26

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

wodenvhair.blog.163.com

wodenvhair.blog.163.com

2851 ms

c.css

c.css

477 ms

b.css

b.css

3009 ms

6630133180817252049.jpg

6630133180817252049.jpg

1437 ms

xcode.png

xcode.png

492 ms

1.0.0.js

1.0.0.js

525 ms

pc.js

pc.js

16 ms

ph.js

ph.js

214 ms

5772207347405742436.jpg

5772207347405742436.jpg

2074 ms

icon.png

icon.png

35 ms

5791066170845357749.jpg

5791066170845357749.jpg

1566 ms

5791066170845357824.jpg

5791066170845357824.jpg

1047 ms

5791066170845357823.jpg

5791066170845357823.jpg

1083 ms

5791066170845357826.jpg

5791066170845357826.jpg

2740 ms

5772207347405742474.jpg

5772207347405742474.jpg

1568 ms

5791066170845357828.jpg

5791066170845357828.jpg

3270 ms

5791066170845357830.jpg

5791066170845357830.jpg

2050 ms

5791066170845357832.jpg

5791066170845357832.jpg

2090 ms

5791066170845357836.jpg

5791066170845357836.jpg

2090 ms

5791066170845357834.jpg

5791066170845357834.jpg

2573 ms

lnkbar.png

lnkbar.png

31 ms

image.png

image.png

32 ms

arrow24.png

arrow24.png

32 ms

newtopbaricon8.png

newtopbaricon8.png

33 ms

analyse.png

analyse.png

1211 ms

analytics.js

analytics.js

7 ms

collect

collect

13 ms

SEO Factors

wodenvhair.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 Wodenvhair.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 Wodenvhair.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

wodenvhair.blog.163.com

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