57.9 sec in total
1.7 sec
55.7 sec
523 ms
Visit vsonic.tmall.com now to see the best up-to-date Vsonic Tmall content for China and also check out these interesting facts you probably never knew about vsonic.tmall.com
淘宝, 店铺, 旺铺, vsonic威索尼可旗舰店
Visit vsonic.tmall.comWe analyzed Vsonic.tmall.com page load time and found that the first response time was 1.7 sec and then it took 56.2 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.
vsonic.tmall.com performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value11.3 s
0/100
25%
Value9.1 s
14/100
10%
Value690 ms
43/100
30%
Value0.002
100/100
15%
Value11.9 s
17/100
10%
1748 ms
8663 ms
4421 ms
5684 ms
4424 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Vsonic.tmall.com, 34% (36 requests) were made to G.alicdn.com and 21% (22 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (10.5 sec) relates to the external source Pcookie.tmall.com.
Page size can be reduced by 640.0 kB (41%)
1.5 MB
904.6 kB
In fact, the total size of Vsonic.tmall.com main page is 1.5 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. Javascripts take 621.5 kB which makes up the majority of the site volume.
Potential reduce by 105.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. 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 105.3 kB or 73% of the original size.
Potential reduce by 4.6 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. Vsonic Tmall images are well optimized though.
Potential reduce by 288.2 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 288.2 kB or 46% of the original size.
Potential reduce by 241.9 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. Vsonic.tmall.com needs all CSS files to be minified and compressed as it can save up to 241.9 kB or 82% of the original size.
Number of requests can be reduced by 49 (54%)
90
41
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vsonic 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.
vsonic.tmall.com
1748 ms
vsonic.tmall.com
8663 ms
vsonic.world.tmall.com
4421 ms
vsonic.world.tmall.com
5684 ms
jump
4424 ms
add
2695 ms
vsonic.world.tmall.com
668 ms
vsonic.world.tmall.com
667 ms
vsonic.world.tmall.com
667 ms
vsonic.world.tmall.com
3079 ms
global-min.css
395 ms
seed-min.js
424 ms
global-min.js
462 ms
g.alicdn.com
421 ms
g.alicdn.com
417 ms
brandbar-min.css
423 ms
copyright-min.css
455 ms
503 ms
g.alicdn.com
458 ms
index.js
457 ms
init-async-min.js
458 ms
77 ms
42 ms
TB2XaQrlFXXXXbhXXXXXXXXXXXX_!!2580483446.jpg
2822 ms
s.gif
159 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
2957 ms
TB2BGX.lFXXXXXuXpXXXXXXXXXX_!!2580483446.jpg
2829 ms
TB2NjEbipXXXXa0XpXXXXXXXXXX_!!2580483446.jpg
2824 ms
TB2XV3giFXXXXXlXpXXXXXXXXXX_!!2580483446.jpg
2823 ms
TB24E.wiFXXXXXYXXXXXXXXXXXX_!!2580483446.jpg
2827 ms
TB2O6oeiFXXXXXIXpXXXXXXXXXX_!!2580483446.jpg
2825 ms
TB2cPEjiFXXXXceXXXXXXXXXXXX_!!2580483446.jpg
2829 ms
TB28jD9iFXXXXbtXpXXXXXXXXXX_!!2580483446.jpg
2895 ms
TB2.E3fiFXXXXXpXpXXXXXXXXXX_!!2580483446.jpg
2893 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
2870 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
2955 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
3024 ms
aplus_v2.js
37 ms
133 ms
getipinfo
2931 ms
counter6
7500 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
2731 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
2918 ms
shopinfo-min.css
107 ms
aplus_v2.js
80 ms
43 ms
72 ms
font_1451273740_187741.woff
2851 ms
posttry.js
59 ms
49 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
2621 ms
TB1xRnQLVXXXXb2aXXXSutbFXXX
2699 ms
TB2mjAoiFXXXXbrXXXXXXXXXXXX_!!2580483446.jpg
2701 ms
TB2sg67XVXXXXcAXXXXXXXXXXXX-456989075.gif
2699 ms
TB2bLApiFXXXXboXXXXXXXXXXXX_!!2580483446.jpg
2700 ms
TB2vbAbiFXXXXaoXpXXXXXXXXXX_!!2580483446.jpg
2716 ms
TB2WXwCiFXXXXXeXXXXXXXXXXXX_!!2580483446.jpg
2723 ms
TB2mDn_iFXXXXbgXpXXXXXXXXXX_!!2580483446.jpg
2721 ms
TB2RDQbiFXXXXalXpXXXXXXXXXX_!!2580483446.jpg
2720 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
2792 ms
T1vEi4XnhyXXXm0Pva-454-340.png
2757 ms
agp_heat.min.js
2550 ms
wp-beacon.js
2549 ms
2.gif
6640 ms
ahot.1.9
7228 ms
182 ms
T1GjdOXA8XXXbHTkoN-122-235.png
256 ms
T156jcXXhfXXcMeXnl-22-160.gif
339 ms
166 ms
166 ms
TB2t8pCeXXXXXb6XpXXXXXXXXXX_!!2580483446.jpg
319 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
203 ms
font_1433225452_0164654.woff
310 ms
webww.js
100 ms
index.js
99 ms
100 ms
53 ms
52 ms
52 ms
muliuserstatus.aw
7827 ms
processUserCookie.htm
9469 ms
TB13WPsLFXXXXbEXpXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5Eef08049fe2f1fd02ab71401bfbc5da50;lang%5Egbk;t%5E1459133735000
583 ms
vdata.htm
672 ms
TB262vjipXXXXbjXXXXXXXXXXXX_!!2580483446.jpg
68 ms
index.js
27 ms
index.js
28 ms
ww.69.2
434 ms
adapter.js
27 ms
ww.69.2
90 ms
app.gif
10486 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
35 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
330 ms
T1uUG.XjtkXXcb2gzo-77-19.gif
31 ms
T1FXHXXahjXXXAK3zo-77-18.gif
36 ms
jump
679 ms
add
2379 ms
www.tmall.com
3002 ms
translateelement.css
31 ms
main.js
30 ms
loading.gif
346 ms
favicon.ico
3353 ms
element_main.js
98 ms
translate_24dp.png
53 ms
l
46 ms
cleardot.gif
77 ms
vsonic.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
vsonic.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
vsonic.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
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vsonic.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 Vsonic.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.
vsonic.tmall.com
Open Graph description is not detected on the main page of Vsonic 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: