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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

30.1 sec in total

First Response

3.6 sec

Resources Loaded

25.5 sec

Page Rendered

1 sec

transist.blog.163.com screenshot

About Website

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

Visit transist.blog.163.com

Key Findings

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

Performance Metrics

transist.blog.163.com performance score

0

Network Requests Diagram

transist.blog.163.com

3581 ms

c.css

21 ms

nb.css

14 ms

89091379594536796.jpg

6601 ms

1379488601707.jpg

2363 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Transist.blog.163.com, 25% (18 requests) were made to Os.blog.163.com and 21% (15 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source G.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 567.5 kB (65%)

Content Size

871.2 kB

After Optimization

303.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 99.6 kB

  • Original 129.1 kB
  • After minification 129.1 kB
  • After compression 29.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 99.6 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 9.3 kB

  • Original 112.5 kB
  • After minification 103.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. Transist Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.3 kB

  • Original 448.7 kB
  • After minification 448.7 kB
  • After compression 138.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 310.3 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 148.3 kB

  • Original 180.9 kB
  • After minification 177.0 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. Transist.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 29 (47%)

Requests Now

62

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

transist.blog.163.com

transist.blog.163.com

3581 ms

c.css

c.css

21 ms

nb.css

nb.css

14 ms

89091379594536796.jpg

89091379594536796.jpg

6601 ms

1379488601707.jpg

1379488601707.jpg

2363 ms

top_banner.jpg

top_banner.jpg

78 ms

bg_tab.jpg

bg_tab.jpg

74 ms

tap_on.gif

tap_on.gif

73 ms

icon.png

icon.png

53 ms

bg_web_b.gif

bg_web_b.gif

52 ms

6630133180817252049.jpg

6630133180817252049.jpg

704 ms

1.0.0.js

1.0.0.js

87 ms

lnkbar.png

lnkbar.png

9 ms

image.png

image.png

17 ms

arrow24.png

arrow24.png

16 ms

newtopbaricon8.png

newtopbaricon8.png

15 ms

1374734662337.jpg

1374734662337.jpg

1984 ms

1374475046769.jpg

1374475046769.jpg

4645 ms

1373352192185.jpg

1373352192185.jpg

4977 ms

xcode.png

xcode.png

6 ms

pc.js

pc.js

26 ms

ph.js

ph.js

81 ms

crossdomain.html

crossdomain.html

934 ms

crossdomain.html

crossdomain.html

759 ms

crossdomain.html

crossdomain.html

659 ms

request.s

request.s

612 ms

analyse.png

analyse.png

613 ms

ava.s

ava.s

2705 ms

loftericon.png

loftericon.png

358 ms

ava.s

ava.s

2449 ms

analyse.png

analyse.png

640 ms

analytics.js

analytics.js

23 ms

collect

collect

53 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

957 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1210 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

10306 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

2668 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

1361 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1895 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

8982 ms

blogPhotoAd

blogPhotoAd

314 ms

close_01.png

close_01.png

13 ms

top_bg.png

top_bg.png

64 ms

bottom_bg.png

bottom_bg.png

50 ms

left_bg.png

left_bg.png

77 ms

right_bg.png

right_bg.png

77 ms

left_top.png

left_top.png

76 ms

right_top.png

right_top.png

75 ms

left_bottom.png

left_bottom.png

79 ms

right_bottom.png

right_bottom.png

84 ms

shadow.png

shadow.png

47 ms

r

r

20027 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

19678 ms

ava.s

ava.s

561 ms

close2.png

close2.png

7 ms

ava.s

ava.s

396 ms

ava.s

ava.s

768 ms

ava.s

ava.s

801 ms

ava.s

ava.s

779 ms

ava.s

ava.s

807 ms

ava.s

ava.s

795 ms

ava.s

ava.s

1549 ms

ava.s

ava.s

2825 ms

ava.s

ava.s

1213 ms

ava.s

ava.s

2687 ms

ava.s

ava.s

1209 ms

ava.s

ava.s

5425 ms

ava.s

ava.s

2835 ms

ava.s

ava.s

2169 ms

ava.s

ava.s

3180 ms

sysbussy.jpg

sysbussy.jpg

221 ms

SEO Factors

transist.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 Transist.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 Transist.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

transist.blog.163.com

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