27.6 sec in total
2.8 sec
24.3 sec
431 ms
Visit riyueliuguang.blog.163.com now to see the best up-to-date Riyueliuguang Blog 163 content for China and also check out these interesting facts you probably never knew about riyueliuguang.blog.163.com
Visit riyueliuguang.blog.163.comWe analyzed Riyueliuguang.blog.163.com page load time and found that the first response time was 2.8 sec and then it took 24.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
riyueliuguang.blog.163.com performance score
2822 ms
115 ms
134 ms
48 ms
41 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Riyueliuguang.blog.163.com, 38% (33 requests) were made to Os.blog.163.com and 25% (22 requests) were made to B.bst.126.net. 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 562.9 kB (51%)
1.1 MB
536.6 kB
In fact, the total size of Riyueliuguang.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. 35% of websites need less resources to load. Javascripts take 449.0 kB which makes up the majority of the site volume.
Potential reduce by 90.8 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 90.8 kB or 79% of the original size.
Potential reduce by 12.7 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. Riyueliuguang 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.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. Riyueliuguang.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 31 (38%)
82
51
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Riyueliuguang 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.
riyueliuguang.blog.163.com
2822 ms
c.css
115 ms
nb.css
134 ms
simiao_dingbu-shang.jpg
48 ms
blog_rec.png
41 ms
simiao_zhongbu-di.jpg
41 ms
simiao_neir-shang02.jpg
43 ms
simiao_neir-shang01.jpg
42 ms
simiao_neir-shang03.jpg
42 ms
simiao_neir-zuo.jpg
64 ms
goodbloghead.png
61 ms
6630133180817252049.jpg
1534 ms
1.0.0.js
91 ms
pc.js
68 ms
ph.js
66 ms
icon.png
17 ms
lnkbar.png
27 ms
image.png
29 ms
arrow24.png
30 ms
newtopbaricon8.png
30 ms
simiao_neir-you.jpg
23 ms
simiao_neir-xia01.jpg
23 ms
simiao_neir-xia03.jpg
24 ms
simiao_neir-xia02.jpg
23 ms
simiao_dilan-bei.jpg
36 ms
xcode.png
29 ms
crossdomain.html
646 ms
crossdomain.html
1911 ms
crossdomain.html
806 ms
request.s
794 ms
analyse.png
20410 ms
ava.s
785 ms
loftericon.png
367 ms
ava.s
740 ms
analyse.png
20135 ms
analytics.js
50 ms
collect
21 ms
HomeBeanNew.getFriends.dwr
667 ms
HomeBeanNew.getAccessStatistics.dwr
944 ms
UserBeanNew.getVisitor.dwr
956 ms
NoteBeanNew.getNotesForPrev.dwr
1058 ms
HomeBeanNew.getClassifyModuleData.dwr
1045 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1112 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
3875 ms
blogPhotoAd
19923 ms
close_01.png
18 ms
top_bg.png
29 ms
bottom_bg.png
15 ms
left_bg.png
16 ms
right_bg.png
16 ms
left_top.png
16 ms
right_top.png
33 ms
left_bottom.png
16 ms
right_bottom.png
14 ms
shadow.png
12 ms
ava.s
426 ms
ava.s
360 ms
ava.s
718 ms
ava.s
724 ms
ava.s
743 ms
ava.s
812 ms
ava.s
813 ms
ava.s
883 ms
ava.s
1082 ms
ava.s
2588 ms
ava.s
2576 ms
ava.s
1221 ms
ava.s
3532 ms
ava.s
1319 ms
ava.s
1452 ms
BgsBean.getBgsUserByUserId.dwr
682 ms
ava.s
2809 ms
ava.s
3080 ms
ava.s
1531 ms
ava.s
2995 ms
ava.s
3007 ms
ava.s
4045 ms
ava.s
3605 ms
ava.s
3360 ms
ava.s
4715 ms
ava.s
3506 ms
ava.s
4050 ms
ava.s
4154 ms
ava.s
4339 ms
ava.s
4010 ms
ava.s
4837 ms
ava.s
4345 ms
riyueliuguang.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 Riyueliuguang.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 Riyueliuguang.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.
riyueliuguang.blog.163.com
Open Graph description is not detected on the main page of Riyueliuguang 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: