36.9 sec in total
4.6 sec
30.1 sec
2.2 sec
Welcome to jinyange222.blog.163.com homepage info - get ready to check Jinyange 222 Blog 163 best content for China right away, or after learning these important things about jinyange222.blog.163.com
Visit jinyange222.blog.163.comWe analyzed Jinyange222.blog.163.com page load time and found that the first response time was 4.6 sec and then it took 32.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 8 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
jinyange222.blog.163.com performance score
4580 ms
17 ms
936 ms
2546 ms
374 ms
Our browser made a total of 254 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Jinyange222.blog.163.com, 39% (99 requests) were made to Os.blog.163.com and 9% (24 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Api.blog.163.com.
Page size can be reduced by 1.1 MB (25%)
4.5 MB
3.3 MB
In fact, the total size of Jinyange222.blog.163.com main page is 4.5 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. 60% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 163.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 163.8 kB or 81% of the original size.
Potential reduce by 38.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. Jinyange 222 Blog 163 images are well optimized though.
Potential reduce by 752.6 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 752.6 kB or 64% of the original size.
Potential reduce by 150.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. Jinyange222.blog.163.com needs all CSS files to be minified and compressed as it can save up to 150.8 kB or 82% of the original size.
Number of requests can be reduced by 54 (22%)
242
188
The browser has sent 242 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jinyange 222 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 22 to 1 for JavaScripts and as a result speed up the page load time.
jinyange222.blog.163.com
4580 ms
c.css
17 ms
b.css
936 ms
6598264935856929906.jpg
2546 ms
6631256881704553420.jpg
374 ms
6598078018880033552.jpg
3142 ms
4910049493840989908.jpg
2209 ms
6598082416926535768.jpg
1804 ms
6631405315774718076.jpg
1227 ms
6598074720344097837.jpg
20471 ms
1999035284699562510.jpg
1985 ms
6598068123275586375.jpg
2237 ms
5127348175761882919.jpg
8688 ms
icon.png
127 ms
585186476582245386.jpg
1332 ms
2583095861274588049.jpg
2422 ms
585186476582245384.jpg
6024 ms
2014516408319860625.jpg
1771 ms
2014516408319860624.jpg
2267 ms
2014516408319860626.jpg
2724 ms
2014516408319860712.jpg
2879 ms
2014516408319860758.jpg
3172 ms
2014516408319860631.jpg
3350 ms
2014516408319860673.jpg
10922 ms
2014516408319860632.jpg
3622 ms
lnkbar.png
58 ms
6630133180817252049.jpg
7781 ms
xcode.png
56 ms
1.0.0.js
91 ms
pc.js
58 ms
ph.js
57 ms
4845310249197930735.jpg
1694 ms
585186476582245385.jpg
8535 ms
6631318454355296372.jpg
1512 ms
6631445997704911433.jpg
1268 ms
6631351439704858133.jpg
4866 ms
image.png
8 ms
arrow24.png
9 ms
newtopbaricon8.png
11 ms
crossdomain.html
790 ms
crossdomain.html
2259 ms
crossdomain.html
4198 ms
request.s
20431 ms
analyse.png
1228 ms
ava.s
2055 ms
loftericon.png
1586 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
4037 ms
nb.css
22 ms
background.gif
7 ms
player_02.gif
33 ms
player_06.gif
21 ms
player_16.gif
20 ms
player_17.gif
8 ms
player_23.gif
9 ms
timeline_1.gif
11 ms
player_29.gif
20 ms
ava.s
3985 ms
analyse.png
2904 ms
analytics.js
9 ms
collect
12 ms
SetupBeanNew.getCustomModulesData.dwr
856 ms
HomeBeanNew.getFriends.dwr
1370 ms
HomeBeanNew.getAccessStatistics.dwr
1280 ms
HomeBeanNew.getMonthStatistics.dwr
20473 ms
HomeBeanNew.getWeatherCityCode.dwr
3095 ms
UserBeanNew.getVisitor.dwr
20472 ms
BlogBeanNew.getRecentCommentsByOffset.dwr
1652 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
2128 ms
UserFollowBeanNew.getUserFollows.dwr
2153 ms
BlogBeanNew.getRecentBlogs.dwr
2524 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2859 ms
blogPhotoAd
3556 ms
close_01.png
14 ms
top_bg.png
15 ms
bottom_bg.png
13 ms
left_bg.png
12 ms
right_bg.png
10 ms
left_top.png
12 ms
right_top.png
13 ms
left_bottom.png
14 ms
right_bottom.png
14 ms
shadow.png
12 ms
873979802786807238.jpg
9140 ms
6608760873795008585.jpg
2044 ms
1137158906011706705.jpg
2339 ms
1172906227954309477.jpg
849 ms
1172906227954309474.jpg
1936 ms
1172906227954309471.jpg
6816 ms
1172906227954309468.jpg
6483 ms
4239294624240162772.jpg
5334 ms
4239294624240162769.jpg
4177 ms
4239294624240162766.jpg
5787 ms
1480276902522362201.jpg
4763 ms
1480276902522362198.jpg
5467 ms
1480276902522362195.jpg
8987 ms
586030901512112015.jpg
15089 ms
586030901512112012.jpg
6374 ms
BgsBean.getBgsUserByUserId.dwr
20210 ms
638385247196874300.jpg
2429 ms
ava.s
475 ms
ava.s
2942 ms
ava.s
946 ms
ava.s
947 ms
ava.s
967 ms
ava.s
1437 ms
ava.s
1436 ms
ava.s
3354 ms
ava.s
1904 ms
ava.s
1910 ms
ava.s
1985 ms
ava.s
4266 ms
ava.s
6402 ms
ava.s
2391 ms
ava.s
2460 ms
ava.s
2877 ms
ava.s
4887 ms
ava.s
5003 ms
ava.s
4928 ms
ava.s
5129 ms
ava.s
4743 ms
ava.s
5197 ms
ava.s
5342 ms
ava.s
7208 ms
ava.s
5447 ms
ava.s
5630 ms
ava.s
5635 ms
ava.s
5792 ms
ava.s
7323 ms
ava.s
6136 ms
ava.s
7822 ms
ava.s
6253 ms
ava.s
6566 ms
ava.s
6688 ms
ava.s
6840 ms
2062085679383944713.jpg
3591 ms
UserSpaceBean.getUserSpace.dwr
3503 ms
PhotoBlogBean.getHeadPic.dwr
1220 ms
UserSpaceBean.getUserSpace.dwr
2077 ms
face55.gif
10 ms
face39.gif
15 ms
ava.s
6568 ms
ava.s
6217 ms
ava.s
6434 ms
ava.s
7564 ms
ava.s
6162 ms
ava.s
6234 ms
837106580738882649.jpg
2875 ms
.gif
925 ms
ava.s
6055 ms
ava.s
5977 ms
ava.s
6139 ms
ava.s
6152 ms
PhotoBlogBean.getPictureSets75PictureUrl.dwr
518 ms
ava.s
5900 ms
ava.s
5848 ms
r
891 ms
6598266035367963874.jpg
404 ms
4900760819609537897.jpg
511 ms
6631393221146406665.jpg
1582 ms
6631393221146406671.jpg
438 ms
6631425106983599336.jpg
1434 ms
6598124198367978593.jpg
460 ms
4902449669469801812.jpg
1689 ms
6598214358321458762.jpg
20253 ms
4944670915976388806.jpg
853 ms
6631262379262692296.jpg
956 ms
6598158283227809639.jpg
1282 ms
6598074720344097833.jpg
2642 ms
6631363534331812655.jpg
2135 ms
6598253940739423391.jpg
2493 ms
6631393221146406672.jpg
1150 ms
6598179173949367539.jpg
1836 ms
6631201906123167900.jpg
694 ms
6631404216262673946.jpg
1111 ms
6631385524565002215.jpg
20251 ms
1629458640278471145.jpg
2851 ms
4849250898871715862.jpg
3003 ms
4910049493840989903.jpg
2368 ms
4828421750594899554.jpg
2845 ms
6598283627553374022.jpg
3235 ms
6598289125111512885.jpg
3979 ms
1999035284699562493.jpg
1111 ms
6631425106983599323.jpg
401 ms
6631205204658051205.jpg
745 ms
6631204105146423445.jpg
1043 ms
6631429505030110384.jpg
1046 ms
6598086814972634338.jpg
20247 ms
1156299204427929193.jpg
2863 ms
4859946947986792003.jpg
1271 ms
6598191268577270374.jpg
2184 ms
6598172576878968433.jpg
1484 ms
6631389922610888317.jpg
2514 ms
ava.s
5479 ms
ava.s
6529 ms
ava.s
5247 ms
ad
843 ms
AlbumBeanNew.getUserSpace.dwr
801 ms
sniff.png
376 ms
close2.png
4 ms
ava.s
4482 ms
jquery-1.4.2.js
18 ms
ad.bid.material_f84d827cd06e43a28ef019b53849c47d
2023 ms
846395254970771785.jpg
2490 ms
28587316893400.js
1069 ms
ava.s
4019 ms
ava.s
3944 ms
ava.s
4062 ms
ava.s
6671 ms
ava.s
4092 ms
ava.s
5071 ms
ava.s
3978 ms
ava.s
4900 ms
-1.gif
9 ms
12094642400852.js
1430 ms
empty.png
7 ms
ava.s
4116 ms
ava.s
4156 ms
ava.s
4139 ms
ava.s
4084 ms
ava.s
4008 ms
ava.s
4068 ms
ava.s
4210 ms
ava.s
4044 ms
ava.s
7315 ms
ava.s
3785 ms
6631249185123574373.jpg
1818 ms
ava.s
3788 ms
ava.s
4008 ms
ava.s
4684 ms
ava.s
3927 ms
1807913775414403039.jpg
1725 ms
ava.s
3857 ms
ava.s
4034 ms
ava.s
3963 ms
ava.s
4109 ms
ava.s
4278 ms
ava.s
5552 ms
ava.s
4886 ms
ava.s
4134 ms
ava.s
5414 ms
ava.s
5265 ms
ava.s
4384 ms
ava.s
4801 ms
ava.s
4757 ms
ava.s
5120 ms
ava.s
5157 ms
ava.s
11120 ms
ava.s
4907 ms
ava.s
6094 ms
ava.s
4897 ms
ava.s
4720 ms
ava.s
4813 ms
ava.s
4709 ms
ava.s
5831 ms
jinyange222.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 Jinyange222.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 Jinyange222.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.
jinyange222.blog.163.com
Open Graph description is not detected on the main page of Jinyange 222 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: