71 sec in total
1.3 sec
65.6 sec
4.1 sec
Visit langsha.tmall.com now to see the best up-to-date Langsha Tmall content for China and also check out these interesting facts you probably never knew about langsha.tmall.com
淘宝, 店铺, 旺铺, 浪莎官方旗舰店
Visit langsha.tmall.comWe analyzed Langsha.tmall.com page load time and found that the first response time was 1.3 sec and then it took 69.7 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.
langsha.tmall.com performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value11.8 s
0/100
25%
Value9.4 s
12/100
10%
Value380 ms
70/100
30%
Value0.002
100/100
15%
Value12.0 s
16/100
10%
1316 ms
2972 ms
3920 ms
17130 ms
2689 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Langsha.tmall.com, 43% (54 requests) were made to G.alicdn.com and 15% (19 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Pcookie.tmall.com.
Page size can be reduced by 1.0 MB (28%)
3.8 MB
2.7 MB
In fact, the total size of Langsha.tmall.com main page is 3.8 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 147.2 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 62.6 kB, which is 37% 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 147.2 kB or 87% of the original size.
Potential reduce by 10.3 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. Langsha Tmall images are well optimized though.
Potential reduce by 400.1 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 400.1 kB or 43% of the original size.
Potential reduce by 485.4 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. Langsha.tmall.com needs all CSS files to be minified and compressed as it can save up to 485.4 kB or 89% of the original size.
Number of requests can be reduced by 79 (75%)
106
27
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Langsha 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 53 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
langsha.tmall.com
1316 ms
langsha.tmall.com
2972 ms
langsha.world.tmall.com
3920 ms
langsha.world.tmall.com
17130 ms
jump
2689 ms
add
7675 ms
langsha.world.tmall.com
361 ms
langsha.world.tmall.com
507 ms
langsha.world.tmall.com
401 ms
langsha.world.tmall.com
4728 ms
global-min.css
488 ms
seed-min.js
651 ms
global-min.js
573 ms
g.alicdn.com
553 ms
g.alicdn.com
607 ms
brandbar-min.css
753 ms
copyright-min.css
749 ms
785 ms
TB1UGObIFXXXXXuaXXXn00bFXXX.css
1085 ms
default_ed.css
756 ms
default_ed.css
828 ms
TB1rBBvMpXXXXXoXXXXn00bFXXX.css
746 ms
index.js
771 ms
init-async-min.js
776 ms
135 ms
100 ms
aplus_v2.js
55 ms
90 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
2968 ms
getipinfo
3006 ms
counter6
4858 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
3031 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
2951 ms
aplus_v2.js
101 ms
font_1451273740_187741.woff
3203 ms
2815 ms
xwj_heat.js
2749 ms
agp_heat.min.js
2749 ms
wp-beacon.js
2907 ms
2.gif
3788 ms
ahot.1.9
5625 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
42 ms
seed-min.js
208 ms
80 ms
module_ed.js
959 ms
module_ed.js
1680 ms
setup-shop-min.js
59 ms
posttry.js
60 ms
250 ms
192 ms
s.gif
195 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
72 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
192 ms
shopinfo-min.css
107 ms
115 ms
285 ms
processUserCookie.htm
10255 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
110 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
351 ms
blank
39 ms
TB1zRrfMXXXXXbFXXXXSutbFXXX.jpg
794 ms
t.gif
107 ms
u.gif
176 ms
T156jcXXhfXXcMeXnl-22-160.gif
105 ms
TB2sOZCkXXXXXawXXXXXXXXXXXX_!!272715291.jpg
284 ms
T2U2zZXb8XXXXXXXXX_!!368136.png
216 ms
T2ARLYXl0aXXXXXXXX_!!368136.png
216 ms
80 ms
159 ms
78 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
235 ms
127 ms
font_1433225452_0164654.woff
125 ms
base-min.js
95 ms
base-min.js
146 ms
base-min.js
93 ms
touch-min.js
92 ms
focusin-min.js
93 ms
custom-min.js
90 ms
ajax-min.js
138 ms
anim-min.js
152 ms
base-min.js
170 ms
node-min.js
152 ms
json-min.js
169 ms
cookie-min.js
179 ms
sizzle-min.js
216 ms
webww.js
270 ms
index.js
271 ms
210 ms
TB1bTDiLFXXXXczXFXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E9d8a62287469b7d17208edf074a5722c;lang%5Egbk;t%5E1460132709000
712 ms
TB2XOTJlVXXXXc2XXXXXXXXXXXX_!!272715291.jpg
284 ms
vdata.htm
596 ms
TB2CiQqkXXXXXb2XXXXXXXXXXXX_!!272715291.jpg
263 ms
TB2EGfKkVXXXXbBXXXXXXXXXXXX_!!272715291.jpg
1433 ms
TB2L8AmkFXXXXXvXXXXXXXXXXXX_!!272715291.jpg
1578 ms
TB2PVHjkVXXXXbrXpXXXXXXXXXX_!!272715291.jpg
1492 ms
localhost.wwbizsrv.alibaba.com
19 ms
muliuserstatus.aw
3428 ms
es53-taming-frame-min.js
140 ms
es53-guest-frame-min.js
159 ms
ajax
1369 ms
ajax
1464 ms
index.js
108 ms
index.js
65 ms
localhost.wwbizsrv.alibaba.com
2 ms
ww.69.2
538 ms
app.gif
19513 ms
adapter.js
59 ms
ww.69.2
109 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
161 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
404 ms
T1FXHXXahjXXXAK3zo-77-18.gif
13 ms
T1FXHXXahjXXXAK3zo-77-18.gif
29 ms
jump
517 ms
add
1982 ms
www.tmall.com
2523 ms
translateelement.css
65 ms
main.js
92 ms
loading.gif
654 ms
favicon.ico
556 ms
ahot.1.2
489 ms
element_main.js
202 ms
translate_24dp.png
253 ms
l
197 ms
cleardot.gif
252 ms
langsha.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
langsha.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
langsha.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 Langsha.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 Langsha.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.
langsha.tmall.com
Open Graph description is not detected on the main page of Langsha 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: