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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

readwall.blog.163.com

obsolete - readwall - 网易博客

Page Load Speed

27.1 sec in total

First Response

2.3 sec

Resources Loaded

24.3 sec

Page Rendered

483 ms

readwall.blog.163.com screenshot

About Website

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

us-en,git,用批处理轻松查找和杀掉某个进程,数据库临时表问题,将.jar文件解压到指定目录？,执行jar中的main方法,doma 找不到sql文件错误,JVM调优总结（五）-分代垃圾回收详述1,HTML中的&amp；和URL中的&,论GPRS技术在无线数据通信中的优势,readwall的网易博客,wanna go,

Visit readwall.blog.163.com

Key Findings

We analyzed Readwall.blog.163.com page load time and found that the first response time was 2.3 sec and then it took 24.8 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 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

readwall.blog.163.com performance score

0

Network Requests Diagram

readwall.blog.163.com

2266 ms

c.css

140 ms

nb.css

106 ms

bj.jpg

32 ms

top.jpg

210 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Readwall.blog.163.com, 44% (35 requests) were made to B.bst.126.net and 15% (12 requests) were made to Api.blog.163.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Lofter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 536.6 kB (56%)

Content Size

965.4 kB

After Optimization

428.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 99.9 kB

  • Original 124.8 kB
  • After minification 124.7 kB
  • After compression 24.9 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 99.9 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 9.3 kB

  • Original 241.8 kB
  • After minification 232.4 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. Readwall Blog 163 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 278.6 kB

  • Original 417.1 kB
  • After minification 417.1 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 278.6 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 148.9 kB

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

Requests Breakdown

Number of requests can be reduced by 42 (59%)

Requests Now

71

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

readwall.blog.163.com

readwall.blog.163.com

2266 ms

c.css

c.css

140 ms

nb.css

nb.css

106 ms

bj.jpg

bj.jpg

32 ms

top.jpg

top.jpg

210 ms

button.gif

button.gif

166 ms

nbj.jpg

nbj.jpg

52 ms

a2.gif

a2.gif

162 ms

a1.gif

a1.gif

165 ms

a3.gif

a3.gif

167 ms

b1.gif

b1.gif

165 ms

b3.gif

b3.gif

166 ms

c1.gif

c1.gif

166 ms

c3.gif

c3.gif

167 ms

c2.gif

c2.gif

191 ms

icon.png

icon.png

20 ms

di.jpg

di.jpg

689 ms

lnkbar.png

lnkbar.png

117 ms

6630133180817252049.jpg

6630133180817252049.jpg

12775 ms

image.png

image.png

198 ms

arrow24.png

arrow24.png

206 ms

newtopbaricon8.png

newtopbaricon8.png

22 ms

1.0.0.js

1.0.0.js

103 ms

pc.js

pc.js

70 ms

ph.js

ph.js

60 ms

xcode.png

xcode.png

23 ms

crossdomain.html

crossdomain.html

1449 ms

crossdomain.html

crossdomain.html

923 ms

crossdomain.html

crossdomain.html

4103 ms

request.s

request.s

14473 ms

analyse.png

analyse.png

19874 ms

ava.s

ava.s

804 ms

loftericon.png

loftericon.png

398 ms

Photo4BlogBean.getPhotoDailyStatistic.dwr

Photo4BlogBean.getPhotoDailyStatistic.dwr

1076 ms

nb.css

nb.css

49 ms

ava.s

ava.s

790 ms

background.gif

background.gif

30 ms

player_02.gif

player_02.gif

33 ms

player_06.gif

player_06.gif

32 ms

player_16.gif

player_16.gif

34 ms

player_17.gif

player_17.gif

33 ms

player_23.gif

player_23.gif

32 ms

timeline_1.gif

timeline_1.gif

50 ms

player_29.gif

player_29.gif

51 ms

analyse.png

analyse.png

19579 ms

analytics.js

analytics.js

34 ms

collect

collect

16 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

5087 ms

blogPhotoAd

blogPhotoAd

20396 ms

close_01.png

close_01.png

50 ms

top_bg.png

top_bg.png

51 ms

bottom_bg.png

bottom_bg.png

55 ms

left_bg.png

left_bg.png

55 ms

right_bg.png

right_bg.png

54 ms

left_top.png

left_top.png

52 ms

right_top.png

right_top.png

94 ms

left_bottom.png

left_bottom.png

89 ms

right_bottom.png

right_bottom.png

93 ms

shadow.png

shadow.png

53 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

20310 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

1382 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1399 ms

HomeBeanNew.getMonthStatistics.dwr

HomeBeanNew.getMonthStatistics.dwr

1398 ms

HomeBeanNew.getWeatherCityCode.dwr

HomeBeanNew.getWeatherCityCode.dwr

20206 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

20200 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

4568 ms

BlogBeanNew.getRecentCommentsByOffset.dwr

BlogBeanNew.getRecentCommentsByOffset.dwr

4529 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

4344 ms

ava.s

ava.s

430 ms

ava.s

ava.s

449 ms

ava.s

ava.s

910 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

3935 ms

AlbumBeanNew.getUserSpace.dwr

AlbumBeanNew.getUserSpace.dwr

1065 ms

sniff.png

sniff.png

1320 ms

234195984535501.js

234195984535501.js

759 ms

-1.gif

-1.gif

341 ms

58274123769232.js

58274123769232.js

2617 ms

empty.png

empty.png

53 ms

6597786648239716595.jpg

6597786648239716595.jpg

1307 ms

SEO Factors

readwall.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 Readwall.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 Readwall.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

readwall.blog.163.com

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