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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

14.8 sec in total

First Response

2.1 sec

Resources Loaded

12.5 sec

Page Rendered

242 ms

252224866.blog.163.com screenshot

About Website

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

Visit 252224866.blog.163.com

Key Findings

We analyzed 252224866.blog.163.com page load time and found that the first response time was 2.1 sec and then it took 12.8 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

252224866.blog.163.com performance score

0

Network Requests Diagram

252224866.blog.163.com

2079 ms

c.css

129 ms

b.css

862 ms

6630133180817252049.jpg

9184 ms

xcode.png

317 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original 252224866.blog.163.com, 24% (10 requests) were made to B.bst.126.net and 19% (8 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (9.2 sec) relates to the external source Img.ph.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 566.0 kB (68%)

Content Size

829.7 kB

After Optimization

263.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 49.3 kB

  • Original 63.7 kB
  • After minification 63.7 kB
  • After compression 14.5 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 49.3 kB or 77% of the original size.

Image Optimization

-15%

Potential reduce by 9.2 kB

  • Original 62.7 kB
  • After minification 53.5 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. Obviously, 252224866 Blog 163 needs image optimization as it can save up to 9.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 358.5 kB

  • Original 521.7 kB
  • After minification 521.6 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 358.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.0 kB

  • Original 181.6 kB
  • After minification 177.7 kB
  • After compression 32.7 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. 252224866.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 24 (59%)

Requests Now

41

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

252224866.blog.163.com

252224866.blog.163.com

2079 ms

c.css

c.css

129 ms

b.css

b.css

862 ms

6630133180817252049.jpg

6630133180817252049.jpg

9184 ms

xcode.png

xcode.png

317 ms

1.0.0.js

1.0.0.js

624 ms

pc.js

pc.js

472 ms

ph.js

ph.js

458 ms

icon.png

icon.png

49 ms

lnkbar.png

lnkbar.png

47 ms

image.png

image.png

46 ms

arrow24.png

arrow24.png

46 ms

newtopbaricon8.png

newtopbaricon8.png

46 ms

crossdomain.html

crossdomain.html

3918 ms

crossdomain.html

crossdomain.html

887 ms

crossdomain.html

crossdomain.html

862 ms

request.s

request.s

788 ms

analyse.png

analyse.png

902 ms

ava.s

ava.s

393 ms

loftericon.png

loftericon.png

373 ms

analyse.png

analyse.png

931 ms

analytics.js

analytics.js

40 ms

collect

collect

28 ms

blogPhotoAd

blogPhotoAd

428 ms

close_01.png

close_01.png

29 ms

top_bg.png

top_bg.png

55 ms

bottom_bg.png

bottom_bg.png

67 ms

left_bg.png

left_bg.png

68 ms

right_bg.png

right_bg.png

62 ms

left_top.png

left_top.png

62 ms

right_top.png

right_top.png

73 ms

left_bottom.png

left_bottom.png

96 ms

right_bottom.png

right_bottom.png

119 ms

shadow.png

shadow.png

25 ms

r

r

790 ms

ad

ad

4901 ms

close2.png

close2.png

5 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1009 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1103 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1047 ms

jquery-1.4.2.js

jquery-1.4.2.js

13 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

1848 ms

SEO Factors

252224866.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 252224866.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 252224866.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

252224866.blog.163.com

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