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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

19.9 sec in total

First Response

1.9 sec

Resources Loaded

14.6 sec

Page Rendered

3.5 sec

lhqxinwen.blog.163.com screenshot

About Website

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

Visit lhqxinwen.blog.163.com

Key Findings

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

lhqxinwen.blog.163.com performance score

0

Network Requests Diagram

lhqxinwen.blog.163.com

1859 ms

c.css

19 ms

nb.css

14 ms

yuexiushan_01.jpg

21 ms

yuexiushan_02.jpg

50 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lhqxinwen.blog.163.com, 29% (37 requests) were made to Os.blog.163.com and 25% (31 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (8.9 sec) relates to the external source Os.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 975.9 kB (24%)

Content Size

4.1 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lhqxinwen.blog.163.com main page is 4.1 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. 55% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 176.0 kB

  • Original 211.2 kB
  • After minification 210.7 kB
  • After compression 35.2 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 176.0 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 77.9 kB

  • Original 2.8 MB
  • After minification 2.7 MB

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. Lhqxinwen Blog 163 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 573.7 kB

  • Original 895.9 kB
  • After minification 895.7 kB
  • After compression 322.2 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 573.7 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 148.3 kB

  • Original 181.1 kB
  • After minification 177.3 kB
  • After compression 32.8 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. Lhqxinwen.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.3 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

124

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lhqxinwen.blog.163.com

lhqxinwen.blog.163.com

1859 ms

c.css

c.css

19 ms

nb.css

nb.css

14 ms

yuexiushan_01.jpg

yuexiushan_01.jpg

21 ms

yuexiushan_02.jpg

yuexiushan_02.jpg

50 ms

zhujiang_02.jpg

zhujiang_02.jpg

621 ms

blog_rec.png

blog_rec.png

5 ms

icon.png

icon.png

92 ms

6630133180817252049.jpg

6630133180817252049.jpg

907 ms

xcode.png

xcode.png

81 ms

1.0.0.js

1.0.0.js

520 ms

pc.js

pc.js

78 ms

ph.js

ph.js

77 ms

lnkbar.png

lnkbar.png

17 ms

image.png

image.png

56 ms

arrow24.png

arrow24.png

57 ms

newtopbaricon8.png

newtopbaricon8.png

56 ms

crossdomain.html

crossdomain.html

716 ms

crossdomain.html

crossdomain.html

938 ms

request.s

request.s

908 ms

analyse.png

analyse.png

756 ms

empty.png

empty.png

131 ms

6598116501786516554.jpg

6598116501786516554.jpg

5992 ms

6631411912843669555.jpg

6631411912843669555.jpg

1884 ms

ava.s

ava.s

1443 ms

Photo4BlogBean.getPhotoDailyStatistic.dwr

Photo4BlogBean.getPhotoDailyStatistic.dwr

1238 ms

nb.css

nb.css

53 ms

BlogCircleBean.getUserShowCircles.dwr

BlogCircleBean.getUserShowCircles.dwr

1101 ms

crossdomain.html

crossdomain.html

898 ms

ava.s

ava.s

888 ms

6598162681274884427.jpg

6598162681274884427.jpg

2664 ms

background.gif

background.gif

24 ms

player_02.gif

player_02.gif

41 ms

player_06.gif

player_06.gif

50 ms

player_16.gif

player_16.gif

41 ms

player_17.gif

player_17.gif

40 ms

stopping.gif

stopping.gif

45 ms

player_23.gif

player_23.gif

45 ms

timeline_1.gif

timeline_1.gif

44 ms

player_29.gif

player_29.gif

60 ms

analyse.png

analyse.png

644 ms

analytics.js

analytics.js

30 ms

collect

collect

27 ms

SetupBeanNew.getResourceModulesData.dwr

SetupBeanNew.getResourceModulesData.dwr

774 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

2281 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1107 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

1207 ms

HomeBeanNew.getMonthStatistics.dwr

HomeBeanNew.getMonthStatistics.dwr

1145 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

3265 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1597 ms

BlogBeanNew.getRecentCommentsByOffset.dwr

BlogBeanNew.getRecentCommentsByOffset.dwr

1873 ms

MusicBeanNew.getPlayList.dwr

MusicBeanNew.getPlayList.dwr

3530 ms

BlogBeanNew.getBlogClasses.dwr

BlogBeanNew.getBlogClasses.dwr

2705 ms

PhotoBlogBean.getHeadPic.dwr

PhotoBlogBean.getHeadPic.dwr

1185 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

2040 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

3457 ms

blogPhotoAd

blogPhotoAd

387 ms

close_01.png

close_01.png

7 ms

top_bg.png

top_bg.png

13 ms

bottom_bg.png

bottom_bg.png

17 ms

left_bg.png

left_bg.png

18 ms

right_bg.png

right_bg.png

16 ms

left_top.png

left_top.png

17 ms

right_top.png

right_top.png

18 ms

left_bottom.png

left_bottom.png

21 ms

right_bottom.png

right_bottom.png

22 ms

shadow.png

shadow.png

16 ms

r

r

782 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

3208 ms

112150201114234.js

112150201114234.js

2568 ms

2396759426708184360.jpg

2396759426708184360.jpg

3051 ms

face51.gif

face51.gif

38 ms

face79.gif

face79.gif

37 ms

face50.gif

face50.gif

37 ms

face56.gif

face56.gif

36 ms

ad

ad

731 ms

close2.png

close2.png

10 ms

PhotoBlogBean.getPictureSets75PictureUrl.dwr

PhotoBlogBean.getPictureSets75PictureUrl.dwr

955 ms

ava.s

ava.s

498 ms

ava.s

ava.s

489 ms

ava.s

ava.s

806 ms

ava.s

ava.s

5312 ms

ava.s

ava.s

5204 ms

ava.s

ava.s

1046 ms

ava.s

ava.s

1063 ms

ava.s

ava.s

5399 ms

ava.s

ava.s

1567 ms

ava.s

ava.s

1590 ms

ava.s

ava.s

2052 ms

ava.s

ava.s

2081 ms

ava.s

ava.s

2088 ms

ava.s

ava.s

2507 ms

ava.s

ava.s

4077 ms

ava.s

ava.s

4434 ms

ava.s

ava.s

4411 ms

ava.s

ava.s

4557 ms

ava.s

ava.s

8896 ms

ava.s

ava.s

4918 ms

jquery-1.4.2.js

jquery-1.4.2.js

82 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

1615 ms

1326310090278242401.jpg

1326310090278242401.jpg

1660 ms

2794483568801006579.jpg

2794483568801006579.jpg

852 ms

1586392968758896947.jpg

1586392968758896947.jpg

1295 ms

188306759436885657.jpg

188306759436885657.jpg

976 ms

1563030545691905379.jpg

1563030545691905379.jpg

1277 ms

ava.s

ava.s

5069 ms

ava.s

ava.s

4488 ms

ava.s

ava.s

5851 ms

ava.s

ava.s

5328 ms

ava.s

ava.s

5260 ms

ava.s

ava.s

4970 ms

ava.s

ava.s

5472 ms

ava.s

ava.s

5615 ms

ava.s

ava.s

6648 ms

ava.s

ava.s

7664 ms

ava.s

ava.s

7442 ms

ava.s

ava.s

6182 ms

ava.s

ava.s

7356 ms

ava.s

ava.s

6692 ms

ava.s

ava.s

7018 ms

list_line.gif

list_line.gif

38 ms

-1.gif

-1.gif

886 ms

5497572023157.js

5497572023157.js

526 ms

2577184886779717799.jpg

2577184886779717799.jpg

1510 ms

1997909384792431554.jpg

1997909384792431554.jpg

437 ms

2487957319162707018.jpg

2487957319162707018.jpg

685 ms

SEO Factors

lhqxinwen.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 Lhqxinwen.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 Lhqxinwen.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

lhqxinwen.blog.163.com

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