86.1 sec in total
1.3 sec
82.9 sec
1.8 sec
Click here to check amazing Shuihuiman Tmall content for China. Otherwise, check out these important facts you probably never knew about shuihuiman.tmall.com
水卉曼旗舰店是由品牌官方企业运营或授权的官网旗舰店,所有商品保证正品无假货。水卉曼旗舰店宝贝与描述相符评分为4.8分,比同行业平均水平低1.11%,卖家的服务态度评分为4.7分,比同行业平均水平低1.03%,物流服务的质量评分为4.8分,比同行业平均水平低0.58%。
Visit shuihuiman.tmall.comWe analyzed Shuihuiman.tmall.com page load time and found that the first response time was 1.3 sec and then it took 84.8 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.
shuihuiman.tmall.com performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value10.1 s
0/100
25%
Value14.0 s
1/100
10%
Value200 ms
89/100
30%
Value0.001
100/100
15%
Value12.8 s
13/100
10%
1306 ms
7928 ms
4193 ms
5250 ms
12319 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Shuihuiman.tmall.com, 35% (36 requests) were made to G.alicdn.com and 18% (19 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Shuihuiman.world.tmall.com.
Page size can be reduced by 765.6 kB (19%)
4.1 MB
3.3 MB
In fact, the total size of Shuihuiman.tmall.com main page is 4.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. 45% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 132.3 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 26.4 kB, which is 15% 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 132.3 kB or 77% of the original size.
Potential reduce by 21.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. Shuihuiman Tmall images are well optimized though.
Potential reduce by 156.6 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 156.6 kB or 35% of the original size.
Potential reduce by 455.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. Shuihuiman.tmall.com needs all CSS files to be minified and compressed as it can save up to 455.6 kB or 89% of the original size.
Number of requests can be reduced by 57 (66%)
87
30
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shuihuiman 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.
shuihuiman.tmall.com
1306 ms
shuihuiman.tmall.com
7928 ms
shuihuiman.world.tmall.com
4193 ms
shuihuiman.world.tmall.com
5250 ms
jump
12319 ms
add
7219 ms
shuihuiman.world.tmall.com
567 ms
shuihuiman.world.tmall.com
2033 ms
shuihuiman.world.tmall.com
577 ms
shuihuiman.world.tmall.com
13942 ms
global-min.css
306 ms
seed-min.js
734 ms
global-min.js
623 ms
g.alicdn.com
288 ms
g.alicdn.com
287 ms
brandbar-min.css
297 ms
copyright-min.css
491 ms
454 ms
TB1f0peJXXXXXcsXVXXn00bFXXX.css
1893 ms
.css
19573 ms
index.js
376 ms
init-async-min.js
384 ms
122 ms
120 ms
posttry.js
19 ms
T2JFwOXwpaXXXXXXXX-698264636.gif
61 ms
s.gif
3567 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
3780 ms
T2SqXGXG8XXXXXXXXX-698264636.png
109 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
3100 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
3559 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
4084 ms
46 ms
aplus_v2.js
46 ms
getipinfo
3297 ms
counter6
4987 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
3877 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
3759 ms
shopinfo-min.css
32 ms
3010 ms
aplus_v2.js
71 ms
19 ms
3001 ms
font_1451273740_187741.woff
3619 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
3718 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
3647 ms
TB1_K4bHXXXXXaSXVXXwu0bFXXX.png
3144 ms
TB14yfpMXXXXXXuXXXXSutbFXXX.jpg
3142 ms
T2A4FIXHRXXXXXXXXX-698264636.png
2992 ms
TB2cRPsmFXXXXbSXXXXXXXXXXXX_!!749551844.gif
3142 ms
T1vEi4XnhyXXXm0Pva-454-340.png
3399 ms
xwj_heat.js
2961 ms
agp_heat.min.js
2961 ms
wp-beacon.js
3364 ms
2.gif
2704 ms
ahot.1.9
3204 ms
171 ms
TB2aGz9bpXXXXXnXpXXXXXXXXXX-185879812.gif
236 ms
arrow.gif
235 ms
T156jcXXhfXXcMeXnl-22-160.gif
629 ms
255 ms
605 ms
TB2QUjXbXXXXXb5XpXXXXXXXXXX_!!749551844.jpg
1378 ms
mainarrow.gif
157 ms
sld_numbtn.gif
335 ms
TB2MBlLmFXXXXbjXpXXXXXXXXXX_!!749551844.png
4260 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
265 ms
font_1433225452_0164654.woff
503 ms
webww.js
134 ms
index.js
136 ms
469 ms
processUserCookie.htm
2348 ms
adapter.js
215 ms
muliuserstatus.aw
4510 ms
69 ms
68 ms
67 ms
T1kyVWFe8dXXcjfCvX-140-75.png
446 ms
T1p8v6XfJjXXXTOpDa-17-16.png
442 ms
TB1TYHYLFXXXXahXFXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E8dcf9be7f12aac3c9d32dcc854f42d1b;lang%5Egbk;t%5E1460129993000
461 ms
vdata.htm
590 ms
TB2aYYmmFXXXXaxXpXXXXXXXXXX_!!749551844.jpg
2826 ms
TB2T22CmFXXXXcpXXXXXXXXXXXX_!!749551844.jpg
3518 ms
T2a2R1XD0aXXXXXXXX-1862941194.png
99 ms
index.js
15 ms
index.js
10 ms
jump
531 ms
app.gif
7290 ms
add
10701 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
54 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
431 ms
T1FXHXXahjXXXAK3zo-77-18.gif
45 ms
TB25BjmmFXXXXagXpXXXXXXXXXX_!!749551844.jpg
2054 ms
www.tmall.com
1673 ms
ali-page-updater
40 ms
translateelement.css
50 ms
main.js
48 ms
loading.gif
586 ms
favicon.ico
581 ms
ahot.1.2
794 ms
element_main.js
545 ms
translate_24dp.png
205 ms
l
79 ms
cleardot.gif
193 ms
shuihuiman.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
shuihuiman.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
Detected JavaScript libraries
shuihuiman.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
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shuihuiman.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 Shuihuiman.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.
shuihuiman.tmall.com
Open Graph description is not detected on the main page of Shuihuiman 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: