30.9 sec in total
2.3 sec
28.1 sec
542 ms
Click here to check amazing Baocai 99 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about baocai99.blog.163.com
Visit baocai99.blog.163.comWe analyzed Baocai99.blog.163.com page load time and found that the first response time was 2.3 sec and then it took 28.6 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 9 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
baocai99.blog.163.com performance score
2282 ms
88 ms
916 ms
19745 ms
108 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Baocai99.blog.163.com, 42% (39 requests) were made to Os.blog.163.com and 15% (14 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 557.8 kB (65%)
860.4 kB
302.6 kB
In fact, the total size of Baocai99.blog.163.com main page is 860.4 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 449.0 kB which makes up the majority of the site volume.
Potential reduce by 88.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 88.2 kB or 80% of the original size.
Potential reduce by 9.4 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. Baocai 99 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.8 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. Baocai99.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.8 kB or 82% of the original size.
Number of requests can be reduced by 31 (38%)
81
50
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Baocai 99 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 12 to 1 for JavaScripts and as a result speed up the page load time.
baocai99.blog.163.com
2282 ms
c.css
88 ms
b.css
916 ms
5781777496613679290.jpg
19745 ms
blog_rec.png
108 ms
6630133180817252049.jpg
1303 ms
xcode.png
131 ms
1.0.0.js
2895 ms
pc.js
152 ms
ph.js
146 ms
5726608401179059854.jpg
19581 ms
5726608401179059852.jpg
19580 ms
5726608401179059848.jpg
19580 ms
5733082325643375573.jpg
19581 ms
5731956425736571643.jpg
19580 ms
5726608401179059850.jpg
19579 ms
icon.png
81 ms
lnkbar.png
83 ms
image.png
90 ms
arrow24.png
89 ms
newtopbaricon8.png
87 ms
crossdomain.html
11080 ms
crossdomain.html
933 ms
crossdomain.html
1029 ms
request.s
19628 ms
analyse.png
2637 ms
ava.s
372 ms
loftericon.png
463 ms
ava.s
738 ms
analyse.png
920 ms
analytics.js
61 ms
collect
37 ms
blogPhotoAd
523 ms
close_01.png
63 ms
top_bg.png
86 ms
bottom_bg.png
87 ms
left_bg.png
86 ms
right_bg.png
81 ms
left_top.png
86 ms
right_top.png
86 ms
left_bottom.png
102 ms
right_bottom.png
105 ms
shadow.png
57 ms
r
19632 ms
close2.png
69 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2988 ms
HomeBeanNew.getFriends.dwr
1360 ms
HomeBeanNew.getAccessStatistics.dwr
1389 ms
UserBeanNew.getVisitor.dwr
2245 ms
NoteBeanNew.getNotesForPrev.dwr
2204 ms
HomeBeanNew.getClassifyModuleData.dwr
2172 ms
ava.s
480 ms
ava.s
923 ms
ava.s
922 ms
ava.s
947 ms
ava.s
2420 ms
ava.s
923 ms
ava.s
1066 ms
ava.s
1283 ms
ava.s
1298 ms
ava.s
1300 ms
ava.s
1337 ms
ava.s
1617 ms
ava.s
1750 ms
ava.s
1762 ms
ava.s
1756 ms
ava.s
3271 ms
ava.s
2126 ms
ava.s
2190 ms
ava.s
2175 ms
ava.s
2198 ms
BgsBean.getBgsUserByUserId.dwr
1147 ms
ava.s
1826 ms
face51.gif
53 ms
face50.gif
52 ms
face50.gif
52 ms
face58.gif
53 ms
ava.s
1721 ms
ava.s
1769 ms
ava.s
1718 ms
ava.s
8410 ms
ava.s
2229 ms
ava.s
2238 ms
ava.s
2296 ms
ava.s
2267 ms
ava.s
2741 ms
ava.s
2743 ms
ava.s
4370 ms
ava.s
2831 ms
ava.s
2862 ms
ava.s
4596 ms
ava.s
3177 ms
baocai99.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 Baocai99.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 Baocai99.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.
baocai99.blog.163.com
Open Graph description is not detected on the main page of Baocai 99 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: