67.4 sec in total
2.1 sec
54.5 sec
10.9 sec
Welcome to peoleo.tmall.com homepage info - get ready to check Peoleo Tmall best content for China right away, or after learning these important things about peoleo.tmall.com
淘宝, 店铺, 旺铺, peoleo飘蕾旗舰店
Visit peoleo.tmall.comWe analyzed Peoleo.tmall.com page load time and found that the first response time was 2.1 sec and then it took 65.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
peoleo.tmall.com performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value11.1 s
0/100
25%
Value8.5 s
18/100
10%
Value320 ms
76/100
30%
Value0.002
100/100
15%
Value11.3 s
19/100
10%
2099 ms
5589 ms
1141 ms
1802 ms
4449 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Peoleo.tmall.com, 48% (54 requests) were made to G.alicdn.com and 16% (18 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (15.3 sec) relates to the external source Count.taobao.com.
Page size can be reduced by 682.2 kB (18%)
3.8 MB
3.1 MB
In fact, the total size of Peoleo.tmall.com main page is 3.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. 50% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 184.6 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 41.0 kB, which is 18% 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 184.6 kB or 81% of the original size.
Potential reduce by 24.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. Peoleo Tmall images are well optimized though.
Potential reduce by 189.3 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 189.3 kB or 37% of the original size.
Potential reduce by 283.8 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. Peoleo.tmall.com needs all CSS files to be minified and compressed as it can save up to 283.8 kB or 88% of the original size.
Number of requests can be reduced by 68 (72%)
95
27
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Peoleo 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 50 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
peoleo.tmall.com
2099 ms
peoleo.tmall.com
5589 ms
peoleo.world.tmall.com
1141 ms
peoleo.world.tmall.com
1802 ms
jump
4449 ms
add
11048 ms
peoleo.world.tmall.com
5091 ms
peoleo.world.tmall.com
1693 ms
peoleo.world.tmall.com
504 ms
peoleo.world.tmall.com
5143 ms
global-min.css
421 ms
seed-min.js
508 ms
global-min.js
677 ms
g.alicdn.com
386 ms
g.alicdn.com
401 ms
brandbar-min.css
400 ms
copyright-min.css
453 ms
654 ms
TB16HH1IXXXXXXAXVXXn00bFXXX.css
1188 ms
default_ed.css
833 ms
index.js
463 ms
init-async-min.js
475 ms
282 ms
90 ms
s.gif
3348 ms
aplus_v2.js
109 ms
174 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
3329 ms
getipinfo
3266 ms
counter6
15313 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
3307 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
3305 ms
shopinfo-min.css
100 ms
115 ms
216 ms
font_1451273740_187741.woff
3776 ms
aplus_v2.js
198 ms
3159 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
3379 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
3382 ms
blank
22 ms
TB2c14kmFXXXXbLXXXXXXXXXXXX_!!672733129.jpg
3119 ms
TB2MVvOaVXXXXXeXXXXXXXXXXXX-907349826.gif
3104 ms
arrow.gif
3337 ms
3046 ms
xwj_heat.js
3259 ms
agp_heat.min.js
3261 ms
wp-beacon.js
3261 ms
2.gif
2285 ms
ahot.1.9
2278 ms
processUserCookie.htm
3166 ms
seed-min.js
483 ms
261 ms
module_ed.js
1638 ms
setup-shop-min.js
266 ms
posttry.js
265 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
364 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
255 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
258 ms
TB2ZXYImpXXXXayXpXXXXXXXXXX_!!672733129.jpg
3769 ms
358 ms
496 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
357 ms
footerbg.jpg
356 ms
searchbg.jpg
397 ms
attention.jpg
494 ms
bookmark.jpg
493 ms
font_1433225452_0164654.woff
305 ms
141 ms
140 ms
183 ms
base-min.js
235 ms
ie-min.js
209 ms
base-min.js
207 ms
base-min.js
230 ms
touch-min.js
206 ms
hashchange-min.js
204 ms
ie-min.js
262 ms
custom-min.js
259 ms
ajax-min.js
258 ms
anim-min.js
262 ms
base-min.js
278 ms
node-min.js
259 ms
json-min.js
288 ms
cookie-min.js
291 ms
sizzle-min.js
285 ms
webww.js
345 ms
index.js
342 ms
TB1IUtNMXXXXXXwXVXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E358b61040533a2113aeb03e64a045b80;lang%5Egbk;t%5E1460130398000
1184 ms
vdata.htm
546 ms
261 ms
TB2aYipfXXXXXXNXpXXXXXXXXXX_!!672733129.jpg
385 ms
T2Ry8xXqXbXXXXXXXX-907349826.png
127 ms
TB2L0C0mFXXXXazXpXXXXXXXXXX_!!672733129.jpg
8930 ms
TB2fs6MmXXXXXX0XXXXXXXXXXXX_!!672733129.png
251 ms
T2a2R1XD0aXXXXXXXX-1862941194.png
95 ms
es53-taming-frame-min.js
464 ms
T1kyVWFe8dXXcjfCvX-140-75.png
426 ms
T1p8v6XfJjXXXTOpDa-17-16.png
609 ms
adapter.js
399 ms
muliuserstatus.aw
4336 ms
app.gif
1675 ms
es53-guest-frame-min.js
97 ms
index.js
45 ms
index.js
191 ms
ajax
13054 ms
jump
1054 ms
add
592 ms
www.tmall.com
4269 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
72 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
375 ms
T1uUG.XjtkXXcb2gzo-77-19.gif
106 ms
ali-page-updater
1370 ms
peoleo.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
peoleo.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
peoleo.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 Peoleo.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 Peoleo.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.
peoleo.tmall.com
Open Graph description is not detected on the main page of Peoleo 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: