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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

37.3 sec in total

First Response

7.4 sec

Resources Loaded

29.3 sec

Page Rendered

590 ms

lcxwblog.blog.163.com screenshot

About Website

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

Visit lcxwblog.blog.163.com

Key Findings

We analyzed Lcxwblog.blog.163.com page load time and found that the first response time was 7.4 sec and then it took 29.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

lcxwblog.blog.163.com performance score

0

Network Requests Diagram

lcxwblog.blog.163.com

7352 ms

c.css

31 ms

b.css

3191 ms

5770799972522187428.jpg

2915 ms

icon.png

119 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Lcxwblog.blog.163.com, 26% (21 requests) were made to Img.bimg.126.net and 20% (16 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Img.ph.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 521.2 kB (65%)

Content Size

800.0 kB

After Optimization

278.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 46.6 kB

  • Original 60.7 kB
  • After minification 60.7 kB
  • After compression 14.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 46.6 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 12.1 kB

  • Original 104.6 kB
  • After minification 92.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. Obviously, Lcxwblog Blog 163 needs image optimization as it can save up to 12.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 310.5 kB

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

CSS Optimization

-82%

Potential reduce by 152.0 kB

  • Original 185.7 kB
  • After minification 181.6 kB
  • After compression 33.6 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. Lcxwblog.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

76

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lcxwblog.blog.163.com

lcxwblog.blog.163.com

7352 ms

c.css

c.css

31 ms

b.css

b.css

3191 ms

5770799972522187428.jpg

5770799972522187428.jpg

2915 ms

icon.png

icon.png

119 ms

6630133180817252049.jpg

6630133180817252049.jpg

19986 ms

xcode.png

xcode.png

211 ms

1.0.0.js

1.0.0.js

223 ms

pc.js

pc.js

241 ms

ph.js

ph.js

309 ms

lnkbar.png

lnkbar.png

151 ms

image.png

image.png

157 ms

arrow24.png

arrow24.png

168 ms

newtopbaricon8.png

newtopbaricon8.png

156 ms

5779244221823515636.jpg

5779244221823515636.jpg

909 ms

5779244221823515635.jpg

5779244221823515635.jpg

604 ms

5791347645822068511.jpg

5791347645822068511.jpg

660 ms

5791347645822068509.jpg

5791347645822068509.jpg

858 ms

5791347645822068513.jpg

5791347645822068513.jpg

1751 ms

5780933071683780524.jpg

5780933071683780524.jpg

2223 ms

5791347645822068515.jpg

5791347645822068515.jpg

1331 ms

5791347645822068517.jpg

5791347645822068517.jpg

1229 ms

5791347645822068546.jpg

5791347645822068546.jpg

1554 ms

5791347645822068549.jpg

5791347645822068549.jpg

1778 ms

5791347645822068547.jpg

5791347645822068547.jpg

1733 ms

5776992422009831185.jpg

5776992422009831185.jpg

1869 ms

5776992422009831184.jpg

5776992422009831184.jpg

2115 ms

5776992422009831186.jpg

5776992422009831186.jpg

2063 ms

5780088646753648775.jpg

5780088646753648775.jpg

2198 ms

5776992422009831187.jpg

5776992422009831187.jpg

2183 ms

5776992422009831188.jpg

5776992422009831188.jpg

2357 ms

5776992422009831189.jpg

5776992422009831189.jpg

2476 ms

5776992422009831191.jpg

5776992422009831191.jpg

2569 ms

5776992422009831190.jpg

5776992422009831190.jpg

2504 ms

crossdomain.html

crossdomain.html

879 ms

crossdomain.html

crossdomain.html

661 ms

crossdomain.html

crossdomain.html

2055 ms

request.s

request.s

985 ms

analyse.png

analyse.png

929 ms

ava.s

ava.s

19626 ms

loftericon.png

loftericon.png

802 ms

ava.s

ava.s

2186 ms

analyse.png

analyse.png

1132 ms

analytics.js

analytics.js

26 ms

collect

collect

59 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

915 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1159 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1289 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1315 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

6804 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1770 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1919 ms

blogPhotoAd

blogPhotoAd

463 ms

close_01.png

close_01.png

36 ms

top_bg.png

top_bg.png

39 ms

bottom_bg.png

bottom_bg.png

38 ms

left_bg.png

left_bg.png

39 ms

right_bg.png

right_bg.png

38 ms

left_top.png

left_top.png

39 ms

right_top.png

right_top.png

39 ms

left_bottom.png

left_bottom.png

40 ms

right_bottom.png

right_bottom.png

40 ms

shadow.png

shadow.png

35 ms

r

r

19734 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

971 ms

ava.s

ava.s

486 ms

ava.s

ava.s

828 ms

ava.s

ava.s

843 ms

ava.s

ava.s

937 ms

ava.s

ava.s

1021 ms

ava.s

ava.s

1236 ms

ava.s

ava.s

1261 ms

ava.s

ava.s

1475 ms

ava.s

ava.s

1516 ms

ava.s

ava.s

1634 ms

ava.s

ava.s

1665 ms

ava.s

ava.s

1792 ms

close2.png

close2.png

89 ms

ava.s

ava.s

392 ms

face140.png

face140.png

49 ms

SEO Factors

lcxwblog.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 Lcxwblog.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 Lcxwblog.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

lcxwblog.blog.163.com

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