57.8 sec in total
1.2 sec
54.6 sec
1.9 sec
Visit enaiter.tmall.com now to see the best up-to-date Enaiter Tmall content for China and also check out these interesting facts you probably never knew about enaiter.tmall.com
淘宝, 店铺, 旺铺, 伊莱特旗舰店
Visit enaiter.tmall.comWe analyzed Enaiter.tmall.com page load time and found that the first response time was 1.2 sec and then it took 56.6 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.
enaiter.tmall.com performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value11.6 s
0/100
25%
Value9.2 s
13/100
10%
Value220 ms
88/100
30%
Value0.002
100/100
15%
Value11.8 s
17/100
10%
1221 ms
5179 ms
2197 ms
12460 ms
5930 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Enaiter.tmall.com, 34% (35 requests) were made to G.alicdn.com and 23% (24 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (12.5 sec) relates to the external source Enaiter.world.tmall.com.
Page size can be reduced by 387.1 kB (12%)
3.1 MB
2.7 MB
In fact, the total size of Enaiter.tmall.com main page is 3.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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 130.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 20.3 kB, which is 12% 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 130.8 kB or 76% of the original size.
Potential reduce by 24.1 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. Enaiter Tmall images are well optimized though.
Potential reduce by 154.7 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 154.7 kB or 45% of the original size.
Potential reduce by 77.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. Enaiter.tmall.com needs all CSS files to be minified and compressed as it can save up to 77.5 kB or 79% of the original size.
Number of requests can be reduced by 48 (56%)
86
38
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enaiter 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 28 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
enaiter.tmall.com
1221 ms
enaiter.tmall.com
5179 ms
enaiter.world.tmall.com
2197 ms
enaiter.world.tmall.com
12460 ms
jump
5930 ms
add
8826 ms
enaiter.world.tmall.com
530 ms
enaiter.world.tmall.com
487 ms
enaiter.world.tmall.com
501 ms
enaiter.world.tmall.com
5710 ms
global-min.css
497 ms
seed-min.js
572 ms
global-min.js
648 ms
g.alicdn.com
478 ms
g.alicdn.com
478 ms
brandbar-min.css
480 ms
copyright-min.css
502 ms
643 ms
g.alicdn.com
509 ms
index.js
523 ms
init-async-min.js
539 ms
TB2_XSNmFXXXXc_XpXXXXXXXXXX_!!1119339412.jpg
4353 ms
TB2QE5WmFXXXXbJXpXXXXXXXXXX_!!1119339412.gif
4538 ms
TB2DEjjmFXXXXceXXXXXXXXXXXX_!!1119339412.gif
4535 ms
TB2.wSTmFXXXXbSXpXXXXXXXXXX_!!1119339412.gif
4566 ms
TB2EknEmFXXXXXzXXXXXXXXXXXX_!!1119339412.gif
4537 ms
403 ms
166 ms
167 ms
aplus_v2.js
153 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
4424 ms
getipinfo
4413 ms
counter6
5822 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
4618 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
4314 ms
shopinfo-min.css
151 ms
aplus_v2.js
289 ms
3929 ms
3884 ms
3919 ms
s.gif
4472 ms
font_1451273740_187741.woff
4571 ms
xwj_heat.js
3699 ms
agp_heat.min.js
3698 ms
wp-beacon.js
4290 ms
2.gif
2864 ms
ahot.1.9
3408 ms
posttry.js
191 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
272 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
411 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
560 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
590 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
494 ms
blank
9 ms
TB1STdpMpXXXXbiXVXXSutbFXXX.jpg
833 ms
T1vEi4XnhyXXXm0Pva-454-340.png
478 ms
blank
93 ms
153 ms
T1GjdOXA8XXXbHTkoN-122-235.png
321 ms
T156jcXXhfXXcMeXnl-22-160.gif
386 ms
278 ms
277 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
230 ms
processUserCookie.htm
11388 ms
font_1433225452_0164654.woff
383 ms
webww.js
117 ms
index.js
114 ms
109 ms
110 ms
117 ms
109 ms
localhost.wwbizsrv.alibaba.com
76 ms
muliuserstatus.aw
2649 ms
TB1hdDoLFXXXXXEXFXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E2cc7765c62c9829893197f7308deaae8;lang%5Egbk;t%5E1460136668000
775 ms
vdata.htm
578 ms
TB2EaKBaXXXXXXxXXXXXXXXXXXX-126112166.png
126 ms
TB2s_WAaXXXXXXQXXXXXXXXXXXX-126112166.png
139 ms
TB2QysxbpXXXXXVXXXXXXXXXXXX_!!822878650.gif
127 ms
TB2zrO3eVXXXXXvXXXXXXXXXXXX_!!1119339412.jpg
127 ms
TB2ueiAeVXXXXbMXpXXXXXXXXXX_!!1119339412.jpg
801 ms
TB2pSZUgVXXXXcJXpXXXXXXXXXX_!!1119339412.jpg
840 ms
TB28UDieVXXXXa_XpXXXXXXXXXX_!!1119339412.jpg
389 ms
TB2hS5SeVXXXXc9XXXXXXXXXXXX_!!1119339412.jpg
599 ms
TB2tDEreFXXXXczXXXXXXXXXXXX_!!1119339412.jpg
358 ms
TB2mmfGmXXXXXX9XXXXXXXXXXXX_!!1119339412.jpg
2971 ms
TB2mf_CmXXXXXX.XXXXXXXXXXXX_!!1119339412.jpg
2795 ms
TB2vMSBmXXXXXXVXpXXXXXXXXXX_!!1119339412.jpg
1681 ms
TB2QhL4lVXXXXXAXpXXXXXXXXXX_!!1119339412.jpg
943 ms
TB2v7DJlVXXXXX_XpXXXXXXXXXX_!!1119339412.jpg
2872 ms
TB2S8LOlVXXXXbGXpXXXXXXXXXX_!!1119339412.jpg
2439 ms
index.js
63 ms
index.js
43 ms
localhost.wwbizsrv.alibaba.com
3 ms
ww.69.2
494 ms
app.gif
5529 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
59 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
399 ms
adapter.js
16 ms
ww.69.2
93 ms
jstracker.3
97 ms
T1FXHXXahjXXXAK3zo-77-18.gif
55 ms
T1FXHXXahjXXXAK3zo-77-18.gif
50 ms
T1FXHXXahjXXXAK3zo-77-18.gif
67 ms
enaiter.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
enaiter.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
General
Impact
Issue
Browser errors were logged to the console
enaiter.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 Enaiter.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 Enaiter.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.
enaiter.tmall.com
Open Graph description is not detected on the main page of Enaiter 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: