54.3 sec in total
4 sec
49 sec
1.3 sec
Click here to check amazing Otterbox Tmall content for China. Otherwise, check out these important facts you probably never knew about otterbox.tmall.com
淘宝, 店铺, 旺铺, otterbox旗舰店
Visit otterbox.tmall.comWe analyzed Otterbox.tmall.com page load time and found that the first response time was 4 sec and then it took 50.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. 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.
otterbox.tmall.com performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value11.0 s
0/100
25%
Value8.5 s
17/100
10%
Value260 ms
83/100
30%
Value0.002
100/100
15%
Value11.1 s
20/100
10%
4006 ms
1691 ms
2192 ms
6725 ms
2935 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Otterbox.tmall.com, 33% (34 requests) were made to G.alicdn.com and 27% (28 requests) were made to Gdp.alicdn.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Gskip.taobao.com.
Page size can be reduced by 403.7 kB (19%)
2.1 MB
1.7 MB
In fact, the total size of Otterbox.tmall.com main page is 2.1 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 165.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 45.4 kB, which is 22% 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 165.5 kB or 80% of the original size.
Potential reduce by 35.3 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. Otterbox Tmall images are well optimized though.
Potential reduce by 148.0 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 148.0 kB or 44% of the original size.
Potential reduce by 54.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. Otterbox.tmall.com needs all CSS files to be minified and compressed as it can save up to 54.9 kB or 72% of the original size.
Number of requests can be reduced by 48 (56%)
86
38
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otterbox 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.
otterbox.tmall.com
4006 ms
otterbox.tmall.com
1691 ms
otterbox.world.tmall.com
2192 ms
otterbox.world.tmall.com
6725 ms
jump
2935 ms
add
2080 ms
otterbox.world.tmall.com
2159 ms
otterbox.world.tmall.com
477 ms
otterbox.world.tmall.com
520 ms
otterbox.world.tmall.com
6468 ms
global-min.css
449 ms
seed-min.js
593 ms
global-min.js
885 ms
g.alicdn.com
430 ms
g.alicdn.com
429 ms
brandbar-min.css
429 ms
copyright-min.css
501 ms
713 ms
g.alicdn.com
500 ms
TB14URSMpXXXXXPXFXXn00bFXXX.css
614 ms
index.js
514 ms
init-async-min.js
579 ms
jstracker.2
766 ms
TB2mH.YiVXXXXbPXpXXXXXXXXXX_!!1891934930.jpg
161 ms
343 ms
106 ms
524 ms
aplus_v2.js
124 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
541 ms
getipinfo
4523 ms
counter6
7265 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
519 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
541 ms
shopinfo-min.css
126 ms
146 ms
324 ms
font_1451273740_187741.woff
576 ms
aplus_v2.js
646 ms
TB1kIX_GXXXXXahXVXXAYQ4SFXX-408-114.png
361 ms
TB11O5QFVXXXXXgXpXXjI5j1VXX-186-127.png
385 ms
276 ms
65 ms
agp_heat.min.js
3706 ms
wp-beacon.js
3841 ms
2.gif
5587 ms
ahot.1.9
5784 ms
218 ms
137 ms
blank
56 ms
TB1gU6EJFXXXXXEXFXXSutbFXXX.jpg
196 ms
T1vEi4XnhyXXXm0Pva-454-340.png
95 ms
TB2BsQAfpXXXXb2XpXXXXXXXXXX_!!1891934930.jpg
171 ms
s.gif
169 ms
T1GjdOXA8XXXbHTkoN-122-235.png
198 ms
T156jcXXhfXXcMeXnl-22-160.gif
56 ms
processUserCookie.htm
20074 ms
TB2UAK.lpXXXXb8XpXXXXXXXXXX_!!1891934930.png
173 ms
TB2JPjwlpXXXXXyXpXXXXXXXXXX_!!1891934930.jpg
154 ms
TB2QYcwlFXXXXXWXXXXXXXXXXXX_!!1891934930.jpg
132 ms
TB2mCEmlFXXXXcvXXXXXXXXXXXX_!!1891934930.jpg
188 ms
TB2.fn5lFXXXXbpXpXXXXXXXXXX_!!1891934930.jpg
189 ms
58 ms
61 ms
61 ms
TB2j2UhlFXXXXXbXpXXXXXXXXXX_!!1891934930.jpg
80 ms
TB2MqAAlFXXXXaiXXXXXXXXXXXX_!!1891934930.jpg
150 ms
TB2UVAclFXXXXX3XpXXXXXXXXXX_!!1891934930.jpg
148 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
65 ms
posttry.js
64 ms
T1cKm3XkRpXXXXXXXX-48-48.gif
60 ms
TB1ZtqIGVXXXXX_XFXXW7_A_FXX-113-21.png
59 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
144 ms
font_1433225452_0164654.woff
124 ms
webww.js
114 ms
index.js
116 ms
104 ms
TB1keDeLFXXXXcsXVXXUxnn4FXX.groupmember%7Cvar%5EgroupMember;sign%5E94624482b392bd34c0edbc2ac5ac6533;lang%5Egbk;t%5E1460136567000
542 ms
TB26WjGlpXXXXayXXXXXXXXXXXX_!!1891934930.png
103 ms
vdata.htm
443 ms
TB2UlXqlFXXXXaOXXXXXXXXXXXX_!!1891934930.jpg
260 ms
TB2WWYClpXXXXbbXXXXXXXXXXXX_!!1891934930.jpg
524 ms
TB2YHOelVXXXXaqXpXXXXXXXXXX_!!1891934930.jpg
719 ms
TB2Io_wlpXXXXb9XXXXXXXXXXXX_!!1891934930.png
116 ms
TB2flv0lFXXXXbCXpXXXXXXXXXX_!!1891934930.png
112 ms
TB2cLoolFXXXXb7XXXXXXXXXXXX_!!1891934930.png
104 ms
TB251oXlFXXXXa0XpXXXXXXXXXX_!!1891934930.png
162 ms
TB2inwslFXXXXbOXXXXXXXXXXXX_!!1891934930.png
209 ms
TB2q_EXlFXXXXXeXpXXXXXXXXXX_!!1891934930.png
402 ms
localhost.wwbizsrv.alibaba.com
47 ms
muliuserstatus.aw
2470 ms
TB23H.ilFXXXXXtXpXXXXXXXXXX_!!1891934930.png
190 ms
TB2T5D3lFXXXXb3XpXXXXXXXXXX_!!1891934930.jpg
309 ms
index.js
56 ms
index.js
59 ms
localhost.wwbizsrv.alibaba.com
1 ms
ww.69.2
390 ms
TB1cut8FVXXXXafXXXXOcKP.FXX-130-60.gif
97 ms
T1YYg5FdhcXXc1Y.Af-102-114.gif
807 ms
adapter.js
66 ms
ww.69.2
111 ms
app.gif
4879 ms
T1FXHXXahjXXXAK3zo-77-18.gif
52 ms
TB2zlztlpXXXXcvXXXXXXXXXXXX_!!1891934930.jpg
71 ms
otterbox.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
otterbox.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
otterbox.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 Otterbox.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 Otterbox.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.
otterbox.tmall.com
Open Graph description is not detected on the main page of Otterbox 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: