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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

31.4 sec in total

First Response

2 sec

Resources Loaded

27.7 sec

Page Rendered

1.6 sec

g6612843.blog.163.com screenshot

About Website

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

Visit g6612843.blog.163.com

Key Findings

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

Performance Metrics

g6612843.blog.163.com performance score

0

Network Requests Diagram

g6612843.blog.163.com

2047 ms

c.css

36 ms

b.css

1902 ms

6598165979809716614.jpg

2151 ms

3d00031bf6,e71579fc

1039 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original G6612843.blog.163.com, 28% (29 requests) were made to Os.blog.163.com and 14% (14 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Os.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 609.6 kB (14%)

Content Size

4.3 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of G6612843.blog.163.com main page is 4.3 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. 35% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 138.5 kB

  • Original 175.9 kB
  • After minification 175.8 kB
  • After compression 37.4 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 138.5 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 11.7 kB

  • Original 3.5 MB
  • After minification 3.4 MB

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. G 6612843 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.6 kB

  • Original 449.5 kB
  • After minification 449.5 kB
  • After compression 138.9 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.9 kB

  • Original 181.8 kB
  • After minification 177.9 kB
  • After compression 32.8 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. G6612843.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (34%)

Requests Now

95

After Optimization

63

  • AJAX
  • Images
  • JavaScript
  • CSS

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

g6612843.blog.163.com

g6612843.blog.163.com

2047 ms

c.css

c.css

36 ms

b.css

b.css

1902 ms

6598165979809716614.jpg

6598165979809716614.jpg

2151 ms

3d00031bf6,e71579fc

3d00031bf6,e71579fc

1039 ms

3274398404175308815.jpg

3274398404175308815.jpg

612 ms

6631374529448257134.jpg

6631374529448257134.jpg

355 ms

6630575184490485611.jpg

6630575184490485611.jpg

2102 ms

6608637728491912919.gif

6608637728491912919.gif

3207 ms

6598299020717391806.jpg

6598299020717391806.jpg

1489 ms

4881057571240156889.jpg

4881057571240156889.jpg

1477 ms

4844747299244480741.jpg

4844747299244480741.jpg

2323 ms

6619097382607821646.jpg

6619097382607821646.jpg

1949 ms

6598251741717307828.jpg

6598251741717307828.jpg

2257 ms

1480276902522163780.gif

1480276902522163780.gif

255 ms

3383610695138987170.jpg

3383610695138987170.jpg

1922 ms

4829547650501832507.jpg

4829547650501832507.jpg

689 ms

6630133180817252049.jpg

6630133180817252049.jpg

1720 ms

xcode.png

xcode.png

82 ms

1.0.0.js

1.0.0.js

250 ms

pc.js

pc.js

123 ms

ph.js

ph.js

120 ms

6598167079321807068.jpeg

6598167079321807068.jpeg

367 ms

1200490775672188397.jpg

1200490775672188397.jpg

865 ms

icon.png

icon.png

285 ms

lnkbar.png

lnkbar.png

270 ms

image.png

image.png

274 ms

arrow24.png

arrow24.png

272 ms

newtopbaricon8.png

newtopbaricon8.png

274 ms

2017612633062792980.jpg

2017612633062792980.jpg

2848 ms

crossdomain.html

crossdomain.html

2218 ms

crossdomain.html

crossdomain.html

733 ms

request.s

request.s

492 ms

analyse.png

analyse.png

746 ms

ava.s

ava.s

2174 ms

crossdomain.html

crossdomain.html

622 ms

ava.s

ava.s

2668 ms

analyse.png

analyse.png

649 ms

analytics.js

analytics.js

30 ms

collect

collect

21 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

699 ms

PhotoBlogBean.getHeadPic.dwr

PhotoBlogBean.getHeadPic.dwr

914 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

994 ms

blogPhotoAd

blogPhotoAd

371 ms

close_01.png

close_01.png

67 ms

top_bg.png

top_bg.png

119 ms

bottom_bg.png

bottom_bg.png

128 ms

left_bg.png

left_bg.png

130 ms

right_bg.png

right_bg.png

131 ms

left_top.png

left_top.png

133 ms

right_top.png

right_top.png

134 ms

left_bottom.png

left_bottom.png

190 ms

right_bottom.png

right_bottom.png

190 ms

shadow.png

shadow.png

86 ms

122045806107535.js

122045806107535.js

1508 ms

r

r

20453 ms

839076905575515202.jpg

839076905575515202.jpg

1645 ms

PhotoBlogBean.getPictureSets75PictureUrl.dwr

PhotoBlogBean.getPictureSets75PictureUrl.dwr

292 ms

6631218398797110361.jpg

6631218398797110361.jpg

718 ms

SetupBeanNew.getCustomModulesData.dwr

SetupBeanNew.getCustomModulesData.dwr

19830 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

1245 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1275 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1475 ms

BlogBeanNew.getHostHotBlogs.dwr

BlogBeanNew.getHostHotBlogs.dwr

19746 ms

BlogBeanNew.getRecentBlogs.dwr

BlogBeanNew.getRecentBlogs.dwr

1987 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1929 ms

close2.png

close2.png

118 ms

-1.gif

-1.gif

52 ms

122045806107534.js

122045806107534.js

917 ms

empty.png

empty.png

69 ms

ava.s

ava.s

2304 ms

ava.s

ava.s

444 ms

ava.s

ava.s

970 ms

ava.s

ava.s

971 ms

ava.s

ava.s

970 ms

ava.s

ava.s

996 ms

ava.s

ava.s

3084 ms

ava.s

ava.s

11041 ms

ava.s

ava.s

9913 ms

ava.s

ava.s

1449 ms

ava.s

ava.s

3572 ms

ava.s

ava.s

1900 ms

ava.s

ava.s

3742 ms

ava.s

ava.s

5579 ms

ava.s

ava.s

4595 ms

ava.s

ava.s

4003 ms

ava.s

ava.s

20488 ms

ava.s

ava.s

7096 ms

ava.s

ava.s

6497 ms

ava.s

ava.s

6013 ms

ava.s

ava.s

6457 ms

ava.s

ava.s

7828 ms

ava.s

ava.s

9644 ms

ava.s

ava.s

7556 ms

ava.s

ava.s

9437 ms

ava.s

ava.s

9564 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

20479 ms

face50.gif

face50.gif

65 ms

6597246788030030981.gif

6597246788030030981.gif

7238 ms

825284631816005714.jpg

825284631816005714.jpg

975 ms

1306606841908039258.jpg

1306606841908039258.jpg

1162 ms

face60.png

face60.png

100 ms

SEO Factors

g6612843.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 G6612843.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 G6612843.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

g6612843.blog.163.com

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