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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

32.8 sec in total

First Response

4.8 sec

Resources Loaded

27.7 sec

Page Rendered

333 ms

guxishang.blog.163.com screenshot

About Website

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

Visit guxishang.blog.163.com

Key Findings

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

Performance Metrics

guxishang.blog.163.com performance score

0

Network Requests Diagram

guxishang.blog.163.com

4755 ms

c.css

179 ms

b.css

1164 ms

5112148527020128933.jpg

11336 ms

icon.png

56 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Guxishang.blog.163.com, 31% (17 requests) were made to Os.blog.163.com and 18% (10 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source G.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 539.7 kB (64%)

Content Size

838.1 kB

After Optimization

298.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Guxishang.blog.163.com main page is 838.1 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 448.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 71.2 kB

  • Original 91.5 kB
  • After minification 91.5 kB
  • After compression 20.3 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 71.2 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 9.2 kB

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

Requests Breakdown

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

Requests Now

51

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

guxishang.blog.163.com

guxishang.blog.163.com

4755 ms

c.css

c.css

179 ms

b.css

b.css

1164 ms

5112148527020128933.jpg

5112148527020128933.jpg

11336 ms

icon.png

icon.png

56 ms

6630133180817252049.jpg

6630133180817252049.jpg

1757 ms

xcode.png

xcode.png

141 ms

1.0.0.js

1.0.0.js

1906 ms

lnkbar.png

lnkbar.png

64 ms

image.png

image.png

80 ms

arrow24.png

arrow24.png

81 ms

newtopbaricon8.png

newtopbaricon8.png

80 ms

4809844402033759321.jpg

4809844402033759321.jpg

3897 ms

pc.js

pc.js

302 ms

ph.js

ph.js

265 ms

crossdomain.html

crossdomain.html

2793 ms

crossdomain.html

crossdomain.html

849 ms

request.s

request.s

19528 ms

analyse.png

analyse.png

862 ms

ava.s

ava.s

2402 ms

crossdomain.html

crossdomain.html

3178 ms

analyse.png

analyse.png

958 ms

analytics.js

analytics.js

140 ms

collect

collect

104 ms

blogPhotoAd

blogPhotoAd

379 ms

close_01.png

close_01.png

28 ms

top_bg.png

top_bg.png

53 ms

bottom_bg.png

bottom_bg.png

49 ms

left_bg.png

left_bg.png

49 ms

right_bg.png

right_bg.png

45 ms

left_top.png

left_top.png

50 ms

right_top.png

right_top.png

52 ms

left_bottom.png

left_bottom.png

62 ms

right_bottom.png

right_bottom.png

63 ms

shadow.png

shadow.png

23 ms

r

r

19653 ms

close2.png

close2.png

33 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1052 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1551 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1637 ms

ava.s

ava.s

4482 ms

ava.s

ava.s

843 ms

ava.s

ava.s

825 ms

ava.s

ava.s

917 ms

ava.s

ava.s

991 ms

ava.s

ava.s

1267 ms

ava.s

ava.s

1291 ms

ava.s

ava.s

4887 ms

ava.s

ava.s

8055 ms

ava.s

ava.s

1701 ms

ava.s

ava.s

4018 ms

ava.s

ava.s

1879 ms

ava.s

ava.s

2094 ms

ava.s

ava.s

2347 ms

ava.s

ava.s

4179 ms

SEO Factors

guxishang.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 Guxishang.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 Guxishang.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

guxishang.blog.163.com

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