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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

25.8 sec in total

First Response

1.9 sec

Resources Loaded

23.2 sec

Page Rendered

725 ms

sdjiaweb.blog.163.com screenshot

About Website

Click here to check amazing Sdjiaweb Blog 163 content for China. Otherwise, check out these important facts you probably never knew about sdjiaweb.blog.163.com

Visit sdjiaweb.blog.163.com

Key Findings

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

sdjiaweb.blog.163.com performance score

0

Network Requests Diagram

sdjiaweb.blog.163.com

1949 ms

c.css

153 ms

nb.css

99 ms

ag_01.jpg

188 ms

icon.png

166 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 619.6 kB (57%)

Content Size

1.1 MB

After Optimization

463.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 96.2 kB

  • Original 121.5 kB
  • After minification 121.5 kB
  • After compression 25.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 96.2 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 15.2 kB

  • Original 256.2 kB
  • After minification 241.0 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. Sdjiaweb Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 359.9 kB

  • Original 524.3 kB
  • After minification 524.3 kB
  • After compression 164.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 359.9 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 148.3 kB

  • Original 180.7 kB
  • After minification 176.9 kB
  • After compression 32.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. Sdjiaweb.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 33 (46%)

Requests Now

71

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sdjiaweb.blog.163.com

sdjiaweb.blog.163.com

1949 ms

c.css

c.css

153 ms

nb.css

nb.css

99 ms

ag_01.jpg

ag_01.jpg

188 ms

icon.png

icon.png

166 ms

6630133180817252049.jpg

6630133180817252049.jpg

4657 ms

1.0.0.js

1.0.0.js

1346 ms

pc.js

pc.js

269 ms

ph.js

ph.js

236 ms

lnkbar.png

lnkbar.png

153 ms

image.png

image.png

156 ms

arrow24.png

arrow24.png

153 ms

newtopbaricon8.png

newtopbaricon8.png

156 ms

ag_02.jpg

ag_02.jpg

149 ms

ag_07.jpg

ag_07.jpg

161 ms

ag_04.jpg

ag_04.jpg

252 ms

xcode.png

xcode.png

176 ms

crossdomain.html

crossdomain.html

982 ms

crossdomain.html

crossdomain.html

801 ms

request.s

request.s

19809 ms

analyse.png

analyse.png

2637 ms

ava.s

ava.s

1511 ms

crossdomain.html

crossdomain.html

821 ms

ava.s

ava.s

3519 ms

analyse.png

analyse.png

1512 ms

analytics.js

analytics.js

71 ms

collect

collect

71 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

834 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1077 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1292 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

2034 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

2096 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

8899 ms

blogPhotoAd

blogPhotoAd

688 ms

close_01.png

close_01.png

43 ms

top_bg.png

top_bg.png

46 ms

bottom_bg.png

bottom_bg.png

41 ms

left_bg.png

left_bg.png

45 ms

right_bg.png

right_bg.png

102 ms

left_top.png

left_top.png

102 ms

right_top.png

right_top.png

106 ms

left_bottom.png

left_bottom.png

107 ms

right_bottom.png

right_bottom.png

109 ms

shadow.png

shadow.png

45 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

8924 ms

1099521683597.js

1099521683597.js

1143 ms

ava.s

ava.s

1581 ms

ava.s

ava.s

3049 ms

ava.s

ava.s

902 ms

ava.s

ava.s

1342 ms

ava.s

ava.s

1775 ms

ava.s

ava.s

1846 ms

ava.s

ava.s

1891 ms

ava.s

ava.s

2607 ms

ava.s

ava.s

2013 ms

ava.s

ava.s

2215 ms

ava.s

ava.s

2238 ms

ava.s

ava.s

2316 ms

ava.s

ava.s

3254 ms

ava.s

ava.s

2689 ms

ava.s

ava.s

3071 ms

r

r

4885 ms

face51.gif

face51.gif

62 ms

-1.gif

-1.gif

407 ms

251788170612656.js

251788170612656.js

817 ms

empty.png

empty.png

64 ms

ava.s

ava.s

1737 ms

close2.png

close2.png

59 ms

2225904115829413828.jpg

2225904115829413828.jpg

1589 ms

ad

ad

1767 ms

jquery-1.4.2.js

jquery-1.4.2.js

107 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

4294 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

6431 ms

SEO Factors

sdjiaweb.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 Sdjiaweb.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 Sdjiaweb.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

sdjiaweb.blog.163.com

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