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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

33 sec in total

First Response

1.6 sec

Resources Loaded

31 sec

Page Rendered

444 ms

xueyongblog.blog.163.com screenshot

About Website

Welcome to xueyongblog.blog.163.com homepage info - get ready to check Xueyongblog Blog 163 best content for China right away, or after learning these important things about xueyongblog.blog.163.com

Visit xueyongblog.blog.163.com

Key Findings

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

xueyongblog.blog.163.com performance score

0

Network Requests Diagram

xueyongblog.blog.163.com

1574 ms

c.css

8 ms

nb.css

23 ms

icon.png

5 ms

bg_browser.jpg

3 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Xueyongblog.blog.163.com, 31% (21 requests) were made to B.bst.126.net and 24% (16 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (8 sec) relates to the external source Api.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 564.7 kB (60%)

Content Size

949.0 kB

After Optimization

384.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 86.7 kB

  • Original 110.9 kB
  • After minification 110.9 kB
  • After compression 24.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 86.7 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 19.1 kB

  • Original 208.1 kB
  • After minification 189.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. Xueyongblog Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.6 kB

  • Original 449.1 kB
  • After minification 449.1 kB
  • After compression 138.5 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 310.6 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 148.4 kB

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

Requests Breakdown

Number of requests can be reduced by 31 (47%)

Requests Now

66

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xueyongblog.blog.163.com

xueyongblog.blog.163.com

1574 ms

c.css

c.css

8 ms

nb.css

nb.css

23 ms

icon.png

icon.png

5 ms

bg_browser.jpg

bg_browser.jpg

3 ms

bg_top.jpg

bg_top.jpg

9 ms

bg_item.png

bg_item.png

7 ms

bg_mid.jpg

bg_mid.jpg

6 ms

bg_bottom.jpg

bg_bottom.jpg

8 ms

goodbloghead.png

goodbloghead.png

4 ms

rssi.png

rssi.png

8 ms

lnkbar.png

lnkbar.png

7 ms

image.png

image.png

19 ms

6630133180817252049.jpg

6630133180817252049.jpg

3806 ms

xcode.png

xcode.png

17 ms

1.0.0.js

1.0.0.js

73 ms

pc.js

pc.js

15 ms

ph.js

ph.js

14 ms

arrow24.png

arrow24.png

10 ms

newtopbaricon8.png

newtopbaricon8.png

10 ms

crossdomain.html

crossdomain.html

965 ms

crossdomain.html

crossdomain.html

1253 ms

crossdomain.html

crossdomain.html

2138 ms

request.s

request.s

679 ms

analyse.png

analyse.png

1289 ms

ava.s

ava.s

875 ms

loftericon.png

loftericon.png

5287 ms

ava.s

ava.s

887 ms

analyse.png

analyse.png

1641 ms

analytics.js

analytics.js

9 ms

collect

collect

20 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1011 ms

close_01.png

close_01.png

6 ms

top_bg.png

top_bg.png

4 ms

bottom_bg.png

bottom_bg.png

13 ms

left_bg.png

left_bg.png

14 ms

right_bg.png

right_bg.png

10 ms

left_top.png

left_top.png

14 ms

right_top.png

right_top.png

13 ms

left_bottom.png

left_bottom.png

14 ms

right_bottom.png

right_bottom.png

16 ms

shadow.png

shadow.png

15 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

2809 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1401 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

7951 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

6074 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

2900 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

966 ms

face50.gif

face50.gif

27 ms

face57.gif

face57.gif

26 ms

face55.gif

face55.gif

28 ms

face63.gif

face63.gif

27 ms

ava.s

ava.s

670 ms

ava.s

ava.s

2608 ms

ava.s

ava.s

4389 ms

ava.s

ava.s

875 ms

ava.s

ava.s

881 ms

ava.s

ava.s

953 ms

ava.s

ava.s

2451 ms

ava.s

ava.s

1306 ms

ava.s

ava.s

1317 ms

ava.s

ava.s

1416 ms

ava.s

ava.s

1740 ms

ava.s

ava.s

1919 ms

ava.s

ava.s

2178 ms

ava.s

ava.s

2393 ms

face60.png

face60.png

5 ms

SEO Factors

xueyongblog.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 Xueyongblog.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 Xueyongblog.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

xueyongblog.blog.163.com

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