46.4 sec in total
4.9 sec
39.8 sec
1.7 sec
Visit montrail.tmall.com now to see the best up-to-date Montrail Tmall content for China and also check out these interesting facts you probably never knew about montrail.tmall.com
淘宝, 店铺, 旺铺, montrail官方旗舰店
Visit montrail.tmall.comWe analyzed Montrail.tmall.com page load time and found that the first response time was 4.9 sec and then it took 41.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.
montrail.tmall.com performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value11.1 s
0/100
25%
Value8.6 s
17/100
10%
Value340 ms
74/100
30%
Value0.002
100/100
15%
Value11.3 s
19/100
10%
4886 ms
1595 ms
905 ms
2666 ms
5830 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Montrail.tmall.com, 34% (36 requests) were made to G.alicdn.com and 21% (22 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (10 sec) relates to the external source Pcookie.tmall.com.
Page size can be reduced by 354.1 kB (17%)
2.1 MB
1.8 MB
In fact, the total size of Montrail.tmall.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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 128.7 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 28.9 kB, which is 17% 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 128.7 kB or 77% of the original size.
Potential reduce by 14.9 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. Montrail Tmall images are well optimized though.
Potential reduce by 148.8 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 148.8 kB or 35% of the original size.
Potential reduce by 61.6 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. Montrail.tmall.com needs all CSS files to be minified and compressed as it can save up to 61.6 kB or 71% of the original size.
Number of requests can be reduced by 51 (58%)
88
37
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Montrail 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 11 to 1 for CSS and as a result speed up the page load time.
montrail.tmall.com
4886 ms
montrail.tmall.com
1595 ms
montrail.world.tmall.com
905 ms
montrail.world.tmall.com
2666 ms
jump
5830 ms
add
2022 ms
montrail.world.tmall.com
412 ms
montrail.world.tmall.com
412 ms
montrail.world.tmall.com
412 ms
montrail.world.tmall.com
5853 ms
global-min.css
233 ms
seed-min.js
292 ms
global-min.js
320 ms
g.alicdn.com
274 ms
g.alicdn.com
291 ms
brandbar-min.css
289 ms
copyright-min.css
288 ms
471 ms
g.alicdn.com
467 ms
TB1BD7XJpXXXXb6XXXXn00bFXXX.css
562 ms
index.js
458 ms
init-async-min.js
411 ms
137 ms
109 ms
TB2IlpCcXXXXXXGXXXXXXXXXXXX_!!2396647172.jpg
4954 ms
TB2cGI.lFXXXXbYXpXXXXXXXXXX_!!2396647172.png
347 ms
TB2RXxtcXXXXXawXpXXXXXXXXXX_!!2396647172.png
455 ms
TB2CCxycXXXXXbyXXXXXXXXXXXX_!!2396647172.png
399 ms
TB2CkBwcXXXXXcoXXXXXXXXXXXX_!!2396647172.png
458 ms
TB2Yi8.cXXXXXXMXpXXXXXXXXXX_!!2396647172.jpg
356 ms
aplus_v2.js
149 ms
4584 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
4789 ms
getipinfo
5055 ms
counter6
6096 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
4974 ms
aplus_v2.js
193 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
4819 ms
shopinfo-min.css
54 ms
56 ms
36 ms
font_1451273740_187741.woff
4657 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
4777 ms
4399 ms
blank
4313 ms
TB1ikuLHXXXXXa5XVXXSutbFXXX.jpg
4510 ms
TB2V_pAcXXXXXaDXXXXXXXXXXXX_!!2396647172.png
4494 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
4717 ms
T1vEi4XnhyXXXm0Pva-454-340.png
4715 ms
agp_heat.min.js
4463 ms
wp-beacon.js
4870 ms
2.gif
4163 ms
ahot.1.9
4705 ms
blank
53 ms
208 ms
T1GjdOXA8XXXbHTkoN-122-235.png
191 ms
T156jcXXhfXXcMeXnl-22-160.gif
473 ms
posttry.js
263 ms
s.gif
575 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
262 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
423 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
492 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
188 ms
147 ms
139 ms
font_1433225452_0164654.woff
78 ms
webww.js
68 ms
index.js
68 ms
62 ms
processUserCookie.htm
4129 ms
59 ms
51 ms
49 ms
localhost.wwbizsrv.alibaba.com
6 ms
muliuserstatus.aw
9160 ms
TB1N82FGVXXXXX1aFXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5Ee0aada146b90cfe5bee98c3ed963051b;lang%5Egbk;t%5E1460125840000
622 ms
TB2oD_0mFXXXXXVXXXXXXXXXXXX_!!2396647172.jpg
1619 ms
vdata.htm
417 ms
TB24VLCjXXXXXbvXXXXXXXXXXXX_!!2396647172.jpg
46 ms
TB2uq6xjXXXXXckXXXXXXXXXXXX_!!2396647172.jpg
57 ms
TB2Zh6fjXXXXXbJXpXXXXXXXXXX_!!2396647172.jpg
53 ms
TB2M0nrjXXXXXcZXXXXXXXXXXXX_!!2396647172.jpg
54 ms
TB2wzLcjXXXXXb8XpXXXXXXXXXX_!!2396647172.jpg
49 ms
TB2xL5MmXXXXXXSXpXXXXXXXXXX_!!2396647172.jpg
176 ms
TB2akiOmXXXXXXiXpXXXXXXXXXX_!!2396647172.jpg
214 ms
TB2Uk95mXXXXXa5XXXXXXXXXXXX_!!2396647172.jpg
188 ms
TB2_7i9mXXXXXaCXXXXXXXXXXXX_!!2396647172.jpg
192 ms
index.js
39 ms
index.js
41 ms
localhost.wwbizsrv.alibaba.com
2 ms
ww.69.2
442 ms
adapter.js
64 ms
ww.69.2
98 ms
app.gif
10012 ms
jump
3018 ms
add
491 ms
www.tmall.com
1828 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
38 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
441 ms
translateelement.css
41 ms
main.js
33 ms
loading.gif
368 ms
favicon.ico
672 ms
element_main.js
132 ms
translate_24dp.png
210 ms
l
169 ms
cleardot.gif
349 ms
montrail.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
montrail.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
montrail.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
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Montrail.tmall.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 Montrail.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.
montrail.tmall.com
Open Graph description is not detected on the main page of Montrail 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: