93 sec in total
13.1 sec
77 sec
2.9 sec
Welcome to lctz.tmall.com homepage info - get ready to check Lctz Tmall best content for China right away, or after learning these important things about lctz.tmall.com
淘宝, 店铺, 旺铺, 乐臣童装专营店
Visit lctz.tmall.comWe analyzed Lctz.tmall.com page load time and found that the first response time was 13.1 sec and then it took 79.9 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.
lctz.tmall.com performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value11.4 s
0/100
25%
Value8.8 s
16/100
10%
Value430 ms
65/100
30%
Value0.002
100/100
15%
Value11.5 s
18/100
10%
13095 ms
1651 ms
1060 ms
6850 ms
14323 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Lctz.tmall.com, 33% (36 requests) were made to G.alicdn.com and 20% (22 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Pcookie.tmall.com.
Page size can be reduced by 420.6 kB (11%)
3.9 MB
3.4 MB
In fact, the total size of Lctz.tmall.com main page is 3.9 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. 65% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 151.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 38.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 151.2 kB or 79% of the original size.
Potential reduce by 32.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. Lctz 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 81.5 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. Lctz.tmall.com needs all CSS files to be minified and compressed as it can save up to 81.5 kB or 77% of the original size.
Number of requests can be reduced by 48 (54%)
89
41
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lctz 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 10 to 1 for CSS and as a result speed up the page load time.
lctz.tmall.com
13095 ms
lctz.tmall.com
1651 ms
lctz.world.tmall.com
1060 ms
lctz.world.tmall.com
6850 ms
jump
14323 ms
add
1604 ms
lctz.world.tmall.com
1941 ms
lctz.world.tmall.com
517 ms
lctz.world.tmall.com
490 ms
lctz.world.tmall.com
8182 ms
global-min.css
361 ms
seed-min.js
370 ms
global-min.js
444 ms
g.alicdn.com
414 ms
g.alicdn.com
414 ms
copyright-min.css
415 ms
565 ms
g.alicdn.com
491 ms
TB1cuNhMpXXXXasXFXXn00bFXXX.css
644 ms
index.js
495 ms
init-async-min.js
495 ms
95 ms
92 ms
TB2tNdViVXXXXa3XXXXXXXXXXXX_!!818123750.jpg
4119 ms
aplus_v2.js
156 ms
159 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
4100 ms
getipinfo
4108 ms
counter6
7439 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
3944 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
3980 ms
font_1451273740_187741.woff
4106 ms
aplus_v2.js
62 ms
3789 ms
xwj_heat.js
3811 ms
agp_heat.min.js
3797 ms
wp-beacon.js
3983 ms
2.gif
5527 ms
ahot.1.9
6032 ms
80 ms
140 ms
s.gif
200 ms
shopinfo-min.css
56 ms
72 ms
162 ms
processUserCookie.htm
10857 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
133 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
86 ms
blank
11 ms
TB1DVGpMXXXXXX8apXXSutbFXXX.jpg
70 ms
TB22OxslpXXXXckXXXXXXXXXXXX_!!818123750.jpg
141 ms
TB2ekdmlpXXXXXbXpXXXXXXXXXX_!!818123750.jpg
185 ms
TB2HqhElpXXXXapXXXXXXXXXXXX_!!818123750.jpg
190 ms
TB2Vc.0mpXXXXboXpXXXXXXXXXX_!!818123750.jpg
296 ms
TB2XyVbmFXXXXXrXpXXXXXXXXXX_!!818123750.jpg
275 ms
TB2I5BolpXXXXc2XXXXXXXXXXXX_!!818123750.jpg
188 ms
TB2ZLlHlpXXXXX0XXXXXXXXXXXX_!!818123750.jpg
186 ms
TB26zdhlpXXXXXHXpXXXXXXXXXX_!!818123750.jpg
212 ms
T1vEi4XnhyXXXm0Pva-454-340.png
60 ms
blank
51 ms
67 ms
67 ms
65 ms
T1GjdOXA8XXXbHTkoN-122-235.png
155 ms
T156jcXXhfXXcMeXnl-22-160.gif
63 ms
80 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
29 ms
TB2vYW7lVXXXXcxXXXXXXXXXXXX_!!818123750.png
319 ms
TB2Wye4lVXXXXc4XXXXXXXXXXXX_!!818123750.png
302 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
104 ms
font_1433225452_0164654.woff
46 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
57 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
140 ms
posttry.js
35 ms
webww.js
85 ms
index.js
84 ms
61 ms
TB1YL_WGFXXXXapXFXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E447960bb1072e770d250202bc451975c;lang%5Egbk;t%5E1460127870000
965 ms
TB2lwjHlFXXXXb3XXXXXXXXXXXX_!!818123750.jpg
372 ms
vdata.htm
565 ms
TB2UAUxiVXXXXcPXXXXXXXXXXXX_!!818123750.jpg
374 ms
T2vlq1XplXXXXXXXXX-818123750.png
74 ms
T2qqi0XDRXXXXXXXXX-818123750.png
76 ms
TB23DE0lpXXXXXPXXXXXXXXXXXX_!!818123750.jpg
336 ms
localhost.wwbizsrv.alibaba.com
37 ms
muliuserstatus.aw
6327 ms
index.js
62 ms
index.js
32 ms
localhost.wwbizsrv.alibaba.com
2 ms
ww.69.2
424 ms
app.gif
20113 ms
adapter.js
31 ms
ww.69.2
83 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
29 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
216 ms
T1FXHXXahjXXXAK3zo-77-18.gif
29 ms
jump
525 ms
add
398 ms
www.tmall.com
589 ms
TB2DvRsiVXXXXa.XpXXXXXXXXXX_!!818123750.jpg
143 ms
translateelement.css
39 ms
main.js
57 ms
loading.gif
199 ms
favicon.ico
4599 ms
ahot.1.1
284 ms
element_main.js
166 ms
translate_24dp.png
154 ms
l
100 ms
cleardot.gif
145 ms
lctz.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
lctz.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
lctz.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 Lctz.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 Lctz.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.
lctz.tmall.com
Open Graph description is not detected on the main page of Lctz 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: