64 sec in total
2.2 sec
60.8 sec
1 sec
Visit fandongxi.com now to see the best up-to-date Fandongxi content for China and also check out these interesting facts you probably never knew about fandongxi.com
想低价可靠地在网上购买最新最时尚最潮流的衣服,鞋子,包包等正品吗?想知道东西质量怎么样?想知道潮人是怎么搭配的吗?翻东西社会化电商导购社区,和网购达人一起快速发现最靠谱的正品淘宝网店并分享购物经验。
Visit fandongxi.comWe analyzed Fandongxi.com page load time and found that the first response time was 2.2 sec and then it took 61.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 58 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fandongxi.com performance score
2206 ms
19699 ms
19698 ms
19699 ms
19698 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Fandongxi.com, 60% (60 requests) were made to Img.fandongxi.com and 7% (7 requests) were made to Misc.fandongxi.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Img.fandongxi.com.
Page size can be reduced by 321.6 kB (13%)
2.5 MB
2.2 MB
In fact, the total size of Fandongxi.com main page is 2.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. 15% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 56.0 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. This page needs HTML code to be minified as it can gain 9.4 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 56.0 kB or 79% of the original size.
Potential reduce by 231.1 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. Fandongxi images are well optimized though.
Potential reduce by 34.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 34.5 kB or 50% of the original size.
Number of requests can be reduced by 15 (48%)
31
16
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fandongxi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
fandongxi.com
2206 ms
core.css&20141014113704
19699 ms
index.css&20141014113704
19698 ms
sea.js&20141014113704
19699 ms
global.js&20141014113704
19698 ms
sdk.js
744 ms
lazyload.js&20141014113704
19721 ms
connect.6.1
263 ms
deskdown.png
849 ms
50.jpg
19986 ms
__fan.gif
1207 ms
hot.png
5370 ms
new.png
3730 ms
50.jpg
19985 ms
50.jpg
19986 ms
15ab3f7041dcca977fa1f88b67790b04.jpg
4605 ms
a5094280dc234d4834de7ad90dac66bf.jpg
4557 ms
05b4d9c08182ea0a976e78774c39d3b7.jpg
9356 ms
fc67eeb7e73a1518918a01e21d8d8915.jpg
6124 ms
64d08779532d0ba2e8bad7f16a372966.jpg
6443 ms
4a600c4335f977d085cadea19e0249b3.jpg
10541 ms
e421ff038d519b293cd7b505b0086ca6.jpg
9660 ms
056e1723c4a2994a2e1eafd61ac64535.jpg
11143 ms
60_60.jpg
19984 ms
60_60.jpg
19984 ms
60_60.jpg
19985 ms
60_60.jpg
19985 ms
9d4ba501368b96af9bd2c88b39184818.jpg
19985 ms
020fec00ba8ad8b8d8521bc6fa07db01.jpg
19985 ms
744abde05477a188ee0ba1335e755e51.jpg
19986 ms
6410813854440cc9622c6ded724908f6.jpg
19987 ms
c65ba5fbf53ec982c06c910c7d3aee14.jpg
19986 ms
e3999b0f591f60e598e06ea9f977d2bb.jpg
19987 ms
c9ae23b133be895e67149ad3e3226557.jpg
19988 ms
23c219b53466041d55e7bbce5818cb35.jpg
19989 ms
b26c4775651ee8dad377a26c1200209a.jpg
19989 ms
17f5d5fbc9c06d2e79256ea9047309af.jpg
19989 ms
e2d7456cb2638f70335c02c13c819ba2.jpg
19990 ms
5e5e666334ec5f4be7adb38aa96ee946.jpg
19990 ms
d8b3b3077c41c8ecb8ccb2c10dc31b20.jpg
19991 ms
eb7ad2dacdc60933fe4d46fa07ab0068.jpg
19990 ms
a2e8fd4fed897a2c0bf87fff5d65dc4c.jpg
19990 ms
c2ceed4e6b54592cad393b5e8a3cc939.jpg
19991 ms
4181b52bcfc8a3c5a66cc76a5d26c61a.jpg
19991 ms
7227d61d57bbbe79d7bcb7b0bc1a2bb0.jpg
19990 ms
ab1973aa727be6c3b2bc49a0e53cf698.jpg
19990 ms
5c6645c3a06f399c920942780c47b899.jpg
19990 ms
fbbbd814c36340049b0cd9d51c4b83ba.jpg
19990 ms
guide_arrow.gif
730 ms
index.php
2268 ms
ga.js
8 ms
trace.js
8015 ms
h.js
1343 ms
stat.php
1443 ms
__utm.gif
12 ms
hm.gif
447 ms
stat.htm
242 ms
core.php
1560 ms
jquery-1.6.2.min.js
19670 ms
9.gif
1012 ms
app.gif
15983 ms
8ce2c37f9bc4772caf672e1d5692004e.jpg
20425 ms
5741d2b1cd734879eaca5c2f49c451bb.jpg
20378 ms
d03979196026ecdd0d71d3afa9a78838.jpg
19860 ms
3244a1286684e4e8f2f8afc33e363e31.jpg
19540 ms
v.do
1005 ms
zz.js
3552 ms
cm.do
1035 ms
cm.gif
1857 ms
mapping.do
933 ms
cm.mediav.com
1316 ms
chain
904 ms
416a29f1b673cea3ba10f08289538371.jpg
19628 ms
8c3b32f21cf3684fc144113acee016f8.jpg
20322 ms
t.gif
3987 ms
mediavcm
1020 ms
6beb25aebcc7631fdeea7774a040d76e.jpg
20441 ms
youkucm
1059 ms
dae6df5f40ac26a8cb565c00a3971417.jpg
19839 ms
cm.gif
992 ms
t.gif
834 ms
chain
539 ms
chain
891 ms
chain
4820 ms
495449f4326466391cdcd20b3b524466.jpg
19999 ms
b12554288ac03039591061524270035b.jpg
19999 ms
1d5f187e174c1dd028234f67e1c66c42.jpg
19999 ms
9d586458ed2c4ef5ef127bcf6520fb6a.jpg
19999 ms
ce1f2a28c9bc56926b85e55c698fa93e.jpg
19999 ms
e43cf40c992ca66805dac2c505de4add.jpg
19998 ms
26ae76f41640d272e9bcaa77b1c761ec.jpg
19998 ms
bdbbe24c968a7a995543a1178d5cc0c3.jpg
19999 ms
a67ca87d6969c5c270496c231aeaa4c8.jpg
19998 ms
931bb25aabeb0181638aed0b6182cd62.jpg
19997 ms
27da3f2e6e23b13555fb9c1c922456f0.jpg
19997 ms
5c57e7e8c816a804ab44d3e9771477db.jpg
19997 ms
ff1f6ff082fbda2f267641fcf74c77e3.jpg
19996 ms
5d4af06906c8e1cc8a0827b2714c6657.jpg
19996 ms
8f8c682f3f15577aa979fe879b5108df.jpg
19996 ms
dc65358c5018e9511dead52ec7374eec.jpg
19994 ms
fandongxi.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fandongxi.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fandongxi.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
fandongxi.com
Open Graph description is not detected on the main page of Fandongxi. 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: