21 sec in total
5.1 sec
15.5 sec
413 ms
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.comWe 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.
charmingkids.blog.163.com performance score
5062 ms
558 ms
556 ms
2103 ms
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 size can be reduced by 591.3 kB (55%)
1.1 MB
483.5 kB
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.
Potential reduce by 73.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 73.5 kB or 78% of the original size.
Potential reduce by 10.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. Charmingkids Blog 163 images are well optimized though.
Potential reduce by 358.6 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.
Potential reduce by 149.0 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.
Number of requests can be reduced by 40 (58%)
69
29
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.
charmingkids.blog.163.com
5062 ms
c.css
558 ms
nb.css
556 ms
6630133180817252049.jpg
2103 ms
1.0.0.js
78 ms
xcode.png
547 ms
web.gif
62 ms
icon.png
60 ms
lnkbar.png
58 ms
image.png
59 ms
arrow24.png
59 ms
newtopbaricon8.png
60 ms
banner.jpg
64 ms
tab.jpg
58 ms
bg-b.gif
60 ms
bg-a.gif
61 ms
bg-c.gif
60 ms
bg-d.gif
62 ms
bg-e.gif
61 ms
bg-f.gif
62 ms
bg-g.gif
63 ms
bg-h.gif
64 ms
web-c.jpg
64 ms
web-d.jpg
64 ms
web-b.jpg
65 ms
pc.js
9 ms
ph.js
7 ms
crossdomain.html
641 ms
crossdomain.html
1130 ms
crossdomain.html
1146 ms
request.s
661 ms
analyse.png
1060 ms
ava.s
1453 ms
loftericon.png
477 ms
ava.s
1808 ms
analyse.png
1073 ms
analytics.js
8 ms
collect
16 ms
HomeBeanNew.getFriends.dwr
6168 ms
HomeBeanNew.getAccessStatistics.dwr
6645 ms
UserBeanNew.getVisitor.dwr
1004 ms
NoteBeanNew.getNotesForPrev.dwr
1338 ms
HomeBeanNew.getClassifyModuleData.dwr
1683 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1987 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
3566 ms
blogPhotoAd
538 ms
close_01.png
6 ms
top_bg.png
4 ms
bottom_bg.png
5 ms
left_bg.png
14 ms
right_bg.png
13 ms
left_top.png
13 ms
right_top.png
13 ms
left_bottom.png
14 ms
right_bottom.png
13 ms
shadow.png
13 ms
ava.s
411 ms
ava.s
2446 ms
ava.s
769 ms
ava.s
2746 ms
ava.s
831 ms
r
4235 ms
face1.gif
5 ms
ava.s
375 ms
face73.gif
5 ms
close2.png
4 ms
ad
1162 ms
jquery-1.4.2.js
7 ms
0316ykt-300-250.jpg
2973 ms
BgsBean.getBgsUserByUserId.dwr
694 ms
charmingkids.blog.163.com SEO score
ZH
ZH
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.
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: