35.3 sec in total
6.3 sec
27.7 sec
1.3 sec
Welcome to 7697.blog.163.com homepage info - get ready to check 7697 Blog 163 best content for China right away, or after learning these important things about 7697.blog.163.com
招聘潜规则(转),MSN上07年经典签名,很强的买手机对白,92个神经个性签名,个男人的品位在于选择妻子,人生36个字,捷克钻、奥钻、中东钻的区别,泛谈出口烫图,热转印的过去式与将来式(4),热转印的过去式与将来式(3),7697的网易博客,转印,
Visit 7697.blog.163.comWe analyzed 7697.blog.163.com page load time and found that the first response time was 6.3 sec and then it took 29 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.
7697.blog.163.com performance score
6310 ms
39 ms
62 ms
1367 ms
154 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 7697.blog.163.com, 41% (36 requests) were made to B.bst.126.net and 15% (13 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Gorgon.youdao.com.
Page size can be reduced by 540.8 kB (61%)
883.6 kB
342.8 kB
In fact, the total size of 7697.blog.163.com main page is 883.6 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. 30% of websites need less resources to load. Javascripts take 431.3 kB which makes up the majority of the site volume.
Potential reduce by 92.9 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 92.9 kB or 79% of the original size.
Potential reduce by 9.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. 7697 Blog 163 images are well optimized though.
Potential reduce by 289.4 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 289.4 kB or 67% of the original size.
Potential reduce by 148.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. 7697.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.8 kB or 82% of the original size.
Number of requests can be reduced by 51 (63%)
81
30
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 7697 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 18 to 1 for JavaScripts and as a result speed up the page load time.
7697.blog.163.com
6310 ms
c.css
39 ms
nb.css
62 ms
6630133180817252049.jpg
1367 ms
1.0.0.js
154 ms
xcode.png
22 ms
icon.png
87 ms
top_01.jpg
86 ms
bg.jpg
83 ms
top_02.jpg
89 ms
st_05.jpg
92 ms
st_04.jpg
86 ms
st_07.jpg
93 ms
st_09.jpg
94 ms
st_11.jpg
95 ms
st_14.jpg
97 ms
st_17.jpg
95 ms
st_15.jpg
599 ms
st_20.jpg
97 ms
lnkbar.png
81 ms
image.png
85 ms
arrow24.png
86 ms
newtopbaricon8.png
86 ms
pc.js
34 ms
ph.js
27 ms
crossdomain.html
5432 ms
crossdomain.html
886 ms
crossdomain.html
690 ms
request.s
20269 ms
analyse.png
20266 ms
ava.s
1037 ms
loftericon.png
394 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
836 ms
nb.css
40 ms
BlogCircleBean.getUserShowCircles.dwr
778 ms
ava.s
2609 ms
background.gif
7 ms
player_02.gif
8 ms
player_06.gif
11 ms
player_16.gif
10 ms
player_17.gif
11 ms
stopping.gif
9 ms
player_23.gif
18 ms
timeline_1.gif
18 ms
player_29.gif
17 ms
analyse.png
19997 ms
analytics.js
34 ms
collect
17 ms
UserSpaceBean.getUserSpace.dwr
5101 ms
blogPhotoAd
19789 ms
close_01.png
8 ms
top_bg.png
15 ms
bottom_bg.png
19 ms
left_bg.png
16 ms
right_bg.png
17 ms
left_top.png
18 ms
right_top.png
19 ms
left_bottom.png
20 ms
right_bottom.png
21 ms
shadow.png
15 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1209 ms
AlbumBeanNew.getUserSpace.dwr
1251 ms
sniff.png
2687 ms
SetupBeanNew.getCustomModulesData.dwr
1236 ms
HomeBeanNew.getAccessStatistics.dwr
1459 ms
HomeBeanNew.getMonthStatistics.dwr
1595 ms
UserBeanNew.getVisitor.dwr
1576 ms
NoteBeanNew.getNotesForPrev.dwr
1631 ms
MusicBeanNew.getPlayList.dwr
2041 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
2376 ms
95657519119534.js
219 ms
-1.gif
32 ms
119846774933001.js
80 ms
empty.png
26 ms
5653424907234018942.jpg
1260 ms
BgsBean.getBgsUserByUserId.dwr
937 ms
ava.s
2422 ms
ava.s
735 ms
ava.s
1102 ms
ava.s
961 ms
ava.s
964 ms
ava.s
1100 ms
ava.s
8075 ms
ava.s
4042 ms
ava.s
1479 ms
ava.s
4150 ms
ava.s
7247 ms
list_line.gif
9 ms
7697.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 7697.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 7697.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.
7697.blog.163.com
Open Graph description is not detected on the main page of 7697 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: