14.7 sec in total
3.4 sec
10.9 sec
381 ms
Welcome to andycapital20121.blog.163.com homepage info - get ready to check Andycapital 20121 Blog 163 best content for China right away, or after learning these important things about andycapital20121.blog.163.com
Visit andycapital20121.blog.163.comWe analyzed Andycapital20121.blog.163.com page load time and found that the first response time was 3.4 sec and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
andycapital20121.blog.163.com performance score
3359 ms
8 ms
709 ms
1072 ms
1062 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 Andycapital20121.blog.163.com, 28% (21 requests) were made to Img.bimg.126.net and 13% (10 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Andycapital20121.blog.163.com.
Page size can be reduced by 599.2 kB (62%)
964.5 kB
365.3 kB
In fact, the total size of Andycapital20121.blog.163.com main page is 964.5 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. 45% of websites need less resources to load. Javascripts take 521.4 kB which makes up the majority of the site volume.
Potential reduce by 78.6 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 78.6 kB or 79% of the original size.
Potential reduce by 10.1 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. Andycapital 20121 Blog 163 images are well optimized though.
Potential reduce by 358.4 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.
Potential reduce by 152.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. Andycapital20121.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.
Number of requests can be reduced by 40 (54%)
74
34
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Andycapital 20121 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 13 to 1 for JavaScripts and as a result speed up the page load time.
andycapital20121.blog.163.com
3359 ms
c.css
8 ms
b.css
709 ms
5770799972522187428.jpg
1072 ms
5779244221823515636.jpg
1062 ms
5779244221823515635.jpg
1071 ms
5791347645822068511.jpg
1072 ms
5791347645822068509.jpg
2731 ms
5791347645822068513.jpg
1136 ms
5780933071683780524.jpg
3223 ms
5791347645822068515.jpg
3242 ms
5791347645822068517.jpg
1604 ms
5791347645822068546.jpg
1605 ms
5791347645822068549.jpg
1691 ms
5791347645822068547.jpg
3682 ms
5776992422009831185.jpg
3728 ms
5776992422009831184.jpg
3826 ms
5776992422009831186.jpg
3263 ms
5780088646753648775.jpg
3746 ms
icon.png
28 ms
6630133180817252049.jpg
3499 ms
xcode.png
20 ms
1.0.0.js
77 ms
pc.js
21 ms
ph.js
19 ms
lnkbar.png
16 ms
image.png
18 ms
arrow24.png
17 ms
newtopbaricon8.png
17 ms
5776992422009831187.jpg
3291 ms
5776992422009831188.jpg
3318 ms
5776992422009831189.jpg
3734 ms
5776992422009831191.jpg
3779 ms
5776992422009831190.jpg
3792 ms
crossdomain.html
1965 ms
crossdomain.html
1082 ms
crossdomain.html
2900 ms
request.s
728 ms
analyse.png
1145 ms
ava.s
678 ms
loftericon.png
4755 ms
ava.s
1339 ms
analyse.png
1167 ms
analytics.js
7 ms
collect
17 ms
blogPhotoAd
597 ms
close_01.png
4 ms
top_bg.png
10 ms
bottom_bg.png
9 ms
left_bg.png
8 ms
right_bg.png
10 ms
left_top.png
7 ms
right_top.png
10 ms
left_bottom.png
9 ms
right_bottom.png
10 ms
shadow.png
9 ms
r
3312 ms
HomeBeanNew.getFriends.dwr
1015 ms
HomeBeanNew.getAccessStatistics.dwr
1457 ms
UserBeanNew.getVisitor.dwr
1471 ms
NoteBeanNew.getNotesForPrev.dwr
2951 ms
HomeBeanNew.getClassifyModuleData.dwr
1460 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1471 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
3300 ms
close2.png
3 ms
ava.s
341 ms
ava.s
506 ms
ava.s
677 ms
ava.s
719 ms
ava.s
1317 ms
ava.s
894 ms
ava.s
883 ms
ad
1220 ms
jquery-1.4.2.js
8 ms
0316ykt-300-250.jpg
808 ms
andycapital20121.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 Andycapital20121.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 Andycapital20121.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.
andycapital20121.blog.163.com
Open Graph description is not detected on the main page of Andycapital 20121 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: