28 sec in total
1.7 sec
25.5 sec
735 ms
Click here to check amazing Fuzhenggang 2012 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about fuzhenggang2012.blog.163.com
Visit fuzhenggang2012.blog.163.comWe analyzed Fuzhenggang2012.blog.163.com page load time and found that the first response time was 1.7 sec and then it took 26.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fuzhenggang2012.blog.163.com performance score
1711 ms
1688 ms
2236 ms
2532 ms
1331 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Fuzhenggang2012.blog.163.com, 36% (22 requests) were made to B.bst.126.net and 15% (9 requests) were made to Api.blog.163.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Lofter.com.
Page size can be reduced by 558.2 kB (47%)
1.2 MB
631.5 kB
In fact, the total size of Fuzhenggang2012.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. 30% of websites need less resources to load. Images take 450.7 kB which makes up the majority of the site volume.
Potential reduce by 86.2 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 86.2 kB or 80% of the original size.
Potential reduce by 12.3 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. Fuzhenggang 2012 Blog 163 images are well optimized though.
Potential reduce by 310.5 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 310.5 kB or 69% of the original size.
Potential reduce by 149.2 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. Fuzhenggang2012.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.
Number of requests can be reduced by 33 (60%)
55
22
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fuzhenggang 2012 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 11 to 1 for JavaScripts and as a result speed up the page load time.
fuzhenggang2012.blog.163.com
1711 ms
c.css
1688 ms
b.css
2236 ms
6630133180817252049.jpg
2532 ms
xcode.png
1331 ms
1.0.0.js
384 ms
pc.js
1251 ms
ph.js
1291 ms
5728860200992701723.jpg
681 ms
goodbloghead.png
131 ms
5762074248244591780.jpg
3816 ms
5762074248244591781.jpg
946 ms
5728860200992701720.jpg
665 ms
icon.png
124 ms
lnkbar.png
127 ms
image.png
126 ms
arrow24.png
125 ms
newtopbaricon8.png
126 ms
crossdomain.html
650 ms
crossdomain.html
613 ms
crossdomain.html
635 ms
request.s
1775 ms
analyse.png
19714 ms
empty.png
64 ms
ava.s
1299 ms
loftericon.png
347 ms
ava.s
792 ms
analyse.png
20445 ms
analytics.js
20 ms
collect
60 ms
HomeBeanNew.getFriends.dwr
729 ms
HomeBeanNew.getAccessStatistics.dwr
1118 ms
UserBeanNew.getVisitor.dwr
19755 ms
NoteBeanNew.getNotesForPrev.dwr
1081 ms
HomeBeanNew.getClassifyModuleData.dwr
1095 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1160 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1310 ms
blogPhotoAd
20233 ms
close_01.png
20 ms
top_bg.png
31 ms
bottom_bg.png
30 ms
left_bg.png
32 ms
right_bg.png
29 ms
left_top.png
33 ms
right_top.png
32 ms
left_bottom.png
34 ms
right_bottom.png
34 ms
shadow.png
17 ms
face50.gif
48 ms
face53.gif
50 ms
face63.gif
42 ms
face84.gif
57 ms
face1.gif
50 ms
face73.gif
50 ms
face82.gif
100 ms
face74.gif
97 ms
face51.gif
95 ms
face39.gif
101 ms
face8.gif
107 ms
BgsBean.getBgsUserByUserId.dwr
767 ms
ava.s
407 ms
fuzhenggang2012.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 Fuzhenggang2012.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 Fuzhenggang2012.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.
fuzhenggang2012.blog.163.com
Open Graph description is not detected on the main page of Fuzhenggang 2012 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: