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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

geyu.blog.163.com

zjl666333的博客 - zjl666333 - 网易博客

Page Load Speed

16.6 sec in total

First Response

2 sec

Resources Loaded

14.3 sec

Page Rendered

232 ms

geyu.blog.163.com screenshot

About Website

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

zjl666333的网易博客,网易博客,

Visit geyu.blog.163.com

Key Findings

We analyzed Geyu.blog.163.com page load time and found that the first response time was 2 sec and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

geyu.blog.163.com performance score

0

Network Requests Diagram

geyu.blog.163.com

2036 ms

c.css

21 ms

b.css

932 ms

6630133180817252049.jpg

2413 ms

xcode.png

55 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Geyu.blog.163.com, 18% (11 requests) were made to Img.bimg.126.net and 17% (10 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (12.2 sec) relates to the external source Img.bimg.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 531.8 kB (61%)

Content Size

877.0 kB

After Optimization

345.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 46.2 kB

  • Original 60.0 kB
  • After minification 59.9 kB
  • After compression 13.8 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 46.2 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 9.2 kB

  • Original 144.4 kB
  • After minification 135.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. Geyu Blog 163 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 326.6 kB

  • Original 489.7 kB
  • After minification 489.7 kB
  • After compression 163.1 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 326.6 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 149.8 kB

  • Original 182.9 kB
  • After minification 179.0 kB
  • After compression 33.1 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. Geyu.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (64%)

Requests Now

59

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

geyu.blog.163.com

geyu.blog.163.com

2036 ms

c.css

c.css

21 ms

b.css

b.css

932 ms

6630133180817252049.jpg

6630133180817252049.jpg

2413 ms

xcode.png

xcode.png

55 ms

1.0.0.js

1.0.0.js

108 ms

pc.js

pc.js

20 ms

ph.js

ph.js

18 ms

5772207347405742436.jpg

5772207347405742436.jpg

10570 ms

icon.png

icon.png

31 ms

5791066170845357749.jpg

5791066170845357749.jpg

12212 ms

5791066170845357824.jpg

5791066170845357824.jpg

1983 ms

5791066170845357823.jpg

5791066170845357823.jpg

9613 ms

5791066170845357826.jpg

5791066170845357826.jpg

4841 ms

5772207347405742474.jpg

5772207347405742474.jpg

6035 ms

5791066170845357828.jpg

5791066170845357828.jpg

3973 ms

5791066170845357830.jpg

5791066170845357830.jpg

5362 ms

5791066170845357832.jpg

5791066170845357832.jpg

5244 ms

5791066170845357836.jpg

5791066170845357836.jpg

5650 ms

5791066170845357834.jpg

5791066170845357834.jpg

5829 ms

lnkbar.png

lnkbar.png

27 ms

image.png

image.png

26 ms

arrow24.png

arrow24.png

27 ms

newtopbaricon8.png

newtopbaricon8.png

27 ms

crossdomain.html

crossdomain.html

921 ms

crossdomain.html

crossdomain.html

776 ms

crossdomain.html

crossdomain.html

1103 ms

request.s

request.s

794 ms

analyse.png

analyse.png

1167 ms

ava.s

ava.s

2760 ms

loftericon.png

loftericon.png

452 ms

ava.s

ava.s

752 ms

analyse.png

analyse.png

1344 ms

analytics.js

analytics.js

9 ms

collect

collect

16 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

927 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1061 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1145 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1156 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

1147 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1341 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

3096 ms

blogPhotoAd

blogPhotoAd

500 ms

close_01.png

close_01.png

48 ms

top_bg.png

top_bg.png

79 ms

bottom_bg.png

bottom_bg.png

82 ms

left_bg.png

left_bg.png

81 ms

right_bg.png

right_bg.png

81 ms

left_top.png

left_top.png

81 ms

right_top.png

right_top.png

81 ms

left_bottom.png

left_bottom.png

111 ms

right_bottom.png

right_bottom.png

112 ms

shadow.png

shadow.png

47 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

727 ms

r

r

1776 ms

ava.s

ava.s

384 ms

close2.png

close2.png

4 ms

ad

ad

907 ms

jquery-1.4.2.js

jquery-1.4.2.js

14 ms

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

1150 ms

SEO Factors

geyu.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 Geyu.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 Geyu.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

geyu.blog.163.com

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