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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

26.7 sec in total

First Response

1.8 sec

Resources Loaded

24.6 sec

Page Rendered

250 ms

blogeditor.blog.163.com screenshot

About Website

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

Visit blogeditor.blog.163.com

Key Findings

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

Performance Metrics

blogeditor.blog.163.com performance score

0

Network Requests Diagram

blogeditor.blog.163.com

1800 ms

c.css

84 ms

b.css

805 ms

6630133180817252049.jpg

19824 ms

xcode.png

103 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Blogeditor.blog.163.com, 27% (17 requests) were made to Os.blog.163.com and 19% (12 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Lofter.com.

Page Optimization Overview & Recommendations

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

Content Size

915.7 kB

After Optimization

367.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 78.7 kB

  • Original 99.8 kB
  • After minification 99.8 kB
  • After compression 21.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 78.7 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 9.3 kB

  • Original 184.2 kB
  • After minification 174.9 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. Blogeditor Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.5 kB

  • Original 449.0 kB
  • After minification 449.0 kB
  • After compression 138.6 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.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.7 kB

  • Original 182.7 kB
  • After minification 178.7 kB
  • After compression 33.0 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. Blogeditor.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (43%)

Requests Now

56

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blogeditor.blog.163.com

blogeditor.blog.163.com

1800 ms

c.css

c.css

84 ms

b.css

b.css

805 ms

6630133180817252049.jpg

6630133180817252049.jpg

19824 ms

xcode.png

xcode.png

103 ms

1.0.0.js

1.0.0.js

126 ms

pc.js

pc.js

102 ms

ph.js

ph.js

100 ms

5685231579602608381.jpg

5685231579602608381.jpg

653 ms

icon.png

icon.png

82 ms

5685231579602608380.jpg

5685231579602608380.jpg

802 ms

2846556439475441096.jpg

2846556439475441096.jpg

803 ms

2846556439475441100.jpg

2846556439475441100.jpg

882 ms

2877518686913619501.jpg

2877518686913619501.jpg

974 ms

2846556439475441105.jpg

2846556439475441105.jpg

988 ms

blog_rec.png

blog_rec.png

71 ms

lnkbar.png

lnkbar.png

73 ms

image.png

image.png

73 ms

arrow24.png

arrow24.png

75 ms

newtopbaricon8.png

newtopbaricon8.png

74 ms

crossdomain.html

crossdomain.html

816 ms

crossdomain.html

crossdomain.html

888 ms

request.s

request.s

599 ms

analyse.png

analyse.png

19874 ms

empty.png

empty.png

47 ms

6631394320658212017.gif

6631394320658212017.gif

1685 ms

ava.s

ava.s

2515 ms

crossdomain.html

crossdomain.html

693 ms

analyse.png

analyse.png

19608 ms

analytics.js

analytics.js

23 ms

collect

collect

18 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

19937 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1165 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1189 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

3191 ms

blogPhotoAd

blogPhotoAd

20401 ms

close_01.png

close_01.png

9 ms

top_bg.png

top_bg.png

16 ms

bottom_bg.png

bottom_bg.png

29 ms

left_bg.png

left_bg.png

29 ms

right_bg.png

right_bg.png

16 ms

left_top.png

left_top.png

17 ms

right_top.png

right_top.png

18 ms

left_bottom.png

left_bottom.png

26 ms

right_bottom.png

right_bottom.png

27 ms

shadow.png

shadow.png

12 ms

ava.s

ava.s

2595 ms

ava.s

ava.s

2224 ms

ava.s

ava.s

708 ms

ava.s

ava.s

5830 ms

ava.s

ava.s

2821 ms

ava.s

ava.s

1061 ms

ava.s

ava.s

1062 ms

ava.s

ava.s

1587 ms

ava.s

ava.s

1421 ms

ava.s

ava.s

1837 ms

ava.s

ava.s

2088 ms

ava.s

ava.s

3618 ms

ava.s

ava.s

2533 ms

ava.s

ava.s

2586 ms

ava.s

ava.s

5426 ms

face56.gif

face56.gif

41 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

876 ms

SEO Factors

blogeditor.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 Blogeditor.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 Blogeditor.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

blogeditor.blog.163.com

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