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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

24.6 sec in total

First Response

1.4 sec

Resources Loaded

22.2 sec

Page Rendered

1 sec

jiongwen.blog.163.com screenshot

About Website

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

Visit jiongwen.blog.163.com

Key Findings

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

Performance Metrics

jiongwen.blog.163.com performance score

0

Network Requests Diagram

jiongwen.blog.163.com

1393 ms

c.css

21 ms

b.css

790 ms

6630133180817252049.jpg

1601 ms

xcode.png

158 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jiongwen.blog.163.com, 36% (27 requests) were made to B.bst.126.net and 11% (8 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Os.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 638.6 kB (55%)

Content Size

1.2 MB

After Optimization

530.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jiongwen.blog.163.com main page is 1.2 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. Javascripts take 543.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 104.3 kB

  • Original 133.4 kB
  • After minification 131.9 kB
  • After compression 29.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 104.3 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 11.4 kB

  • Original 306.6 kB
  • After minification 295.2 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. Jiongwen Blog 163 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 371.7 kB

  • Original 543.8 kB
  • After minification 543.8 kB
  • After compression 172.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 371.7 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 151.2 kB

  • Original 184.8 kB
  • After minification 180.7 kB
  • After compression 33.5 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. Jiongwen.blog.163.com needs all CSS files to be minified and compressed as it can save up to 151.2 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

72

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

jiongwen.blog.163.com

jiongwen.blog.163.com

1393 ms

c.css

c.css

21 ms

b.css

b.css

790 ms

6630133180817252049.jpg

6630133180817252049.jpg

1601 ms

xcode.png

xcode.png

158 ms

1.0.0.js

1.0.0.js

222 ms

pc.js

pc.js

162 ms

ph.js

ph.js

159 ms

5770518497545593941.jpg

5770518497545593941.jpg

607 ms

icon.png

icon.png

154 ms

5780933071683898331.jpg

5780933071683898331.jpg

5260 ms

5780933071683898330.jpg

5780933071683898330.jpg

3163 ms

5780933071683898375.jpg

5780933071683898375.jpg

676 ms

5780933071683898329.jpg

5780933071683898329.jpg

4649 ms

5770518497545593887.jpg

5770518497545593887.jpg

2235 ms

5788532896055036664.jpg

5788532896055036664.jpg

2108 ms

5780933071683898345.jpg

5780933071683898345.jpg

2756 ms

lnkbar.png

lnkbar.png

142 ms

image.png

image.png

149 ms

arrow24.png

arrow24.png

150 ms

newtopbaricon8.png

newtopbaricon8.png

147 ms

crossdomain.html

crossdomain.html

2037 ms

crossdomain.html

crossdomain.html

12188 ms

request.s

request.s

1892 ms

analyse.png

analyse.png

8106 ms

empty.png

empty.png

81 ms

ava.s

ava.s

2426 ms

nb.css

nb.css

42 ms

crossdomain.html

crossdomain.html

2032 ms

ava.s

ava.s

19911 ms

face16.gif

face16.gif

58 ms

face19.gif

face19.gif

58 ms

background.gif

background.gif

36 ms

player_02.gif

player_02.gif

36 ms

player_06.gif

player_06.gif

69 ms

player_16.gif

player_16.gif

70 ms

player_17.gif

player_17.gif

68 ms

stopping.gif

stopping.gif

68 ms

player_23.gif

player_23.gif

67 ms

timeline_1.gif

timeline_1.gif

65 ms

player_29.gif

player_29.gif

65 ms

analyse.png

analyse.png

1082 ms

analytics.js

analytics.js

17 ms

collect

collect

41 ms

blogPhotoAd

blogPhotoAd

6254 ms

close_01.png

close_01.png

46 ms

top_bg.png

top_bg.png

212 ms

bottom_bg.png

bottom_bg.png

212 ms

left_bg.png

left_bg.png

211 ms

right_bg.png

right_bg.png

210 ms

left_top.png

left_top.png

243 ms

right_top.png

right_top.png

210 ms

left_bottom.png

left_bottom.png

368 ms

right_bottom.png

right_bottom.png

367 ms

shadow.png

shadow.png

207 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

898 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

2290 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1456 ms

MusicBeanNew.getPlayList.dwr

MusicBeanNew.getPlayList.dwr

3109 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1507 ms

face39.gif

face39.gif

57 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

3687 ms

list_line.gif

list_line.gif

550 ms

AlbumBeanNew.getUserSpace.dwr

AlbumBeanNew.getUserSpace.dwr

870 ms

sniff.png

sniff.png

883 ms

r

r

871 ms

90159968724347.js

90159968724347.js

2145 ms

ad

ad

6857 ms

close2.png

close2.png

162 ms

-1.gif

-1.gif

10 ms

75866310800003.js

75866310800003.js

1214 ms

6619084188467387974.jpg

6619084188467387974.jpg

1258 ms

jquery-1.4.2.js

jquery-1.4.2.js

44 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

2773 ms

face60.png

face60.png

78 ms

SEO Factors

jiongwen.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 Jiongwen.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 Jiongwen.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

jiongwen.blog.163.com

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