58.3 sec in total
819 ms
55.9 sec
1.6 sec
Welcome to bliss.tmall.com homepage info - get ready to check Bliss Tmall best content for China right away, or after learning these important things about bliss.tmall.com
淘宝, 店铺, 旺铺, 百丽丝家纺旗舰店
Visit bliss.tmall.comWe analyzed Bliss.tmall.com page load time and found that the first response time was 819 ms and then it took 57.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
bliss.tmall.com performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value14.1 s
0/100
25%
Value20.9 s
0/100
10%
Value310 ms
77/100
30%
Value1.179
1/100
15%
Value14.7 s
8/100
10%
819 ms
1985 ms
917 ms
3579 ms
13917 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Bliss.tmall.com, 47% (55 requests) were made to G.alicdn.com and 14% (16 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (13.9 sec) relates to the external source Login.taobao.com.
Page size can be reduced by 521.6 kB (29%)
1.8 MB
1.3 MB
In fact, the total size of Bliss.tmall.com main page is 1.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. 45% of websites need less resources to load. Images take 916.2 kB which makes up the majority of the site volume.
Potential reduce by 108.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 108.4 kB or 73% of the original size.
Potential reduce by 18.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. Bliss Tmall images are well optimized though.
Potential reduce by 242.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 242.6 kB or 45% of the original size.
Potential reduce by 152.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. Bliss.tmall.com needs all CSS files to be minified and compressed as it can save up to 152.3 kB or 79% of the original size.
Number of requests can be reduced by 65 (66%)
99
34
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bliss 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 48 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
bliss.tmall.com
819 ms
bliss.tmall.com
1985 ms
bliss.world.tmall.com
917 ms
bliss.world.tmall.com
3579 ms
jump
13917 ms
add
5175 ms
bliss.world.tmall.com
465 ms
bliss.world.tmall.com
1479 ms
bliss.world.tmall.com
411 ms
bliss.world.tmall.com
9424 ms
global-min.css
690 ms
seed-min.js
835 ms
global-min.js
919 ms
g.alicdn.com
1143 ms
g.alicdn.com
617 ms
brandbar-min.css
648 ms
copyright-min.css
889 ms
861 ms
g.alicdn.com
737 ms
TB1puYdMXXXXXauXFXXn00bFXXX.css
868 ms
index.js
859 ms
init-async-min.js
878 ms
base-min.js
62 ms
attribute-min.js
53 ms
custom-min.js
57 ms
base-min.js
61 ms
event-min.js
53 ms
base-min.js
87 ms
base-min.js
88 ms
ie-min.js
360 ms
touch-min.js
93 ms
hashchange-min.js
364 ms
ie-min.js
415 ms
node-min.js
117 ms
anim-min.js
120 ms
base-min.js
140 ms
promise-min.js
139 ms
timer-min.js
166 ms
transition-min.js
251 ms
io-min.js
292 ms
json-min.js
331 ms
cookie-min.js
291 ms
TB25iqzlFXXXXarXXXXXXXXXXXX-170712287.png
101 ms
TB2Ka1tmFXXXXXJXXXXXXXXXXXX-170712287.png
4635 ms
aplus_v2.js
88 ms
294 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
4950 ms
getipinfo
4919 ms
counter6
9042 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
4972 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
4963 ms
shopinfo-min.css
168 ms
166 ms
220 ms
font_1451273740_187741.woff
4934 ms
aplus_v2.js
207 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
4848 ms
s.gif
4851 ms
blank
4305 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
4414 ms
TB15oWIGpXXXXcMXXXXtKXbFXXX.gif
4509 ms
TB2wYX.lFXXXXbFXpXXXXXXXXXX-170712287.jpg
4586 ms
T1vEi4XnhyXXXm0Pva-454-340.png
4745 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
4909 ms
xwj_heat.js
4353 ms
agp_heat.min.js
4353 ms
wp-beacon.js
4889 ms
2.gif
6358 ms
ahot.1.9
9750 ms
blank
28 ms
181 ms
175 ms
T1GjdOXA8XXXbHTkoN-122-235.png
318 ms
T156jcXXhfXXcMeXnl-22-160.gif
482 ms
posttry.js
284 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
434 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
581 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
250 ms
font_1433225452_0164654.woff
342 ms
266 ms
279 ms
processUserCookie.htm
3976 ms
webww.js
124 ms
index.js
123 ms
116 ms
T1kyVWFe8dXXcjfCvX-140-75.png
348 ms
T1p8v6XfJjXXXTOpDa-17-16.png
456 ms
adapter.js
60 ms
muliuserstatus.aw
5768 ms
57 ms
52 ms
63 ms
blank
31 ms
TB1UbvUJVXXXXa9XXXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E1c1527f777965ebeea262e23a822f335;lang%5Egbk;t%5E1460102295000
460 ms
T2bLRjXexXXXXXXXXX_!!170712287.gif
63 ms
vdata.htm
407 ms
TB279CelFXXXXcQXXXXXXXXXXXX-170712287.jpg
3235 ms
TB20yGnlFXXXXb5XXXXXXXXXXXX-170712287.jpg
148 ms
TB2bFn2iVXXXXcSXXXXXXXXXXXX-170712287.jpg
545 ms
TB2r31glFXXXXcBXXXXXXXXXXXX-170712287.jpg
331 ms
TB2h69rlFXXXXbnXXXXXXXXXXXX-170712287.jpg
320 ms
TB2DMmclFXXXXXDXpXXXXXXXXXX-170712287.jpg
358 ms
TB23XmwlFXXXXaQXXXXXXXXXXXX-170712287.jpg
322 ms
index.js
41 ms
index.js
44 ms
jump
10552 ms
app.gif
1817 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
31 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
176 ms
add
397 ms
www.tmall.com
1629 ms
translateelement.css
26 ms
main.js
21 ms
loading.gif
492 ms
favicon.ico
472 ms
ahot.1.2
653 ms
element_main.js
802 ms
bliss.tmall.com accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
bliss.tmall.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Missing source maps for large first-party JavaScript
bliss.tmall.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bliss.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 Bliss.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.
bliss.tmall.com
Open Graph description is not detected on the main page of Bliss 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: