Tools & Wizards About Us
keypleasure.tmall.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

keypleasure.tmall.com

Page Load Speed

56.5 sec in total

First Response

1.9 sec

Resources Loaded

53.4 sec

Page Rendered

1.2 sec

keypleasure.tmall.com screenshot

About Website

Visit keypleasure.tmall.com now to see the best up-to-date Keypleasure Tmall content for China and also check out these interesting facts you probably never knew about keypleasure.tmall.com

淘宝, 店铺, 旺铺, key官方旗舰店

Visit keypleasure.tmall.com

Key Findings

We analyzed Keypleasure.tmall.com page load time and found that the first response time was 1.9 sec and then it took 54.6 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.

Performance Metrics

keypleasure.tmall.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

keypleasure.tmall.com

1943 ms

keypleasure.tmall.com

3896 ms

keypleasure.world.tmall.com

3957 ms

keypleasure.world.tmall.com

2968 ms

jump

11324 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Keypleasure.tmall.com, 47% (51 requests) were made to G.alicdn.com and 15% (16 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Gskip.taobao.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 729.6 kB (46%)

Content Size

1.6 MB

After Optimization

847.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Keypleasure.tmall.com main page is 1.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. 45% of websites need less resources to load. Javascripts take 482.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 127.2 kB

  • Original 168.8 kB
  • After minification 148.1 kB
  • After compression 41.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 20.8 kB, which is 12% 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 127.2 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 7.2 kB

  • Original 455.1 kB
  • After minification 447.9 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. Keypleasure Tmall images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 175.9 kB

  • Original 482.0 kB
  • After minification 481.8 kB
  • After compression 306.1 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 175.9 kB or 36% of the original size.

CSS Optimization

-89%

Potential reduce by 419.3 kB

  • Original 471.6 kB
  • After minification 448.3 kB
  • After compression 52.3 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. Keypleasure.tmall.com needs all CSS files to be minified and compressed as it can save up to 419.3 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (75%)

Requests Now

91

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Keypleasure 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 47 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

keypleasure.tmall.com

keypleasure.tmall.com

1943 ms

keypleasure.tmall.com

keypleasure.tmall.com

3896 ms

keypleasure.world.tmall.com

keypleasure.world.tmall.com

3957 ms

keypleasure.world.tmall.com

keypleasure.world.tmall.com

2968 ms

jump

jump

11324 ms

add

add

3524 ms

keypleasure.world.tmall.com

keypleasure.world.tmall.com

454 ms

keypleasure.world.tmall.com

keypleasure.world.tmall.com

419 ms

keypleasure.world.tmall.com

keypleasure.world.tmall.com

468 ms

keypleasure.world.tmall.com

keypleasure.world.tmall.com

5165 ms

global-min.css

global-min.css

460 ms

seed-min.js

seed-min.js

695 ms

global-min.js

global-min.js

912 ms

g.alicdn.com

g.alicdn.com

457 ms

g.alicdn.com

g.alicdn.com

470 ms

brandbar-min.css

brandbar-min.css

471 ms

copyright-min.css

copyright-min.css

516 ms

688 ms

TB1AmsrHpXXXXXkXFXXn00bFXXX.css

TB1AmsrHpXXXXXkXFXXn00bFXXX.css

1015 ms

default_ed.css

default_ed.css

639 ms

index.js

index.js

526 ms

init-async-min.js

init-async-min.js

526 ms

318 ms

103 ms

200 ms

126 ms

200 ms

85 ms

72 ms

59 ms

68 ms

aplus_v2.js

aplus_v2.js

48 ms

TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png

TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png

2492 ms

getipinfo

getipinfo

2502 ms

counter6

counter6

4183 ms

TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png

TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png

2477 ms

TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png

TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png

2465 ms

font_1451273740_187741.woff

font_1451273740_187741.woff

2696 ms

aplus_v2.js

aplus_v2.js

188 ms

agp_heat.min.js

agp_heat.min.js

2185 ms

wp-beacon.js

wp-beacon.js

2391 ms

2.gif

2.gif

3550 ms

ahot.1.9

ahot.1.9

3972 ms

processUserCookie.htm

processUserCookie.htm

19615 ms

shopinfo-min.css

shopinfo-min.css

52 ms

s.gif

s.gif

34 ms

TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png

TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png

33 ms

TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png

TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png

48 ms

seed-min.js

seed-min.js

88 ms

63 ms

module_ed.js

module_ed.js

583 ms

setup-shop-min.js

setup-shop-min.js

52 ms

posttry.js

posttry.js

62 ms

TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png

TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png

159 ms

50 ms

114 ms

TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png

TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png

59 ms

TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png

TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png

101 ms

blank

blank

10 ms

TB1yO6xKFXXXXaRXFXXSutbFXXX.jpg

TB1yO6xKFXXXXaRXFXXSutbFXXX.jpg

80 ms

TB2x_nnhFXXXXcZXXXXXXXXXXXX_!!2090362539.gif

TB2x_nnhFXXXXcZXXXXXXXXXXXX_!!2090362539.gif

103 ms

t.gif

t.gif

243 ms

btn1.jpg

btn1.jpg

243 ms

u.gif

u.gif

159 ms

T156jcXXhfXXcMeXnl-22-160.gif

T156jcXXhfXXcMeXnl-22-160.gif

79 ms

65 ms

font_1433225452_0164654.woff

font_1433225452_0164654.woff

75 ms

base-min.js

base-min.js

109 ms

base-min.js

base-min.js

109 ms

base-min.js

base-min.js

109 ms

touch-min.js

touch-min.js

106 ms

focusin-min.js

focusin-min.js

93 ms

custom-min.js

custom-min.js

104 ms

ajax-min.js

ajax-min.js

135 ms

anim-min.js

anim-min.js

132 ms

base-min.js

base-min.js

124 ms

node-min.js

node-min.js

128 ms

json-min.js

json-min.js

135 ms

cookie-min.js

cookie-min.js

385 ms

sizzle-min.js

sizzle-min.js

152 ms

webww.js

webww.js

161 ms

index.js

index.js

189 ms

TB1l4zCLFXXXXXaXXXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5Ef8aed61b03a32a9bb72f1ce36d4cad74;lang%5Egbk;t%5E1460132402000

TB1l4zCLFXXXXXaXXXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5Ef8aed61b03a32a9bb72f1ce36d4cad74;lang%5Egbk;t%5E1460132402000

836 ms

TB2ooRTkFXXXXbZXpXXXXXXXXXX_!!2090362539.jpg

TB2ooRTkFXXXXbZXpXXXXXXXXXX_!!2090362539.jpg

120 ms

vdata.htm

vdata.htm

507 ms

100 ms

TB2nQN7kFXXXXXuXpXXXXXXXXXX_!!2090362539.jpg

TB2nQN7kFXXXXXuXpXXXXXXXXXX_!!2090362539.jpg

303 ms

TB29pJ0kFXXXXbeXpXXXXXXXXXX_!!2090362539.jpg

TB29pJ0kFXXXXbeXpXXXXXXXXXX_!!2090362539.jpg

188 ms

TB2fa81kFXXXXaaXpXXXXXXXXXX_!!2090362539.jpg

TB2fa81kFXXXXaaXpXXXXXXXXXX_!!2090362539.jpg

593 ms

TB2T107kFXXXXXDXpXXXXXXXXXX_!!2090362539.jpg

TB2T107kFXXXXXDXpXXXXXXXXXX_!!2090362539.jpg

127 ms

TB2jKqekFXXXXceXXXXXXXXXXXX_!!2090362539.jpg

TB2jKqekFXXXXceXXXXXXXXXXXX_!!2090362539.jpg

121 ms

TB2.I1tkFXXXXaeXXXXXXXXXXXX_!!2090362539.jpg

TB2.I1tkFXXXXaeXXXXXXXXXXXX_!!2090362539.jpg

127 ms

localhost.wwbizsrv.alibaba.com

localhost.wwbizsrv.alibaba.com

19 ms

muliuserstatus.aw

muliuserstatus.aw

4421 ms

es53-taming-frame-min.js

es53-taming-frame-min.js

433 ms

index.js

index.js

47 ms

es53-guest-frame-min.js

es53-guest-frame-min.js

91 ms

index.js

index.js

179 ms

ajax

ajax

3814 ms

localhost.wwbizsrv.alibaba.com

localhost.wwbizsrv.alibaba.com

4 ms

ww.69.2

ww.69.2

2089 ms

app.gif

app.gif

9677 ms

adapter.js

adapter.js

74 ms

ww.69.2

ww.69.2

699 ms

TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif

TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif

75 ms

T1YYg5FdhcXXc1Y.Af-102-114.gif

T1YYg5FdhcXXc1Y.Af-102-114.gif

400 ms

T1FXHXXahjXXXAK3zo-77-18.gif

T1FXHXXahjXXXAK3zo-77-18.gif

53 ms

T1FXHXXahjXXXAK3zo-77-18.gif

T1FXHXXahjXXXAK3zo-77-18.gif

31 ms

Accessibility Review

keypleasure.tmall.com accessibility score

67

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

keypleasure.tmall.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

keypleasure.tmall.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keypleasure.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 Keypleasure.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.

Social Sharing Optimization

keypleasure.tmall.com

Open Graph description is not detected on the main page of Keypleasure 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: