51.5 sec in total
1.1 sec
46.8 sec
3.5 sec
Visit jxh.tmall.com now to see the best up-to-date Jxh Tmall content for China and also check out these interesting facts you probably never knew about jxh.tmall.com
淘宝, 店铺, 旺铺, jxh旗舰店
Visit jxh.tmall.comWe analyzed Jxh.tmall.com page load time and found that the first response time was 1.1 sec and then it took 50.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
jxh.tmall.com performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value12.0 s
0/100
25%
Value9.3 s
12/100
10%
Value150 ms
95/100
30%
Value0.002
100/100
15%
Value11.8 s
17/100
10%
1070 ms
1788 ms
10445 ms
7121 ms
4737 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Jxh.tmall.com, 33% (36 requests) were made to G.alicdn.com and 25% (27 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (10.4 sec) relates to the external source Jxh.world.tmall.com.
Page size can be reduced by 580.1 kB (15%)
3.8 MB
3.2 MB
In fact, the total size of Jxh.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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 130.5 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 30.9 kB, which is 18% 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.5 kB or 76% of the original size.
Potential reduce by 247.2 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. Jxh Tmall images are well optimized though.
Potential reduce by 149.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 149.7 kB or 35% of the original size.
Potential reduce by 52.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. Jxh.tmall.com needs all CSS files to be minified and compressed as it can save up to 52.6 kB or 69% of the original size.
Number of requests can be reduced by 45 (48%)
94
49
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jxh 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.
jxh.tmall.com
1070 ms
jxh.tmall.com
1788 ms
jxh.world.tmall.com
10445 ms
jump
7121 ms
add
4737 ms
jxh.world.tmall.com
431 ms
jxh.world.tmall.com
466 ms
jxh.world.tmall.com
451 ms
jxh.world.tmall.com
4266 ms
global-min.css
332 ms
seed-min.js
357 ms
global-min.js
484 ms
g.alicdn.com
340 ms
g.alicdn.com
350 ms
brandbar-min.css
349 ms
copyright-min.css
427 ms
453 ms
g.alicdn.com
439 ms
index.js
427 ms
init-async-min.js
427 ms
posttry.js
433 ms
TB2RCT5mXXXXXXGXXXXXXXXXXXX_!!268485414.jpg
4460 ms
s.gif
4464 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
744 ms
TB2AfTQmXXXXXbGXXXXXXXXXXXX_!!268485414.jpg
4458 ms
TB2SzHqmXXXXXaYXpXXXXXXXXXX_!!268485414.jpg
4457 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
4458 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
4456 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
4459 ms
230 ms
134 ms
216 ms
aplus_v2.js
119 ms
getipinfo
4499 ms
counter6
5438 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
4504 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
4283 ms
shopinfo-min.css
363 ms
371 ms
358 ms
font_1451273740_187741.woff
4459 ms
aplus_v2.js
476 ms
3962 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
4093 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
3799 ms
blank
23 ms
3757 ms
T1vEi4XnhyXXXm0Pva-454-340.png
3843 ms
blank
28 ms
T1GjdOXA8XXXbHTkoN-122-235.png
3807 ms
T156jcXXhfXXcMeXnl-22-160.gif
3812 ms
agp_heat.min.js
3627 ms
wp-beacon.js
3719 ms
2.gif
2927 ms
ahot.1.9
3492 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
218 ms
font_1433225452_0164654.woff
385 ms
185 ms
260 ms
webww.js
168 ms
index.js
163 ms
127 ms
processUserCookie.htm
4470 ms
T1kyVWFe8dXXcjfCvX-140-75.png
423 ms
T1p8v6XfJjXXXTOpDa-17-16.png
465 ms
adapter.js
167 ms
muliuserstatus.aw
2008 ms
103 ms
164 ms
163 ms
TB1pEr.LVXXXXbaXXXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E2ea7e41ad1fa2f8003b2bb65ff2ade62;lang%5Egbk;t%5E1460104252000
880 ms
TB2RioxmXXXXXc1XXXXXXXXXXXX_!!268485414.jpg
758 ms
vdata.htm
498 ms
TB2gDYRmXXXXXb1XXXXXXXXXXXX_!!268485414.jpg
2516 ms
TB2HA2smXXXXXaPXpXXXXXXXXXX_!!268485414.jpg
3902 ms
TB2XsjomXXXXXbFXpXXXXXXXXXX_!!268485414.jpg
4283 ms
TB2CEMUmXXXXXX8XXXXXXXXXXXX_!!268485414.jpg
891 ms
TB28torXVXXXXXxXXXXXXXXXXXX_!!268485414.png
121 ms
TB2bhknXVXXXXa8XpXXXXXXXXXX_!!268485414.png
177 ms
TB2rK3DmXXXXXceXXXXXXXXXXXX_!!268485414.jpg
430 ms
TB2_U.amXXXXXXUXXXXXXXXXXXX_!!268485414.gif
556 ms
TB2VDbVmXXXXXcHXXXXXXXXXXXX_!!268485414.gif
742 ms
TB2lYbBmXXXXXa9XpXXXXXXXXXX_!!268485414.gif
902 ms
TB2om2EmXXXXXauXpXXXXXXXXXX_!!268485414.gif
850 ms
TB2Te6QmXXXXXXeXpXXXXXXXXXX_!!268485414.gif
958 ms
TB2qf64mXXXXXbhXXXXXXXXXXXX_!!268485414.gif
1114 ms
TB26U6ymXXXXXblXpXXXXXXXXXX_!!268485414.gif
1133 ms
TB2mvTImXXXXXaXXpXXXXXXXXXX_!!268485414.gif
1113 ms
TB2nBn2mXXXXXbJXXXXXXXXXXXX_!!268485414.gif
1243 ms
TB2uAjEmXXXXXaIXpXXXXXXXXXX_!!268485414.gif
1234 ms
TB2Z3bwmXXXXXbCXpXXXXXXXXXX_!!268485414.gif
1261 ms
TB2DTzOmXXXXXc4XXXXXXXXXXXX_!!268485414.gif
1352 ms
TB2EaY9mXXXXXaDXXXXXXXXXXXX_!!268485414.gif
1809 ms
index.js
67 ms
index.js
51 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
88 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
379 ms
app.gif
3401 ms
T1uUG.XjtkXXcb2gzo-77-19.gif
86 ms
jump
1703 ms
add
445 ms
www.tmall.com
1697 ms
translateelement.css
50 ms
main.js
60 ms
loading.gif
725 ms
favicon.ico
910 ms
element_main.js
138 ms
translate_24dp.png
448 ms
l
356 ms
cleardot.gif
483 ms
jxh.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
jxh.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
jxh.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
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jxh.tmall.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jxh.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.
jxh.tmall.com
Open Graph description is not detected on the main page of Jxh 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: