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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

25.4 sec in total

First Response

2.5 sec

Resources Loaded

22.6 sec

Page Rendered

334 ms

devilswrwr.blog.163.com screenshot

About Website

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

Visit devilswrwr.blog.163.com

Key Findings

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

Performance Metrics

devilswrwr.blog.163.com performance score

0

Network Requests Diagram

devilswrwr.blog.163.com

2516 ms

c.css

389 ms

nb.css

385 ms

top.jpg

116 ms

bee1c1aa7d02d49d0a87e084ca419.png

5520 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 652.5 kB (54%)

Content Size

1.2 MB

After Optimization

559.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 119.5 kB

  • Original 149.8 kB
  • After minification 149.7 kB
  • After compression 30.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 119.5 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 19.9 kB

  • Original 348.6 kB
  • After minification 328.8 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. Devilswrwr Blog 163 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 363.9 kB

  • Original 531.6 kB
  • After minification 531.6 kB
  • After compression 167.7 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 363.9 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 149.2 kB

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

Requests Breakdown

Number of requests can be reduced by 39 (58%)

Requests Now

67

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

devilswrwr.blog.163.com

devilswrwr.blog.163.com

2516 ms

c.css

c.css

389 ms

nb.css

nb.css

385 ms

top.jpg

top.jpg

116 ms

bee1c1aa7d02d49d0a87e084ca419.png

bee1c1aa7d02d49d0a87e084ca419.png

5520 ms

5789658796761600565.jpg

5789658796761600565.jpg

20089 ms

20150419154540534.png

20150419154540534.png

6122 ms

20160125213435_580.jpg

20160125213435_580.jpg

20087 ms

531400.jpg

531400.jpg

1633 ms

1209576-33c43d3e35a41ad4.png

1209576-33c43d3e35a41ad4.png

1428 ms

20141023_31_51377_0.jpg!view

20141023_31_51377_0.jpg!view

5492 ms

icon.png

icon.png

97 ms

6630133180817252049.jpg

6630133180817252049.jpg

1718 ms

1.0.0.js

1.0.0.js

116 ms

pc.js

pc.js

89 ms

ph.js

ph.js

89 ms

bg.gif

bg.gif

78 ms

line.gif

line.gif

78 ms

xcode.png

xcode.png

82 ms

434923.jpg

434923.jpg

1681 ms

465088.png

465088.png

1672 ms

lnkbar.png

lnkbar.png

79 ms

image.png

image.png

84 ms

arrow24.png

arrow24.png

81 ms

newtopbaricon8.png

newtopbaricon8.png

83 ms

crossdomain.html

crossdomain.html

1883 ms

crossdomain.html

crossdomain.html

672 ms

crossdomain.html

crossdomain.html

993 ms

request.s

request.s

628 ms

analyse.png

analyse.png

933 ms

empty.png

empty.png

40 ms

ava.s

ava.s

843 ms

loftericon.png

loftericon.png

440 ms

nb.css

nb.css

13 ms

ava.s

ava.s

852 ms

background.gif

background.gif

7 ms

player_02.gif

player_02.gif

6 ms

player_06.gif

player_06.gif

5 ms

player_16.gif

player_16.gif

8 ms

player_17.gif

player_17.gif

8 ms

player_23.gif

player_23.gif

9 ms

timeline_1.gif

timeline_1.gif

10 ms

player_29.gif

player_29.gif

9 ms

analyse.png

analyse.png

820 ms

analytics.js

analytics.js

14 ms

collect

collect

14 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

802 ms

blogPhotoAd

blogPhotoAd

8264 ms

close_01.png

close_01.png

27 ms

top_bg.png

top_bg.png

29 ms

bottom_bg.png

bottom_bg.png

25 ms

left_bg.png

left_bg.png

28 ms

right_bg.png

right_bg.png

23 ms

left_top.png

left_top.png

27 ms

right_top.png

right_top.png

28 ms

left_bottom.png

left_bottom.png

27 ms

right_bottom.png

right_bottom.png

28 ms

shadow.png

shadow.png

24 ms

45079991258605.js

45079991258605.js

2756 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

894 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

2453 ms

HomeBeanNew.getWeatherCityCode.dwr

HomeBeanNew.getWeatherCityCode.dwr

2191 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1278 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1282 ms

-1.gif

-1.gif

25 ms

20890734366110.js

20890734366110.js

3606 ms

.gif

.gif

5 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

2025 ms

winy2015test-403

winy2015test-403

1242 ms

6631303061191795211.jpg

6631303061191795211.jpg

1608 ms

r

r

815 ms

ad

ad

790 ms

close2.png

close2.png

8 ms

jquery-1.4.2.js

jquery-1.4.2.js

8 ms

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

1117 ms

SEO Factors

devilswrwr.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 Devilswrwr.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 Devilswrwr.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

devilswrwr.blog.163.com

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