77.4 sec in total
1.2 sec
72.7 sec
3.6 sec
Visit onon.tmall.com now to see the best up-to-date Onon Tmall content for China and also check out these interesting facts you probably never knew about onon.tmall.com
淘宝, 店铺, 旺铺, onon旗舰店
Visit onon.tmall.comWe analyzed Onon.tmall.com page load time and found that the first response time was 1.2 sec and then it took 76.3 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. 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.
onon.tmall.com performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value10.7 s
0/100
25%
Value8.6 s
17/100
10%
Value160 ms
93/100
30%
Value0.002
100/100
15%
Value11.5 s
18/100
10%
1152 ms
2040 ms
914 ms
2166 ms
3778 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Onon.tmall.com, 33% (35 requests) were made to G.alicdn.com and 22% (23 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Tmall.com.
Page size can be reduced by 371.7 kB (11%)
3.3 MB
2.9 MB
In fact, the total size of Onon.tmall.com main page is 3.3 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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 138.4 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 25.5 kB, which is 14% 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 138.4 kB or 77% of the original size.
Potential reduce by 33.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. Onon Tmall images are well optimized though.
Potential reduce by 148.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 148.7 kB or 35% of the original size.
Potential reduce by 51.3 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. Onon.tmall.com needs all CSS files to be minified and compressed as it can save up to 51.3 kB or 73% of the original size.
Number of requests can be reduced by 47 (55%)
86
39
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Onon 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 10 to 1 for CSS and as a result speed up the page load time.
onon.tmall.com
1152 ms
onon.tmall.com
2040 ms
onon.world.tmall.com
914 ms
onon.world.tmall.com
2166 ms
jump
3778 ms
add
4597 ms
onon.world.tmall.com
412 ms
onon.world.tmall.com
4784 ms
onon.world.tmall.com
410 ms
onon.world.tmall.com
8694 ms
global-min.css
351 ms
seed-min.js
413 ms
global-min.js
604 ms
g.alicdn.com
398 ms
g.alicdn.com
402 ms
brandbar-min.css
407 ms
copyright-min.css
404 ms
519 ms
TB1OwBIGXXXXXbhXXXXn00bFXXX.css
477 ms
index.js
453 ms
init-async-min.js
442 ms
s.gif
550 ms
184 ms
92 ms
90 ms
aplus_v2.js
45 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
7181 ms
getipinfo
7155 ms
counter6
8063 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
7153 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
7148 ms
shopinfo-min.css
96 ms
aplus_v2.js
449 ms
346 ms
336 ms
font_1451273740_187741.woff
7286 ms
380 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
6670 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
6668 ms
agp_heat.min.js
6571 ms
wp-beacon.js
6568 ms
2.gif
2652 ms
ahot.1.9
3114 ms
blank
130 ms
bgheader1.jpg
304 ms
281 ms
T1vEi4XnhyXXXm0Pva-454-340.png
182 ms
downarrow.png
181 ms
rightarrow.png
178 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
317 ms
164 ms
163 ms
processUserCookie.htm
4088 ms
posttry.js
270 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
268 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
274 ms
TB2VvfelVXXXXaKXXXXXXXXXXXX_!!1610153279.jpg
264 ms
TB2jmGWlVXXXXXhXpXXXXXXXXXX_!!1610153279.jpg
263 ms
TB24QrllVXXXXXgXXXXXXXXXXXX_!!1610153279.jpg
255 ms
TB2VDqBlVXXXXa7XpXXXXXXXXXX_!!1610153279.jpg
260 ms
TB2FECElVXXXXa8XpXXXXXXXXXX_!!1610153279.jpg
300 ms
TB2N7OBlVXXXXXSXpXXXXXXXXXX_!!1610153279.jpg
261 ms
TB29Ka8lVXXXXbUXXXXXXXXXXXX_!!1610153279.jpg
297 ms
TB2f3uYlVXXXXc_XXXXXXXXXXXX_!!1610153279.jpg
261 ms
TB2f7KVlVXXXXc3XXXXXXXXXXXX_!!1610153279.jpg
261 ms
TB2KVe5lVXXXXbtXXXXXXXXXXXX_!!1610153279.jpg
297 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
188 ms
font_1433225452_0164654.woff
149 ms
108 ms
137 ms
136 ms
webww.js
151 ms
index.js
149 ms
138 ms
TB1NTWZLFXXXXbuaXXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E82a8d4b35d5c8c01515dab3e51d7c6ef;lang%5Egbk;t%5E1460107508000
653 ms
TB2i_7OjVXXXXcfXXXXXXXXXXXX_!!1610153279.jpg
33 ms
vdata.htm
563 ms
TB2kPExjVXXXXayXpXXXXXXXXXX_!!1610153279.jpg
56 ms
TB2ttwrjVXXXXbNXpXXXXXXXXXX_!!1610153279.jpg
55 ms
TB2MUsZjVXXXXaoXXXXXXXXXXXX_!!1610153279.jpg
51 ms
TB29D72jVXXXXahXXXXXXXXXXXX_!!1610153279.jpg
51 ms
TB2y3ApjVXXXXbGXpXXXXXXXXXX_!!1610153279.jpg
56 ms
localhost.wwbizsrv.alibaba.com
34 ms
muliuserstatus.aw
6021 ms
TB2u_bymXXXXXXLXpXXXXXXXXXX_!!1610153279.jpg
130 ms
index.js
63 ms
index.js
50 ms
localhost.wwbizsrv.alibaba.com
2 ms
ww.69.2
2170 ms
app.gif
1957 ms
adapter.js
157 ms
ww.69.2
803 ms
jump
3114 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
92 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
354 ms
add
10853 ms
www.tmall.com
20156 ms
translateelement.css
38 ms
main.js
49 ms
loading.gif
676 ms
favicon.ico
598 ms
element_main.js
170 ms
translate_24dp.png
352 ms
l
265 ms
cleardot.gif
385 ms
onon.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
onon.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
onon.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 Onon.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 Onon.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.
onon.tmall.com
Open Graph description is not detected on the main page of Onon 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: