54.8 sec in total
4 sec
49.6 sec
1.2 sec
Click here to check amazing Xingyuets Tmall content for China. Otherwise, check out these important facts you probably never knew about xingyuets.tmall.com
兴阅图书专营店是由品牌官方企业运营或授权的官网旗舰店,所有商品保证正品无假货。兴阅图书专营店宝贝与描述相符评分为4.8分,与同行业平均水平持平,卖家的服务态度评分为4.8分,与同行业平均水平持平,物流服务的质量评分为4.8分,与同行业平均水平持平。
Visit xingyuets.tmall.comWe analyzed Xingyuets.tmall.com page load time and found that the first response time was 4 sec and then it took 50.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.
xingyuets.tmall.com performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value11.4 s
0/100
25%
Value8.7 s
17/100
10%
Value1,150 ms
22/100
30%
Value0.002
100/100
15%
Value11.8 s
17/100
10%
3970 ms
4435 ms
913 ms
4539 ms
3799 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Xingyuets.tmall.com, 33% (33 requests) were made to G.alicdn.com and 26% (26 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Gskip.taobao.com.
Page size can be reduced by 972.6 kB (34%)
2.8 MB
1.9 MB
In fact, the total size of Xingyuets.tmall.com main page is 2.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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 521.7 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 236.7 kB, which is 41% 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 521.7 kB or 90% of the original size.
Potential reduce by 67.0 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. Xingyuets Tmall images are well optimized though.
Potential reduce by 154.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 154.7 kB or 45% of the original size.
Potential reduce by 229.2 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. Xingyuets.tmall.com needs all CSS files to be minified and compressed as it can save up to 229.2 kB or 86% of the original size.
Number of requests can be reduced by 43 (52%)
82
39
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xingyuets 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 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
xingyuets.tmall.com
3970 ms
xingyuets.tmall.com
4435 ms
xingyuets.world.tmall.com
913 ms
xingyuets.world.tmall.com
4539 ms
jump
3799 ms
add
4578 ms
xingyuets.world.tmall.com
432 ms
xingyuets.world.tmall.com
395 ms
xingyuets.world.tmall.com
427 ms
xingyuets.world.tmall.com
9432 ms
global-min.css
275 ms
seed-min.js
302 ms
global-min.js
351 ms
g.alicdn.com
299 ms
g.alicdn.com
298 ms
copyright-min.css
299 ms
342 ms
TB1ZFKlKVXXXXcKXVXXn00bFXXX.css
429 ms
index.js
339 ms
init-async-min.js
339 ms
125 ms
121 ms
aplus_v2.js
113 ms
303 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
344 ms
getipinfo
4202 ms
counter6
5804 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
4226 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
4163 ms
aplus_v2.js
71 ms
font_1451273740_187741.woff
4555 ms
3955 ms
xwj_heat.js
3900 ms
agp_heat.min.js
3906 ms
wp-beacon.js
4397 ms
2.gif
2014 ms
ahot.1.9
3430 ms
TB2h_F_kVXXXXXVXXXXXXXXXXXX_!!1698005656.png
214 ms
TB2_j03kVXXXXaUXXXXXXXXXXXX_!!1698005656.png
501 ms
TB2XyWakFXXXXXpXpXXXXXXXXXX_!!1698005656.jpg
580 ms
TB2NHUzlVXXXXXLXXXXXXXXXXXX_!!1698005656.jpg
759 ms
TB2Bs66lFXXXXa2XpXXXXXXXXXX_!!1698005656.jpg
644 ms
TB2_zBYkpXXXXXFXXXXXXXXXXXX_!!1698005656.jpg
613 ms
shopinfo-min.css
64 ms
71 ms
85 ms
processUserCookie.htm
19754 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
425 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
425 ms
blank
80 ms
319 ms
TB1vfGBLXXXXXbuXXXXSutbFXXX.jpg
417 ms
TB21e0LiVXXXXbiXXXXXXXXXXXX_!!1698005656.jpg
410 ms
T1vEi4XnhyXXXm0Pva-454-340.png
375 ms
352 ms
386 ms
xialahover.png
286 ms
69 ms
123 ms
118 ms
prev.png
153 ms
next.png
154 ms
TB2VAxIiFXXXXaEXpXXXXXXXXXX_!!1698005656.jpg
117 ms
s.gif
66 ms
TB2WhUOlVXXXXXiXXXXXXXXXXXX_!!1698005656.jpg
241 ms
bgg.jpg
70 ms
lor.png
45 ms
TB23ZhpiVXXXXbaXpXXXXXXXXXX_!!1698005656.jpg
164 ms
TB2kHXIiFXXXXalXpXXXXXXXXXX_!!1698005656.jpg
149 ms
TB2KGdqiVXXXXagXpXXXXXXXXXX_!!1698005656.jpg
173 ms
slides-shadow.png
76 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
83 ms
app.gif
11132 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
68 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
68 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
267 ms
font_1433225452_0164654.woff
39 ms
posttry.js
33 ms
webww.js
282 ms
index.js
282 ms
56 ms
TB1no_zLFXXXXaLXXXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5Ece12ed3baebd362a76c9dc860f334304;lang%5Egbk;t%5E1460110356000
587 ms
TB2BfAmiFXXXXcaXXXXXXXXXXXX_!!1698005656.jpg
110 ms
vdata.htm
2436 ms
TB2l2rtkVXXXXbwXpXXXXXXXXXX_!!1698005656.jpg
106 ms
TB2zliXiFXXXXaqXXXXXXXXXXXX_!!1698005656.jpg
81 ms
TB2ezsuiFXXXXaBXXXXXXXXXXXX_!!1698005656.jpg
82 ms
localhost.wwbizsrv.alibaba.com
72 ms
muliuserstatus.aw
3627 ms
index.js
42 ms
index.js
50 ms
localhost.wwbizsrv.alibaba.com
1 ms
ww.69.2
509 ms
adapter.js
30 ms
ww.69.2
87 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
74 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
459 ms
T1uUG.XjtkXXcb2gzo-77-19.gif
33 ms
T1FXHXXahjXXXAK3zo-77-18.gif
37 ms
xingyuets.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
xingyuets.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
xingyuets.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 Xingyuets.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 Xingyuets.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.
xingyuets.tmall.com
Open Graph description is not detected on the main page of Xingyuets 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: