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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

24 sec in total

First Response

5 sec

Resources Loaded

18.6 sec

Page Rendered

332 ms

swxu2004.blog.163.com screenshot

About Website

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

Visit swxu2004.blog.163.com

Key Findings

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

Performance Metrics

swxu2004.blog.163.com performance score

0

Network Requests Diagram

swxu2004.blog.163.com

5040 ms

c.css

1106 ms

b.css

869 ms

6630133180817252049.jpg

1010 ms

xcode.png

3334 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Swxu2004.blog.163.com, 34% (23 requests) were made to B.bst.126.net and 19% (13 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (5.8 sec) relates to the external source Img.bimg.126.net.

Page Optimization Overview & Recommendations

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

Content Size

949.7 kB

After Optimization

370.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 58.7 kB

  • Original 76.8 kB
  • After minification 76.7 kB
  • After compression 18.0 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 58.7 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 10.9 kB

  • Original 167.1 kB
  • After minification 156.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. Swxu 2004 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.4 kB

  • Original 521.4 kB
  • After minification 521.4 kB
  • After compression 162.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 358.4 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 151.0 kB

  • Original 184.5 kB
  • After minification 180.5 kB
  • After compression 33.5 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. Swxu2004.blog.163.com needs all CSS files to be minified and compressed as it can save up to 151.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (63%)

Requests Now

67

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

swxu2004.blog.163.com

swxu2004.blog.163.com

5040 ms

c.css

c.css

1106 ms

b.css

b.css

869 ms

6630133180817252049.jpg

6630133180817252049.jpg

1010 ms

xcode.png

xcode.png

3334 ms

1.0.0.js

1.0.0.js

633 ms

pc.js

pc.js

4293 ms

ph.js

ph.js

1833 ms

5715912352063876170.jpg

5715912352063876170.jpg

2188 ms

icon.png

icon.png

59 ms

lnkbar.png

lnkbar.png

58 ms

image.png

image.png

59 ms

arrow24.png

arrow24.png

461 ms

newtopbaricon8.png

newtopbaricon8.png

59 ms

5757289173640286811.jpg

5757289173640286811.jpg

5756 ms

5735052650480193026.jpg

5735052650480193026.jpg

1055 ms

5717882676900853093.jpg

5717882676900853093.jpg

1068 ms

5717882676900853092.jpg

5717882676900853092.jpg

1068 ms

5717882676900853119.jpg

5717882676900853119.jpg

1075 ms

5735052650480193091.jpg

5735052650480193091.jpg

1607 ms

5717882676900853097.jpg

5717882676900853097.jpg

3202 ms

5717882676900853099.jpg

5717882676900853099.jpg

1627 ms

5717882676900853125.jpg

5717882676900853125.jpg

3224 ms

5717882676900853128.jpg

5717882676900853128.jpg

2161 ms

5717882676900853126.jpg

5717882676900853126.jpg

2187 ms

5757289173640286823.jpg

5757289173640286823.jpg

2711 ms

crossdomain.html

crossdomain.html

1870 ms

crossdomain.html

crossdomain.html

3419 ms

request.s

request.s

603 ms

analyse.png

analyse.png

1030 ms

ava.s

ava.s

4970 ms

nb.css

nb.css

44 ms

crossdomain.html

crossdomain.html

1058 ms

ava.s

ava.s

3648 ms

background.gif

background.gif

7 ms

player_02.gif

player_02.gif

8 ms

player_06.gif

player_06.gif

69 ms

player_16.gif

player_16.gif

547 ms

player_17.gif

player_17.gif

1042 ms

player_23.gif

player_23.gif

37 ms

timeline_1.gif

timeline_1.gif

626 ms

player_29.gif

player_29.gif

71 ms

analyse.png

analyse.png

979 ms

analytics.js

analytics.js

9 ms

collect

collect

14 ms

k.gif

k.gif

1272 ms

blogPhotoAd

blogPhotoAd

523 ms

close_01.png

close_01.png

758 ms

top_bg.png

top_bg.png

5 ms

bottom_bg.png

bottom_bg.png

460 ms

left_bg.png

left_bg.png

577 ms

right_bg.png

right_bg.png

1192 ms

left_top.png

left_top.png

1026 ms

right_top.png

right_top.png

12 ms

left_bottom.png

left_bottom.png

12 ms

right_bottom.png

right_bottom.png

471 ms

shadow.png

shadow.png

481 ms

r

r

997 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

912 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1253 ms

ad

ad

1099 ms

close2.png

close2.png

6 ms

face1.gif

face1.gif

22 ms

face85.gif

face85.gif

22 ms

face55.gif

face55.gif

21 ms

face22.gif

face22.gif

910 ms

jquery-1.4.2.js

jquery-1.4.2.js

1869 ms

0316ykt-300-250.jpg

0316ykt-300-250.jpg

3259 ms

SEO Factors

swxu2004.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 Swxu2004.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 Swxu2004.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

swxu2004.blog.163.com

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