49.4 sec in total
4.1 sec
42.9 sec
2.3 sec
Click here to check amazing Pipiniu Tmall content for China. Otherwise, check out these important facts you probably never knew about pipiniu.tmall.com
淘宝, 店铺, 旺铺, 皮皮牛童装旗舰店
Visit pipiniu.tmall.comWe analyzed Pipiniu.tmall.com page load time and found that the first response time was 4.1 sec and then it took 45.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.
pipiniu.tmall.com performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value10.8 s
0/100
25%
Value8.7 s
17/100
10%
Value120 ms
97/100
30%
Value0.002
100/100
15%
Value9.8 s
28/100
10%
4146 ms
2037 ms
954 ms
1623 ms
6437 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Pipiniu.tmall.com, 34% (34 requests) were made to G.alicdn.com and 25% (25 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (12.4 sec) relates to the external source Gskip.taobao.com.
Page size can be reduced by 453.3 kB (30%)
1.5 MB
1.1 MB
In fact, the total size of Pipiniu.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. Images take 849.0 kB which makes up the majority of the site volume.
Potential reduce by 134.5 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 28.0 kB, which is 16% 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 134.5 kB or 77% of the original size.
Potential reduce by 43.5 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. Pipiniu Tmall images are well optimized though.
Potential reduce by 147.8 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 147.8 kB or 44% of the original size.
Potential reduce by 127.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. Pipiniu.tmall.com needs all CSS files to be minified and compressed as it can save up to 127.4 kB or 83% of the original size.
Number of requests can be reduced by 48 (58%)
83
35
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pipiniu 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 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
pipiniu.tmall.com
4146 ms
pipiniu.tmall.com
2037 ms
pipiniu.world.tmall.com
954 ms
pipiniu.world.tmall.com
1623 ms
jump
6437 ms
add
1544 ms
pipiniu.world.tmall.com
413 ms
pipiniu.world.tmall.com
395 ms
pipiniu.world.tmall.com
1742 ms
pipiniu.world.tmall.com
9279 ms
global-min.css
471 ms
seed-min.js
528 ms
global-min.js
600 ms
g.alicdn.com
487 ms
g.alicdn.com
482 ms
brandbar-min.css
483 ms
copyright-min.css
500 ms
591 ms
g.alicdn.com
593 ms
TB1kuXmMpXXXXczXpXXn00bFXXX.css
460 ms
index.js
524 ms
init-async-min.js
539 ms
85 ms
41 ms
53 ms
83 ms
62 ms
57 ms
33 ms
28 ms
36 ms
TB2WxU5jVXXXXcqXXXXXXXXXXXX_!!1829418276.png
41 ms
aplus_v2.js
49 ms
s.gif
1973 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
101 ms
posttry.js
45 ms
TB2ssxVbVXXXXa3XXXXXXXXXXXX_!!1829418276.png
65 ms
TB2UOjJbFXXXXazXpXXXXXXXXXX_!!1829418276.gif
55 ms
TB2_LYVbFXXXXXOXXXXXXXXXXXX_!!1829418276.gif
72 ms
TB2XR3DXVXXXXX4XXXXXXXXXXXX_!!1829418276.gif
1907 ms
TB2CikCXVXXXXbTXXXXXXXXXXXX_!!1829418276.gif
67 ms
TB2wVknbFXXXXaJXXXXXXXXXXXX_!!1829418276.gif
72 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
100 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
99 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
118 ms
getipinfo
1876 ms
counter6
3466 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
1952 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
81 ms
shopinfo-min.css
53 ms
51 ms
80 ms
font_1451273740_187741.woff
2036 ms
aplus_v2.js
93 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
1901 ms
blank
9 ms
TB20NhQbVXXXXXyXpXXXXXXXXXX_!!1829418276.png
1774 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
1774 ms
blank
1758 ms
1828 ms
T1GjdOXA8XXXbHTkoN-122-235.png
1827 ms
T156jcXXhfXXcMeXnl-22-160.gif
1828 ms
agp_heat.min.js
1822 ms
wp-beacon.js
1877 ms
2.gif
5092 ms
ahot.1.9
5554 ms
processUserCookie.htm
12423 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
57 ms
TB2eoCXlVXXXXbfXXXXXXXXXXXX_!!1829418276.jpg
115 ms
TB2A1UmkVXXXXcqXXXXXXXXXXXX_!!1829418276.png
112 ms
font_1433225452_0164654.woff
151 ms
webww.js
90 ms
index.js
90 ms
75 ms
blank
36 ms
TB1vsqGMXXXXXcgXVXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E886fe798d2d1386b10dcbe5f8c3c69d2;lang%5Egbk;t%5E1460135895000
594 ms
TB2JM8omFXXXXaxXXXXXXXXXXXX_!!1829418276.jpg
210 ms
vdata.htm
396 ms
TB2QspXmFXXXXcSXXXXXXXXXXXX_!!1829418276.jpg
869 ms
TB2wu3KmpXXXXcsXpXXXXXXXXXX_!!1829418276.jpg
203 ms
TB2Ln8nmFXXXXaIXXXXXXXXXXXX_!!1829418276.gif
108 ms
TB2NEALmpXXXXb9XpXXXXXXXXXX_!!1829418276.jpg
811 ms
TB2yfUTmpXXXXaAXpXXXXXXXXXX_!!1829418276.jpg
256 ms
TB2Fp0nmFXXXXaFXXXXXXXXXXXX_!!1829418276.jpg
1036 ms
TB2jmNxmFXXXXXfXXXXXXXXXXXX_!!1829418276.jpg
373 ms
TB2QxcMmpXXXXbIXpXXXXXXXXXX_!!1829418276.jpg
313 ms
TB2XgBmmFXXXXaNXXXXXXXXXXXX_!!1829418276.jpg
508 ms
TB2nvxfmFXXXXbtXXXXXXXXXXXX_!!1829418276.jpg
1091 ms
localhost.wwbizsrv.alibaba.com
50 ms
muliuserstatus.aw
4363 ms
index.js
31 ms
index.js
31 ms
localhost.wwbizsrv.alibaba.com
1 ms
ww.69.2
428 ms
adapter.js
35 ms
ww.69.2
83 ms
T1FXHXXahjXXXAK3zo-77-18.gif
11 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
11 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
193 ms
T1FXHXXahjXXXAK3zo-77-18.gif
61 ms
app.gif
2829 ms
pipiniu.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
pipiniu.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
Registers an unload listener
pipiniu.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 Pipiniu.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 Pipiniu.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.
pipiniu.tmall.com
Open Graph description is not detected on the main page of Pipiniu 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: