28.8 sec in total
2.6 sec
25.1 sec
1.1 sec
Visit xx13656816849.blog.163.com now to see the best up-to-date Xx 13656816849 Blog 163 content for China and also check out these interesting facts you probably never knew about xx13656816849.blog.163.com
Visit xx13656816849.blog.163.comWe analyzed Xx13656816849.blog.163.com page load time and found that the first response time was 2.6 sec and then it took 26.2 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
xx13656816849.blog.163.com performance score
2588 ms
71 ms
69 ms
3113 ms
1487 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Xx13656816849.blog.163.com, 30% (25 requests) were made to B.bst.126.net and 20% (17 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source G.163.com.
Page size can be reduced by 578.0 kB (36%)
1.6 MB
1.0 MB
In fact, the total size of Xx13656816849.blog.163.com main page is 1.6 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 843.6 kB which makes up the majority of the site volume.
Potential reduce by 105.7 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 105.7 kB or 81% of the original size.
Potential reduce by 13.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. Xx 13656816849 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 148.6 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. Xx13656816849.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.6 kB or 82% of the original size.
Number of requests can be reduced by 35 (44%)
80
45
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xx 13656816849 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.
xx13656816849.blog.163.com
2588 ms
c.css
71 ms
nb.css
69 ms
3123246341681623738.jpg
3113 ms
731834939548002429.jpg
1487 ms
1668583662041095724.jpg
1483 ms
1470143803459865631.jpg
1579 ms
6599327064028194459.jpg
2114 ms
3782742212114689086.jpg
1127 ms
1140536605731889453.jpg
936 ms
1377538536122078137.jpg
2495 ms
top_banner.jpg
1197 ms
rssi.png
11 ms
icon.png
17 ms
lnkbar.png
12 ms
top_tab.jpg
13 ms
tap_on.gif
18 ms
bg_web_a.jpg
15 ms
bg_titlebar.gif
17 ms
bg_l_titlebar.gif
117 ms
bg_r_titlebar.gif
115 ms
bg_web_b.jpg
21 ms
image.png
70 ms
6630133180817252049.jpg
19544 ms
1.0.0.js
226 ms
pc.js
279 ms
ph.js
268 ms
xcode.png
65 ms
arrow24.png
30 ms
newtopbaricon8.png
63 ms
crossdomain.html
1735 ms
crossdomain.html
912 ms
crossdomain.html
728 ms
request.s
776 ms
analyse.png
956 ms
ava.s
1854 ms
loftericon.png
444 ms
empty.png
27 ms
ava.s
2064 ms
analyse.png
1199 ms
analytics.js
30 ms
collect
17 ms
blogPhotoAd
590 ms
close_01.png
8 ms
top_bg.png
21 ms
bottom_bg.png
16 ms
left_bg.png
20 ms
right_bg.png
22 ms
left_top.png
21 ms
right_top.png
24 ms
left_bottom.png
25 ms
right_bottom.png
24 ms
shadow.png
19 ms
HomeBeanNew.getAccessStatistics.dwr
4425 ms
UserBeanNew.getVisitor.dwr
1123 ms
BlogBeanNew.getRecentCommentsByOffset.dwr
1391 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
3073 ms
BlogBeanNew.getBlogClasses.dwr
1210 ms
BlogBeanNew.getHostHotBlogs.dwr
1244 ms
r
20130 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1535 ms
SetupBeanNew.getResourceModulesData.dwr
1594 ms
ava.s
6258 ms
ava.s
661 ms
ava.s
2858 ms
ava.s
2728 ms
ava.s
4478 ms
ava.s
7322 ms
ava.s
5021 ms
ava.s
6075 ms
ava.s
9848 ms
ava.s
7368 ms
ava.s
7691 ms
ava.s
6712 ms
ava.s
7243 ms
ava.s
8977 ms
ava.s
9841 ms
close2.png
9 ms
face8.gif
49 ms
face30.gif
42 ms
face50.gif
46 ms
face55.gif
46 ms
face17.gif
47 ms
BgsBean.getBgsUserByUserId.dwr
919 ms
xx13656816849.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 Xx13656816849.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 Xx13656816849.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.
xx13656816849.blog.163.com
Open Graph description is not detected on the main page of Xx 13656816849 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: