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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

13.2 sec in total

First Response

1.4 sec

Resources Loaded

11.7 sec

Page Rendered

135 ms

jing.blog.163.com screenshot

About Website

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

Visit jing.blog.163.com

Key Findings

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

jing.blog.163.com performance score

0

Network Requests Diagram

jing.blog.163.com

1402 ms

c.css

10 ms

nb.css

23 ms

6630133180817252049.jpg

1098 ms

1.0.0.js

1423 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Jing.blog.163.com, 34% (18 requests) were made to B.bst.126.net and 15% (8 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (7.7 sec) relates to the external source Api.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 577.2 kB (63%)

Content Size

910.5 kB

After Optimization

333.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 58.7 kB

  • Original 75.2 kB
  • After minification 75.2 kB
  • After compression 16.5 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 58.7 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 11.2 kB

  • Original 132.0 kB
  • After minification 120.8 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. Jing Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.8 kB

  • Original 522.2 kB
  • After minification 522.2 kB
  • After compression 163.4 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.8 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 148.5 kB

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

Requests Breakdown

Number of requests can be reduced by 30 (58%)

Requests Now

52

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jing.blog.163.com

jing.blog.163.com

1402 ms

c.css

c.css

10 ms

nb.css

nb.css

23 ms

6630133180817252049.jpg

6630133180817252049.jpg

1098 ms

1.0.0.js

1.0.0.js

1423 ms

pc.js

pc.js

15 ms

ph.js

ph.js

14 ms

xcode.png

xcode.png

15 ms

icon.png

icon.png

5 ms

lnkbar.png

lnkbar.png

5 ms

image.png

image.png

5 ms

arrow24.png

arrow24.png

4 ms

newtopbaricon8.png

newtopbaricon8.png

7 ms

top_bg.jpg

top_bg.jpg

18 ms

bg_tab.jpg

bg_tab.jpg

14 ms

tab_on.gif

tab_on.gif

13 ms

bg_titlebar.gif

bg_titlebar.gif

5 ms

bg_titlebar_c_l.gif

bg_titlebar_c_l.gif

5 ms

bg_titlebar_c_r.gif

bg_titlebar_c_r.gif

5 ms

bg_bottom.gif

bg_bottom.gif

20 ms

crossdomain.html

crossdomain.html

638 ms

crossdomain.html

crossdomain.html

1187 ms

crossdomain.html

crossdomain.html

1433 ms

request.s

request.s

706 ms

analyse.png

analyse.png

1042 ms

ava.s

ava.s

2403 ms

ava.s

ava.s

3051 ms

loftericon.png

loftericon.png

344 ms

analyse.png

analyse.png

1040 ms

analytics.js

analytics.js

5 ms

collect

collect

12 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

697 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

7736 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

962 ms

blogPhotoAd

blogPhotoAd

521 ms

close_01.png

close_01.png

6 ms

top_bg.png

top_bg.png

5 ms

bottom_bg.png

bottom_bg.png

9 ms

left_bg.png

left_bg.png

8 ms

right_bg.png

right_bg.png

9 ms

left_top.png

left_top.png

8 ms

right_top.png

right_top.png

9 ms

left_bottom.png

left_bottom.png

9 ms

right_bottom.png

right_bottom.png

8 ms

shadow.png

shadow.png

9 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1487 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

1078 ms

r

r

1539 ms

82463372092375.js

82463372092375.js

2786 ms

close2.png

close2.png

4 ms

ad

ad

1089 ms

jquery-1.4.2.js

jquery-1.4.2.js

1418 ms

0316ykt-300-250.jpg

0316ykt-300-250.jpg

3059 ms

SEO Factors

jing.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 Jing.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 Jing.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

jing.blog.163.com

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