42 sec in total
8.5 sec
32.3 sec
1.2 sec
Welcome to meiguodaigou.blog.163.com homepage info - get ready to check Meiguodaigou Blog 163 best content for China right away, or after learning these important things about meiguodaigou.blog.163.com
2014时尚女包cadice toal机器人包包明星同款,levi's缩水版牛仔裤的小常识,时尚大品牌LOGO与马的不解之缘,卡西欧 G-SHOCK迷彩系列腕表,迷彩当道,Michael Kors2014早春包包系列,洋年货来袭!Coach美国专柜75折华丽绽放啦!,蒂芙尼情人节甄选 —— “心”爱之钻,New Balance私人定制款,DIY你的2014潮鞋,美国知名网站10日知名品牌折扣小汇,...
Visit meiguodaigou.blog.163.comWe analyzed Meiguodaigou.blog.163.com page load time and found that the first response time was 8.5 sec and then it took 33.4 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
meiguodaigou.blog.163.com performance score
8549 ms
659 ms
3094 ms
2875 ms
1678 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Meiguodaigou.blog.163.com, 46% (64 requests) were made to Os.blog.163.com and 9% (12 requests) were made to Api.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 621.2 kB (30%)
2.1 MB
1.4 MB
In fact, the total size of Meiguodaigou.blog.163.com main page is 2.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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 150.6 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 150.6 kB or 81% 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. Meiguodaigou Blog 163 images are well optimized though.
Potential reduce by 311.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 311.5 kB or 69% of the original size.
Potential reduce by 149.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. Meiguodaigou.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.8 kB or 82% of the original size.
Number of requests can be reduced by 40 (30%)
135
95
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meiguodaigou 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.
meiguodaigou.blog.163.com
8549 ms
c.css
659 ms
b.css
3094 ms
3184607886604499554.jpg
2875 ms
2072781728597396481.jpg
1678 ms
83879543159857190.jpg
6970 ms
1492661801596731750.jpg
712 ms
2579436686594497788.png
9460 ms
1255378396229606600.jpg
1509 ms
3025574524762974205.png
2972 ms
830632656373516021.jpg
2473 ms
2235755740112935417.jpg
2421 ms
3313241950961360353.jpg
13594 ms
2483735194512978825.jpg
1774 ms
2455306221947278498.jpg
1772 ms
6597209404635488341.jpg
2462 ms
6630133180817252049.jpg
5560 ms
xcode.png
557 ms
1.0.0.js
555 ms
pc.js
692 ms
ph.js
510 ms
6598279229448899288.jpg
9450 ms
291889550949259998.jpg
3000 ms
5777555371964400691.jpg
1980 ms
icon.png
288 ms
lnkbar.png
279 ms
image.png
281 ms
arrow24.png
280 ms
newtopbaricon8.png
279 ms
5778681271871234347.jpg
2737 ms
5778681271871234276.jpg
559 ms
5778681271871234269.jpg
597 ms
5778681271871234277.jpg
633 ms
5778681271871234278.jpg
679 ms
5778681271871234279.jpg
866 ms
5778681271871234280.jpg
895 ms
5778681271871234282.jpg
1168 ms
5778681271871234281.jpg
1237 ms
crossdomain.html
921 ms
crossdomain.html
677 ms
crossdomain.html
4966 ms
request.s
11810 ms
analyse.png
8461 ms
ava.s
4770 ms
loftericon.png
907 ms
BlogCircleBean.getUserShowCircles.dwr
896 ms
ava.s
885 ms
analyse.png
958 ms
analytics.js
132 ms
collect
275 ms
SetupBeanNew.getResourceModulesData.dwr
809 ms
HomeBeanNew.getFriends.dwr
3605 ms
HomeBeanNew.getAccessStatistics.dwr
1452 ms
UserBeanNew.getVisitor.dwr
3919 ms
NoteBeanNew.getNotesForPrev.dwr
3475 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1594 ms
BlogBeanNew.getBlogClasses.dwr
2402 ms
PhotoBlogBean.getHeadPic.dwr
2997 ms
UserFollowBeanNew.getUserFollows.dwr
2360 ms
TagBeanNew.getHostHotTags.dwr
11532 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
5095 ms
blogPhotoAd
302 ms
close_01.png
53 ms
top_bg.png
23 ms
bottom_bg.png
41 ms
left_bg.png
42 ms
right_bg.png
42 ms
left_top.png
63 ms
right_top.png
59 ms
left_bottom.png
55 ms
right_bottom.png
63 ms
shadow.png
63 ms
r
20079 ms
BgsBean.getBgsUserByUserId.dwr
1939 ms
close2.png
18 ms
ava.s
2359 ms
ava.s
786 ms
ava.s
805 ms
ava.s
790 ms
ava.s
829 ms
ava.s
3305 ms
ava.s
1159 ms
ava.s
1195 ms
ava.s
1264 ms
ava.s
1592 ms
ava.s
1627 ms
ava.s
1682 ms
ava.s
1839 ms
ava.s
2043 ms
ava.s
2151 ms
ava.s
2149 ms
ava.s
2338 ms
ava.s
2511 ms
ava.s
2602 ms
ava.s
2613 ms
ava.s
2762 ms
ava.s
2769 ms
ava.s
2921 ms
ava.s
3004 ms
ava.s
3008 ms
ava.s
3158 ms
ava.s
3161 ms
photoblog.png
402 ms
face50.gif
12 ms
ava.s
3133 ms
ava.s
3192 ms
ava.s
2207 ms
ava.s
5410 ms
ava.s
2397 ms
ava.s
2505 ms
ava.s
4151 ms
ava.s
2792 ms
ava.s
2901 ms
ava.s
3222 ms
ava.s
3318 ms
ava.s
3532 ms
ava.s
3600 ms
ava.s
3619 ms
ava.s
3716 ms
ava.s
3713 ms
ava.s
3613 ms
ava.s
3630 ms
ava.s
5362 ms
ava.s
5082 ms
ava.s
4007 ms
ava.s
6804 ms
ava.s
5220 ms
ava.s
4589 ms
ava.s
5479 ms
ava.s
5647 ms
ava.s
5168 ms
ava.s
5264 ms
ava.s
5460 ms
ava.s
5599 ms
ava.s
5722 ms
ava.s
5291 ms
ava.s
6001 ms
ava.s
5880 ms
meiguodaigou.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 Meiguodaigou.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 Meiguodaigou.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.
meiguodaigou.blog.163.com
Open Graph description is not detected on the main page of Meiguodaigou 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: