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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

21 sec in total

First Response

5.1 sec

Resources Loaded

15.5 sec

Page Rendered

413 ms

charmingkids.blog.163.com screenshot

About Website

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

Visit charmingkids.blog.163.com

Key Findings

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

charmingkids.blog.163.com performance score

0

Network Requests Diagram

charmingkids.blog.163.com

5062 ms

c.css

558 ms

nb.css

556 ms

6630133180817252049.jpg

2103 ms

1.0.0.js

78 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Charmingkids.blog.163.com, 39% (27 requests) were made to B.bst.126.net and 13% (9 requests) were made to Api.blog.163.com. The less responsive or slowest element that took the longest time to load (6.6 sec) relates to the external source Api.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 591.3 kB (55%)

Content Size

1.1 MB

After Optimization

483.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 73.5 kB

  • Original 94.3 kB
  • After minification 94.3 kB
  • After compression 20.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 73.5 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 10.2 kB

  • Original 277.1 kB
  • After minification 266.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. Charmingkids Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.6 kB

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

CSS Optimization

-82%

Potential reduce by 149.0 kB

  • Original 181.6 kB
  • After minification 177.8 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. Charmingkids.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 40 (58%)

Requests Now

69

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

charmingkids.blog.163.com

charmingkids.blog.163.com

5062 ms

c.css

c.css

558 ms

nb.css

nb.css

556 ms

6630133180817252049.jpg

6630133180817252049.jpg

2103 ms

1.0.0.js

1.0.0.js

78 ms

xcode.png

xcode.png

547 ms

web.gif

web.gif

62 ms

icon.png

icon.png

60 ms

lnkbar.png

lnkbar.png

58 ms

image.png

image.png

59 ms

arrow24.png

arrow24.png

59 ms

newtopbaricon8.png

newtopbaricon8.png

60 ms

banner.jpg

banner.jpg

64 ms

tab.jpg

tab.jpg

58 ms

bg-b.gif

bg-b.gif

60 ms

bg-a.gif

bg-a.gif

61 ms

bg-c.gif

bg-c.gif

60 ms

bg-d.gif

bg-d.gif

62 ms

bg-e.gif

bg-e.gif

61 ms

bg-f.gif

bg-f.gif

62 ms

bg-g.gif

bg-g.gif

63 ms

bg-h.gif

bg-h.gif

64 ms

web-c.jpg

web-c.jpg

64 ms

web-d.jpg

web-d.jpg

64 ms

web-b.jpg

web-b.jpg

65 ms

pc.js

pc.js

9 ms

ph.js

ph.js

7 ms

crossdomain.html

crossdomain.html

641 ms

crossdomain.html

crossdomain.html

1130 ms

crossdomain.html

crossdomain.html

1146 ms

request.s

request.s

661 ms

analyse.png

analyse.png

1060 ms

ava.s

ava.s

1453 ms

loftericon.png

loftericon.png

477 ms

ava.s

ava.s

1808 ms

analyse.png

analyse.png

1073 ms

analytics.js

analytics.js

8 ms

collect

collect

16 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

6168 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

6645 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1004 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1338 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

1683 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1987 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

3566 ms

blogPhotoAd

blogPhotoAd

538 ms

close_01.png

close_01.png

6 ms

top_bg.png

top_bg.png

4 ms

bottom_bg.png

bottom_bg.png

5 ms

left_bg.png

left_bg.png

14 ms

right_bg.png

right_bg.png

13 ms

left_top.png

left_top.png

13 ms

right_top.png

right_top.png

13 ms

left_bottom.png

left_bottom.png

14 ms

right_bottom.png

right_bottom.png

13 ms

shadow.png

shadow.png

13 ms

ava.s

ava.s

411 ms

ava.s

ava.s

2446 ms

ava.s

ava.s

769 ms

ava.s

ava.s

2746 ms

ava.s

ava.s

831 ms

r

r

4235 ms

face1.gif

face1.gif

5 ms

ava.s

ava.s

375 ms

face73.gif

face73.gif

5 ms

close2.png

close2.png

4 ms

ad

ad

1162 ms

jquery-1.4.2.js

jquery-1.4.2.js

7 ms

0316ykt-300-250.jpg

0316ykt-300-250.jpg

2973 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

694 ms

SEO Factors

charmingkids.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 Charmingkids.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 Charmingkids.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

charmingkids.blog.163.com

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