78.8 sec in total
2.1 sec
71.7 sec
4.9 sec
Welcome to xsyd.tmall.com homepage info - get ready to check Xsyd Tmall best content for China right away, or after learning these important things about xsyd.tmall.com
淘宝, 店铺, 旺铺, 徐氏运动专营店
Visit xsyd.tmall.comWe analyzed Xsyd.tmall.com page load time and found that the first response time was 2.1 sec and then it took 76.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
xsyd.tmall.com performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value11.2 s
0/100
25%
Value8.7 s
16/100
10%
Value240 ms
85/100
30%
Value0.002
100/100
15%
Value11.3 s
19/100
10%
2123 ms
12280 ms
5046 ms
11511 ms
2273 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Xsyd.tmall.com, 33% (35 requests) were made to G.alicdn.com and 24% (25 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (16.9 sec) relates to the external source Pcookie.tmall.com.
Page size can be reduced by 660.9 kB (15%)
4.5 MB
3.8 MB
In fact, the total size of Xsyd.tmall.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 3.6 MB which makes up the majority of the site volume.
Potential reduce by 159.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. This page needs HTML code to be minified as it can gain 41.0 kB, which is 20% 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 159.8 kB or 79% of the original size.
Potential reduce by 173.8 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. Xsyd Tmall images are well optimized though.
Potential reduce by 155.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 155.5 kB or 36% of the original size.
Potential reduce by 171.7 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. Xsyd.tmall.com needs all CSS files to be minified and compressed as it can save up to 171.7 kB or 83% of the original size.
Number of requests can be reduced by 47 (53%)
88
41
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xsyd Tmall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
xsyd.tmall.com
2123 ms
xsyd.tmall.com
12280 ms
xsyd.world.tmall.com
5046 ms
xsyd.world.tmall.com
11511 ms
jump
2273 ms
add
4517 ms
xsyd.world.tmall.com
489 ms
xsyd.world.tmall.com
474 ms
xsyd.world.tmall.com
504 ms
xsyd.world.tmall.com
10831 ms
global-min.css
622 ms
seed-min.js
678 ms
global-min.js
1217 ms
g.alicdn.com
553 ms
g.alicdn.com
554 ms
copyright-min.css
566 ms
760 ms
TB1oe3uHFXXXXc2XXXXn00bFXXX.css
1415 ms
TB1Xsx4MpXXXXceXXXXn00bFXXX.css
824 ms
index.js
624 ms
init-async-min.js
628 ms
7927 ms
320 ms
aplus_v2.js
173 ms
192 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
7779 ms
getipinfo
206 ms
counter6
14452 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
331 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
8032 ms
shopinfo-min.css
116 ms
font_1451273740_187741.woff
8070 ms
aplus_v2.js
214 ms
91 ms
7451 ms
7557 ms
processUserCookie.htm
11419 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
7313 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
7882 ms
xwj_heat.js
7837 ms
agp_heat.min.js
7838 ms
wp-beacon.js
8652 ms
2.gif
3759 ms
ahot.1.9
4273 ms
blank
123 ms
TB1ysb3HpXXXXXZXXXXSutbFXXX.jpg
553 ms
posttry.js
525 ms
TB27gbOcFXXXXaTXpXXXXXXXXXX_!!320868932.jpg
539 ms
arrow.gif
543 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
543 ms
s.gif
1353 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
535 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
978 ms
546 ms
TB2F4O0gFXXXXbAXXXXXXXXXXXX_!!320868932.jpg
2067 ms
TB2Gd8bmFXXXXXaXpXXXXXXXXXX_!!320868932.jpg
992 ms
TB2R2JhmpXXXXahXXXXXXXXXXXX_!!320868932.jpg
1726 ms
TB2RseAmXXXXXX7XpXXXXXXXXXX_!!320868932.jpg
1551 ms
TB2gXTGipXXXXcAXXXXXXXXXXXX_!!320868932.jpg
1552 ms
TB2oximjFXXXXXMXXXXXXXXXXXX_!!320868932.jpg
1551 ms
TB2NePjlFXXXXcsXXXXXXXXXXXX_!!320868932.jpg
1551 ms
TB28Qy7lFXXXXX_XpXXXXXXXXXX_!!320868932.jpg
1725 ms
TB2ydDhlFXXXXazXpXXXXXXXXXX_!!320868932.jpg
1777 ms
TB2wjrQlFXXXXakXXXXXXXXXXXX_!!320868932.jpg
1817 ms
TB23g6vlFXXXXakXXXXXXXXXXXX_!!320868932.jpg
1776 ms
570 ms
558 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
1707 ms
font_1433225452_0164654.woff
258 ms
webww.js
427 ms
index.js
429 ms
355 ms
90 ms
144 ms
120 ms
localhost.wwbizsrv.alibaba.com
101 ms
muliuserstatus.aw
3050 ms
TB1ubLCLFXXXXXjXXXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5Ed78d4e79db85a73fc6647c58646f4fb6;lang%5Egbk;t%5E1460135985000
639 ms
vdata.htm
553 ms
TB2ZSPwgpXXXXbhXpXXXXXXXXXX_!!320868932.jpg
145 ms
TB2LsvEgpXXXXauXpXXXXXXXXXX_!!320868932.jpg
178 ms
TB2LeYwgpXXXXbAXpXXXXXXXXXX_!!320868932.jpg
180 ms
TB2z833kpXXXXaUXpXXXXXXXXXX_!!320868932.jpg
179 ms
TB2GZmkjVXXXXcxXpXXXXXXXXXX_!!320868932.jpg
181 ms
TB2Hg4.mpXXXXajXXXXXXXXXXXX_!!320868932.jpg
484 ms
TB2f3LxlpXXXXc5XXXXXXXXXXXX_!!320868932.jpg
348 ms
index.js
132 ms
index.js
72 ms
localhost.wwbizsrv.alibaba.com
2 ms
ww.69.2
639 ms
app.gif
16881 ms
jump
994 ms
adapter.js
87 ms
ww.69.2
127 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
103 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
323 ms
add
543 ms
T1FXHXXahjXXXAK3zo-77-18.gif
328 ms
T1FXHXXahjXXXAK3zo-77-18.gif
71 ms
www.tmall.com
2218 ms
translateelement.css
76 ms
main.js
86 ms
loading.gif
540 ms
favicon.ico
450 ms
ahot.1.1
384 ms
element_main.js
854 ms
xsyd.tmall.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
xsyd.tmall.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
xsyd.tmall.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xsyd.tmall.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Xsyd.tmall.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.
xsyd.tmall.com
Open Graph description is not detected on the main page of Xsyd Tmall. 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: