41.3 sec in total
1.1 sec
39 sec
1.2 sec
Click here to check amazing Phoenix Tmall content for China. Otherwise, check out these important facts you probably never knew about phoenix.tmall.com
淘宝, 店铺, 旺铺, 凤凰官方旗舰店
Visit phoenix.tmall.comWe analyzed Phoenix.tmall.com page load time and found that the first response time was 1.1 sec and then it took 40.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
phoenix.tmall.com performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value11.4 s
0/100
25%
Value9.1 s
14/100
10%
Value290 ms
80/100
30%
Value0.002
100/100
15%
Value11.5 s
18/100
10%
1100 ms
6901 ms
5191 ms
4462 ms
1785 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Phoenix.tmall.com, 32% (36 requests) were made to G.alicdn.com and 23% (25 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Phoenix.tmall.com.
Page size can be reduced by 375.1 kB (14%)
2.6 MB
2.2 MB
In fact, the total size of Phoenix.tmall.com main page is 2.6 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 133.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 26.6 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 133.4 kB or 77% of the original size.
Potential reduce by 40.7 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. Phoenix 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 52.4 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. Phoenix.tmall.com needs all CSS files to be minified and compressed as it can save up to 52.4 kB or 69% of the original size.
Number of requests can be reduced by 52 (57%)
92
40
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phoenix 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.
phoenix.tmall.com
1100 ms
phoenix.tmall.com
6901 ms
phoenix.world.tmall.com
5191 ms
phoenix.world.tmall.com
4462 ms
jump
1785 ms
add
3593 ms
phoenix.world.tmall.com
513 ms
phoenix.world.tmall.com
384 ms
phoenix.world.tmall.com
496 ms
phoenix.world.tmall.com
3626 ms
global-min.css
258 ms
seed-min.js
344 ms
global-min.js
443 ms
g.alicdn.com
271 ms
g.alicdn.com
269 ms
brandbar-min.css
271 ms
copyright-min.css
284 ms
407 ms
g.alicdn.com
304 ms
index.js
305 ms
init-async-min.js
306 ms
TB2qpiimFXXXXbaXpXXXXXXXXXX_!!707662361.jpg
114 ms
s.gif
2896 ms
117 ms
55 ms
73 ms
aplus_v2.js
51 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
2704 ms
getipinfo
2812 ms
counter6
4638 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
2788 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
2733 ms
shopinfo-min.css
52 ms
42 ms
146 ms
font_1451273740_187741.woff
2843 ms
aplus_v2.js
145 ms
2625 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
2716 ms
blank
8 ms
TB12Ne2LFXXXXcvapXXSutbFXXX.jpg
2608 ms
T1vEi4XnhyXXXm0Pva-454-340.png
2658 ms
blank
67 ms
T1GjdOXA8XXXbHTkoN-122-235.png
2569 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
2620 ms
T156jcXXhfXXcMeXnl-22-160.gif
2621 ms
agp_heat.min.js
2499 ms
wp-beacon.js
2660 ms
2.gif
4355 ms
ahot.1.9
4227 ms
165 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
142 ms
TB2dBEkbXXXXXb6XpXXXXXXXXXX_!!707662361.jpg
210 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
162 ms
posttry.js
97 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
103 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
124 ms
font_1433225452_0164654.woff
197 ms
115 ms
122 ms
webww.js
48 ms
index.js
61 ms
102 ms
localhost.wwbizsrv.alibaba.com
8 ms
muliuserstatus.aw
2541 ms
processUserCookie.htm
4576 ms
42 ms
60 ms
108 ms
TB1BELkLFXXXXbCXFXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5Eda2545294aec81337d9f7db533aca61c;lang%5Egbk;t%5E1460133048000
435 ms
TB2hfHmlVXXXXayXpXXXXXXXXXX_!!707662361.png
16 ms
vdata.htm
398 ms
TB2VEbjlVXXXXaEXpXXXXXXXXXX_!!707662361.png
19 ms
TB2jURBmXXXXXbKXpXXXXXXXXXX_!!707662361.jpg
289 ms
TB2E9KAmFXXXXbMXXXXXXXXXXXX_!!707662361.jpg
197 ms
TB2f839lFXXXXcpXXXXXXXXXXXX_!!707662361.jpg
18 ms
TB2FuoJlFXXXXcDXpXXXXXXXXXX_!!707662361.jpg
30 ms
TB2yXwYlFXXXXahXpXXXXXXXXXX_!!707662361.jpg
30 ms
TB2nOFmlVXXXXX0XXXXXXXXXXXX_!!707662361.jpg
41 ms
TB2ae0olVXXXXXBXXXXXXXXXXXX_!!707662361.jpg
43 ms
TB2uxw2lFXXXXXaXpXXXXXXXXXX_!!707662361.jpg
43 ms
TB2NI74kpXXXXaoXpXXXXXXXXXX_!!707662361.jpg
134 ms
TB2wW0ekFXXXXc6XXXXXXXXXXXX_!!707662361.jpg
190 ms
TB2xX4dkFXXXXcSXXXXXXXXXXXX_!!707662361.jpg
59 ms
TB2w4JhkFXXXXcjXXXXXXXXXXXX_!!707662361.jpg
64 ms
TB2NT4nkFXXXXa5XXXXXXXXXXXX_!!707662361.jpg
69 ms
TB2ojVekFXXXXcKXXXXXXXXXXXX_!!707662361.jpg
127 ms
TB2lHk3kpXXXXbqXpXXXXXXXXXX_!!707662361.jpg
122 ms
TB23nhskFXXXXXCXXXXXXXXXXXX_!!707662361.jpg
161 ms
TB24plckFXXXXXAXpXXXXXXXXXX_!!707662361.jpg
174 ms
index.js
28 ms
index.js
52 ms
localhost.wwbizsrv.alibaba.com
1 ms
ww.69.2
541 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
10 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
230 ms
adapter.js
46 ms
ww.69.2
86 ms
T1FXHXXahjXXXAK3zo-77-18.gif
9 ms
app.gif
5799 ms
jump
373 ms
add
3590 ms
www.tmall.com
1891 ms
translateelement.css
47 ms
main.js
60 ms
loading.gif
162 ms
favicon.ico
378 ms
element_main.js
166 ms
translate_24dp.png
80 ms
l
43 ms
cleardot.gif
100 ms
phoenix.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
phoenix.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
phoenix.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 Phoenix.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 Phoenix.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.
phoenix.tmall.com
Open Graph description is not detected on the main page of Phoenix 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: