26.8 sec in total
2.4 sec
24.2 sec
305 ms
Welcome to fengweikid.blog.163.com homepage info - get ready to check Fengweikid Blog 163 best content for China right away, or after learning these important things about fengweikid.blog.163.com
四川升和制药参展第十八次全国眼科学术大会,2013年7月四川升和制药半年工作总结会,四川升和制药对阿坝州希望小学进行捐赠,2013年四川升和药业春游活动,润年家私名品微博活动正式开始啦!,珍珠粉属于哪一类保健品,皮肤不好对症下药的招,快来学习吧,推拿按摩千万不要自己随意发挥,吃冬瓜玉米清汤既能消除水肿还能减肥,喝水也能预防各种疾病的,教教大家可以试试,四川升和制药业的网易博客,四川升和制药业,
Visit fengweikid.blog.163.comWe analyzed Fengweikid.blog.163.com page load time and found that the first response time was 2.4 sec and then it took 24.5 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 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fengweikid.blog.163.com performance score
2369 ms
1356 ms
1025 ms
939 ms
48 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Fengweikid.blog.163.com, 27% (19 requests) were made to Os.blog.163.com and 14% (10 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 Img.bimg.126.net.
Page size can be reduced by 546.6 kB (52%)
1.0 MB
503.3 kB
In fact, the total size of Fengweikid.blog.163.com main page is 1.0 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. Javascripts take 489.7 kB which makes up the majority of the site volume.
Potential reduce by 61.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 61.2 kB or 79% of the original size.
Potential reduce by 9.2 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. Fengweikid Blog 163 images are well optimized though.
Potential reduce by 326.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 326.6 kB or 67% of the original size.
Potential reduce by 149.5 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. Fengweikid.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.5 kB or 82% of the original size.
Number of requests can be reduced by 28 (43%)
65
37
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fengweikid 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 13 to 1 for JavaScripts and as a result speed up the page load time.
fengweikid.blog.163.com
2369 ms
c.css
1356 ms
b.css
1025 ms
6630133180817252049.jpg
939 ms
xcode.png
48 ms
1.0.0.js
100 ms
pc.js
1845 ms
ph.js
1928 ms
5781777496613668265.jpg
20452 ms
icon.png
80 ms
lnkbar.png
80 ms
image.png
81 ms
arrow24.png
82 ms
newtopbaricon8.png
83 ms
5782621921543800209.jpg
20442 ms
5782621921543800253.jpg
2506 ms
5779244221823300646.jpg
2746 ms
5781777496613668331.jpg
1736 ms
5782621921543800348.jpg
5714 ms
5782621921543800347.jpg
20440 ms
5779244221823300628.jpg
20440 ms
crossdomain.html
677 ms
crossdomain.html
764 ms
crossdomain.html
7514 ms
request.s
19878 ms
analyse.png
4297 ms
ava.s
2847 ms
loftericon.png
458 ms
ava.s
11643 ms
analyse.png
2007 ms
analytics.js
59 ms
collect
24 ms
HomeBeanNew.getAccessStatistics.dwr
1500 ms
UserBeanNew.getVisitor.dwr
1474 ms
NoteBeanNew.getNotesForPrev.dwr
1440 ms
HomeBeanNew.getClassifyModuleData.dwr
2923 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
2090 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2295 ms
blogPhotoAd
1074 ms
close_01.png
18 ms
top_bg.png
20 ms
bottom_bg.png
23 ms
left_bg.png
26 ms
right_bg.png
21 ms
left_top.png
20 ms
right_top.png
23 ms
left_bottom.png
29 ms
right_bottom.png
23 ms
shadow.png
11 ms
BgsBean.getBgsUserByUserId.dwr
2420 ms
ava.s
2797 ms
ava.s
7459 ms
ava.s
4494 ms
ava.s
972 ms
ava.s
6019 ms
ava.s
1966 ms
ava.s
2914 ms
ava.s
3291 ms
ava.s
4391 ms
ava.s
5226 ms
ava.s
8499 ms
ava.s
4992 ms
ava.s
6978 ms
ava.s
5723 ms
ava.s
6211 ms
r
8064 ms
close2.png
6 ms
ava.s
7400 ms
ad
1949 ms
jquery-1.4.2.js
148 ms
ad.bid.material_f84d827cd06e43a28ef019b53849c47d
7232 ms
fengweikid.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 Fengweikid.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 Fengweikid.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.
fengweikid.blog.163.com
Open Graph description is not detected on the main page of Fengweikid 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: