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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

19.4 sec in total

First Response

5.8 sec

Resources Loaded

13.5 sec

Page Rendered

217 ms

lizhang515025.blog.163.com screenshot

About Website

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

Visit lizhang515025.blog.163.com

Key Findings

We analyzed Lizhang515025.blog.163.com page load time and found that the first response time was 5.8 sec and then it took 13.7 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

lizhang515025.blog.163.com performance score

0

Network Requests Diagram

lizhang515025.blog.163.com

5767 ms

c.css

986 ms

b.css

836 ms

5781777496613668265.jpg

5534 ms

5782621921543800209.jpg

8328 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 564.1 kB (44%)

Content Size

1.3 MB

After Optimization

730.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lizhang515025.blog.163.com main page is 1.3 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. Images take 545.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 95.8 kB

  • Original 117.8 kB
  • After minification 117.8 kB
  • After compression 22.1 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 95.8 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 8.4 kB

  • Original 545.8 kB
  • After minification 537.3 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. Lizhang 515025 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.5 kB

  • Original 182.6 kB
  • After minification 178.7 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. Lizhang515025.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.5 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

lizhang515025.blog.163.com

lizhang515025.blog.163.com

5767 ms

c.css

c.css

986 ms

b.css

b.css

836 ms

5781777496613668265.jpg

5781777496613668265.jpg

5534 ms

5782621921543800209.jpg

5782621921543800209.jpg

8328 ms

5782621921543800253.jpg

5782621921543800253.jpg

2335 ms

5779244221823300646.jpg

5779244221823300646.jpg

4406 ms

5781777496613668331.jpg

5781777496613668331.jpg

1651 ms

5782621921543800348.jpg

5782621921543800348.jpg

1651 ms

5782621921543800347.jpg

5782621921543800347.jpg

4386 ms

icon.png

icon.png

25 ms

6630133180817252049.jpg

6630133180817252049.jpg

2149 ms

xcode.png

xcode.png

1374 ms

1.0.0.js

1.0.0.js

2197 ms

pc.js

pc.js

25 ms

ph.js

ph.js

24 ms

lnkbar.png

lnkbar.png

20 ms

image.png

image.png

22 ms

arrow24.png

arrow24.png

21 ms

newtopbaricon8.png

newtopbaricon8.png

22 ms

5779244221823300628.jpg

5779244221823300628.jpg

3788 ms

analyse.png

analyse.png

2106 ms

analytics.js

analytics.js

4 ms

collect

collect

12 ms

SEO Factors

lizhang515025.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 Lizhang515025.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 Lizhang515025.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

lizhang515025.blog.163.com

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