Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

luhluhl.blog.163.com

涟漪深处 - 涟漪深处 - 网易博客

Page Load Speed

14.1 sec in total

First Response

1.5 sec

Resources Loaded

11.9 sec

Page Rendered

769 ms

About Website

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

【转载】家庭自制养花好肥料【图】,【转载】【花落无息】云樱 -- 仿云落仙仙的圆肩衣,【转载】不再吃垃圾食品,在家炸出肯德基,【转载】最适合春天扦插的15种花,保证活!,【转载】【菲尔手作】云丝珠语---圆肩短袖小衫(美图+真人秀),【转载】自带袖一岸柳,【转载】灰姑娘,【转载】2017.04 藕粉色志田,【转载】【引用九色鹿编织教程】轻烟 经典小v领绅士保暖毛衣 莉诺小马绒,【转载】漂亮的搓板针...

Visit luhluhl.blog.163.com

Key Findings

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

luhluhl.blog.163.com performance score

0

Network Requests Diagram

luhluhl.blog.163.com

1461 ms

c.css

15 ms

b.css

858 ms

6630133180817252049.jpg

658 ms

xcode.png

47 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Luhluhl.blog.163.com, 25% (17 requests) were made to Os.blog.163.com and 18% (12 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (10 sec) relates to the external source Img.bimg.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 608.3 kB (40%)

Content Size

1.5 MB

After Optimization

918.5 kB

In fact, the total size of Luhluhl.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. 30% of websites need less resources to load. Images take 710.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 90.6 kB

  • Original 112.6 kB
  • After minification 112.6 kB
  • After compression 22.0 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 90.6 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 10.1 kB

  • Original 710.6 kB
  • After minification 700.5 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. Luhluhl Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.5 kB

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

CSS Optimization

-82%

Potential reduce by 149.1 kB

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

Requests Breakdown

Number of requests can be reduced by 29 (45%)

Requests Now

64

After Optimization

35

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

SEO Factors

luhluhl.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 Luhluhl.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 Luhluhl.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

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