51.2 sec in total
8.1 sec
41.7 sec
1.4 sec
Click here to check amazing Moussy Tmall content for China. Otherwise, check out these important facts you probably never knew about moussy.tmall.com
淘宝, 店铺, 旺铺, moussy旗舰店
Visit moussy.tmall.comWe analyzed Moussy.tmall.com page load time and found that the first response time was 8.1 sec and then it took 43.1 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.
moussy.tmall.com performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value11.8 s
0/100
25%
Value9.2 s
13/100
10%
Value480 ms
60/100
30%
Value0.002
100/100
15%
Value12.1 s
16/100
10%
8142 ms
4092 ms
1673 ms
1924 ms
2612 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Moussy.tmall.com, 33% (36 requests) were made to G.alicdn.com and 22% (24 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (8.1 sec) belongs to the original domain Moussy.tmall.com.
Page size can be reduced by 946.9 kB (35%)
2.7 MB
1.8 MB
In fact, the total size of Moussy.tmall.com main page is 2.7 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 103.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. This page needs HTML code to be minified as it can gain 32.0 kB, which is 26% 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 103.6 kB or 84% of the original size.
Potential reduce by 10.0 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. Moussy Tmall images are well optimized though.
Potential reduce by 374.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 374.6 kB or 47% of the original size.
Potential reduce by 458.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. Moussy.tmall.com needs all CSS files to be minified and compressed as it can save up to 458.7 kB or 89% of the original size.
Number of requests can be reduced by 54 (57%)
94
40
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moussy 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 31 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
moussy.tmall.com
8142 ms
moussy.world.tmall.com
4092 ms
moussy.world.tmall.com
1673 ms
jump
1924 ms
add
2612 ms
moussy.world.tmall.com
430 ms
moussy.world.tmall.com
400 ms
moussy.world.tmall.com
484 ms
moussy.world.tmall.com
6794 ms
global-min.css
584 ms
seed-min.js
694 ms
global-min.js
959 ms
g.alicdn.com
784 ms
g.alicdn.com
797 ms
brandbar-min.css
845 ms
copyright-min.css
863 ms
1017 ms
TB194O6HFXXXXXtXXXXn00bFXXX.css
1349 ms
TB1kz3EHFXXXXbsaXXXn00bFXXX.css
517 ms
index.js
906 ms
init-async-min.js
1014 ms
137 ms
63 ms
TB25ZP7kVXXXXb8XpXXXXXXXXXX_!!2438930156.jpg
81 ms
aplus_v2.js
82 ms
127 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
4890 ms
getipinfo
5341 ms
counter6
6446 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
5654 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
5120 ms
shopinfo-min.css
56 ms
aplus_v2.js
155 ms
85 ms
143 ms
font_1451273740_187741.woff
5664 ms
4618 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
4989 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
5505 ms
TB1GXh.LVXXXXaoXXXXSutbFXXX
4678 ms
blank
4497 ms
TB2pRVokFXXXXc7XXXXXXXXXXXX_!!2438930156.png
4618 ms
T1vEi4XnhyXXXm0Pva-454-340.png
5098 ms
xwj_heat.js
4903 ms
agp_heat.min.js
4902 ms
wp-beacon.js
5493 ms
2.gif
3774 ms
ahot.1.9
3966 ms
423 ms
TB2aGz9bpXXXXXnXpXXXXXXXXXX-185879812.gif
153 ms
arrow.gif
435 ms
T156jcXXhfXXcMeXnl-22-160.gif
589 ms
360 ms
353 ms
posttry.js
329 ms
TB2ysH7bpXXXXakXpXXXXXXXXXX-185879812.gif
329 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
327 ms
s.gif
903 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
480 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
518 ms
sld_numbtn.gif
443 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
386 ms
font_1433225452_0164654.woff
637 ms
webww.js
179 ms
index.js
202 ms
169 ms
164 ms
162 ms
160 ms
adapter.js
343 ms
muliuserstatus.aw
5191 ms
processUserCookie.htm
3080 ms
T1kyVWFe8dXXcjfCvX-140-75.png
386 ms
T1p8v6XfJjXXXTOpDa-17-16.png
433 ms
TB1CO4KMXXXXXXeXpXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5Ef8a7db15f0c22a1b3765c1b35c2054cf;lang%5Egbk;t%5E1460121522000
529 ms
TB2ZkUUlVXXXXb9XpXXXXXXXXXX_!!2438930156.jpg
229 ms
vdata.htm
420 ms
widgetAsync.htm
849 ms
TB25cDFmXXXXXaGXpXXXXXXXXXX_!!2438930156.jpg
435 ms
TB2BlzrlVXXXXb4XpXXXXXXXXXX_!!2438930156.jpg
194 ms
TB2cICuXFXXXXbJXpXXXXXXXXXX_!!2438930156.jpg
1097 ms
TB2T2frcFXXXXXuXpXXXXXXXXXX_!!2438930156.jpg
188 ms
TB23ljCcFXXXXciXXXXXXXXXXXX_!!2438930156.jpg
192 ms
TB2yGLHcFXXXXXGXXXXXXXXXXXX_!!2438930156.jpg
195 ms
TB22OLucFXXXXXaXpXXXXXXXXXX_!!2438930156.jpg
200 ms
TB2gs_ucFXXXXXbXpXXXXXXXXXX_!!2438930156.jpg
197 ms
TB2kEjxcFXXXXcWXXXXXXXXXXXX_!!2438930156.jpg
236 ms
TB2dxbEcFXXXXbsXXXXXXXXXXXX_!!2438930156.jpg
245 ms
TB2dB2OgFXXXXXRXXXXXXXXXXXX_!!2438930156.jpg
260 ms
index.js
51 ms
index.js
58 ms
TB2i1F3aXXXXXcnXpXXXXXXXXXX_!!2438930156.jpg
245 ms
jump
418 ms
app.gif
1887 ms
add
381 ms
www.tmall.com
1709 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
63 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
402 ms
T1FXHXXahjXXXAK3zo-77-18.gif
60 ms
ali-page-updater
29 ms
T1FXHXXahjXXXAK3zo-77-18.gif
37 ms
translateelement.css
125 ms
main.js
146 ms
loading.gif
403 ms
favicon.ico
386 ms
ahot.1.2
698 ms
element_main.js
262 ms
translate_24dp.png
197 ms
l
141 ms
cleardot.gif
189 ms
moussy.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
moussy.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
moussy.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 Moussy.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 Moussy.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.
moussy.tmall.com
Open Graph description is not detected on the main page of Moussy 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: