61.3 sec in total
958 ms
58.9 sec
1.4 sec
Welcome to pearllife.tmall.com homepage info - get ready to check Pearllife Tmall best content for China right away, or after learning these important things about pearllife.tmall.com
淘宝, 店铺, 旺铺, 珍珠生活旗舰店
Visit pearllife.tmall.comWe analyzed Pearllife.tmall.com page load time and found that the first response time was 958 ms and then it took 60.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. 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.
pearllife.tmall.com performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value11.6 s
0/100
25%
Value8.9 s
15/100
10%
Value350 ms
73/100
30%
Value0.002
100/100
15%
Value11.7 s
17/100
10%
958 ms
3310 ms
942 ms
2992 ms
6181 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Pearllife.tmall.com, 35% (36 requests) were made to G.alicdn.com and 16% (17 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Pcookie.tmall.com.
Page size can be reduced by 682.4 kB (12%)
5.6 MB
4.9 MB
In fact, the total size of Pearllife.tmall.com main page is 5.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. 65% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 122.0 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.7 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 122.0 kB or 76% of the original size.
Potential reduce by 28.2 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. Pearllife Tmall images are well optimized though.
Potential reduce by 164.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 164.2 kB or 37% of the original size.
Potential reduce by 368.0 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. Pearllife.tmall.com needs all CSS files to be minified and compressed as it can save up to 368.0 kB or 88% of the original size.
Number of requests can be reduced by 48 (56%)
85
37
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pearllife 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 31 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
pearllife.tmall.com
958 ms
pearllife.tmall.com
3310 ms
pearllife.world.tmall.com
942 ms
pearllife.world.tmall.com
2992 ms
jump
6181 ms
add
5598 ms
pearllife.world.tmall.com
1733 ms
pearllife.world.tmall.com
410 ms
pearllife.world.tmall.com
434 ms
pearllife.world.tmall.com
7865 ms
global-min.css
360 ms
seed-min.js
306 ms
global-min.js
405 ms
g.alicdn.com
369 ms
g.alicdn.com
364 ms
brandbar-min.css
377 ms
copyright-min.css
376 ms
382 ms
TB1URgAKpXXXXbIXVXXn00bFXXX.css
599 ms
TB1EEh4MpXXXXbEXXXXn00bFXXX.css
680 ms
index.js
397 ms
init-async-min.js
523 ms
155 ms
38 ms
56 ms
35 ms
36 ms
101 ms
29 ms
51 ms
31 ms
aplus_v2.js
60 ms
TB2pt0TjpXXXXX4XXXXXXXXXXXX_!!1751847701.jpg
189 ms
s.gif
6547 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
5582 ms
posttry.js
57 ms
TB2jdy8mFXXXXX.XpXXXXXXXXXX_!!1751847701.jpg
5302 ms
TB2iESnmFXXXXXIXpXXXXXXXXXX_!!1751847701.jpg
302 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
239 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
5578 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
6255 ms
getipinfo
6506 ms
counter6
16492 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
6209 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
6203 ms
shopinfo-min.css
101 ms
aplus_v2.js
185 ms
124 ms
179 ms
font_1451273740_187741.woff
6269 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
5990 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
6277 ms
blank
4817 ms
TB10QqgLVXXXXX8aXXXSutbFXXX.jpg
5958 ms
T1vEi4XnhyXXXm0Pva-454-340.png
5957 ms
agp_heat.min.js
5626 ms
wp-beacon.js
6426 ms
2.gif
7973 ms
ahot.1.9
9960 ms
812 ms
u.gif
810 ms
T156jcXXhfXXcMeXnl-22-160.gif
1122 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
784 ms
font_1433225452_0164654.woff
1071 ms
webww.js
680 ms
index.js
667 ms
674 ms
TB1lCcfHpXXXXXeXXXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E92c76867dcee6cc6982cc15ff43aa03a;lang%5Egbk;t%5E1460131229000
1798 ms
vdata.htm
631 ms
581 ms
widgetAsync.htm
1669 ms
TB2GKBKkFXXXXXsXXXXXXXXXXXX_!!1751847701.jpg
616 ms
TB2I90qkFXXXXcjXXXXXXXXXXXX_!!1751847701.jpg
509 ms
TB20lNHkFXXXXXWXXXXXXXXXXXX_!!1751847701.jpg
1762 ms
TB2TrsqmpXXXXX3XXXXXXXXXXXX_!!1751847701.jpg
1840 ms
TB2IKvwmFXXXXaFXXXXXXXXXXXX_!!1751847701.jpg
923 ms
TB20BvGmFXXXXXcXXXXXXXXXXXX_!!1751847701.jpg
619 ms
TB214C5mFXXXXaVXpXXXXXXXXXX_!!1751847701.jpg
917 ms
TB2ZEi_mFXXXXXGXpXXXXXXXXXX_!!1751847701.jpg
1518 ms
localhost.wwbizsrv.alibaba.com
144 ms
muliuserstatus.aw
6541 ms
processUserCookie.htm
18659 ms
index.js
111 ms
newinfo
8127 ms
index.js
55 ms
localhost.wwbizsrv.alibaba.com
4 ms
ww.69.2
440 ms
adapter.js
104 ms
ww.69.2
165 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
50 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
236 ms
app.gif
20155 ms
T1uUG.XjtkXXcb2gzo-77-19.gif
27 ms
jump
400 ms
add
507 ms
www.tmall.com
1778 ms
translateelement.css
30 ms
main.js
46 ms
loading.gif
595 ms
favicon.ico
450 ms
element_main.js
113 ms
translate_24dp.png
306 ms
l
153 ms
cleardot.gif
262 ms
pearllife.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
pearllife.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
pearllife.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 Pearllife.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 Pearllife.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.
pearllife.tmall.com
Open Graph description is not detected on the main page of Pearllife 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: