4.6 sec in total
266 ms
4 sec
282 ms
Welcome to runmingtea.en.alibaba.com homepage info - get ready to check Runmingtea En Alibaba best content for China right away, or after learning these important things about runmingtea.en.alibaba.com
Visit runmingtea.en.alibaba.comWe analyzed Runmingtea.en.alibaba.com page load time and found that the first response time was 266 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
runmingtea.en.alibaba.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value4.9 s
29/100
25%
Value4.6 s
70/100
10%
Value300 ms
78/100
30%
Value0
100/100
15%
Value8.2 s
41/100
10%
266 ms
112 ms
56 ms
69 ms
49 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Runmingtea.en.alibaba.com, 48% (47 requests) were made to S.alicdn.com and 13% (13 requests) were made to Gj.mmstat.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Fourier.taobao.com.
Page size can be reduced by 1.1 MB (49%)
2.2 MB
1.1 MB
In fact, the total size of Runmingtea.en.alibaba.com main page is 2.2 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 551.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 551.4 kB or 84% of the original size.
Potential reduce by 2.7 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. Runmingtea En Alibaba images are well optimized though.
Potential reduce by 278.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 278.8 kB or 26% of the original size.
Potential reduce by 273.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. Runmingtea.en.alibaba.com needs all CSS files to be minified and compressed as it can save up to 273.0 kB or 74% of the original size.
Number of requests can be reduced by 57 (64%)
89
32
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runmingtea En Alibaba. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
runmingtea.en.alibaba.com
266 ms
runmingtea.en.alibaba.com
112 ms
error404.htm
56 ms
i.alicdn.com
69 ms
error.css
49 ms
atom.js
64 ms
51 ms
202212-image-hack.bundle.js
51 ms
index.css
40 ms
index.js
44 ms
polyfill.min.js
1058 ms
index.js
58 ms
common.js
52 ms
error.js
53 ms
index.js
55 ms
56 ms
52 ms
O1CN01ghhT9i1HWsCDe82rV_!!6000000000766-2-tps-20-28.png
93 ms
queryNicheMaterial.do
42 ms
TB1hVGkvVP7gK0jSZFjXXc5aXXa-365-49.svg
26 ms
TB1mHDTXMaH3KVjSZFpXXbhKpXa-600-400.png
26 ms
TB1VtZtebH1gK0jSZFwXXc7aXXa-65-70.gif
72 ms
TB1QhYprKT2gK0jSZFvXXXnFXXa-20-20.png
76 ms
AAA=
2 ms
AAA=
2 ms
font_3610275_m1jmy24w8q.woff
45 ms
iconfont.woff
47 ms
eg.js
24 ms
sc.sc_header_footer.tbexp
9 ms
O1CN01rvHbgC1dqUsWIKhoN_!!6000000003787-0-tps-3840-80.jpg
45 ms
7.gif
5 ms
TB1SU4upFT7gK0jSZFpXXaTkpXa-440-348.png
43 ms
gatewayService
238 ms
footer.css
5 ms
font_1516980_tt14kzligp.woff
20 ms
i.alicdn.com
16 ms
package.js
35 ms
sc.sc_header_footer.schd_coms
7 ms
index.js
142 ms
async.css
20 ms
header.js
71 ms
index.js
137 ms
store-proxy.html
32 ms
sc.sc_header_footer.sc_hds
10 ms
sc.sc_header_footer.sc_hds
9 ms
sc.migrate.event
8 ms
sc.sc_header_footer.sc_hds
9 ms
need_show_cookie_setting.do
25 ms
queryIpAjax.do
95 ms
sc.error.exp
7 ms
Hb3c8f1c97fb246d69ae0f3956fbb1c34Z.jpg_220x220.jpg
58 ms
Hd802feb033ff41808fe69adcde1a9b01a.jpg_220x220.jpg
4 ms
ULB8wPVYsMnJXKJkSaelq6xUzXXat.jpg_220x220.jpg
156 ms
H8cf78b7dcd2440418d87147de7ad5cafP.jpg_220x220.jpg
20 ms
Hf7b7f5c6c91c4a44a20666f9782f39b8M.jpg_220x220.jpg
32 ms
Hb6ba4ce3de814f05a3e12d5937c38d76R.jpg_220x220.jpg
30 ms
H770eaa06bcc846a186350f91be01d341e.png_220x220.png
6 ms
Hbe530ab6cb5b460d95894b25fb261d8eP.png_220x220.png
17 ms
H9f41992d783141fbb296ebc0c856c43co.jpg_220x220.jpg
21 ms
Hf4aa9b9700954f1dae19d72999987c97k.png_220x220.png
23 ms
Hdc0e42570bd940f38cd70e0eff5f11641.jpg_220x220.jpg
22 ms
H6fde4154c07b498faf52be81129c3cebM.jpg_220x220.jpg
31 ms
Hb9ed55fca9c244c0b6a13a84c68855f1U.png_220x220.png
31 ms
H27b4234597cb41c4ab056cdba6f397dbZ.jpg_220x220.jpg
31 ms
sc.error.exp
3 ms
data
20 ms
index.js
24 ms
defer-common.js
122 ms
defer-common.css
10 ms
index.js
4 ms
awsc.js
9 ms
baxiaCommon.js
286 ms
rp
1848 ms
et_n.js
5 ms
header.json
157 ms
personRoleInfo.do
233 ms
queryRedirectUrl.json
141 ms
unread.htm
155 ms
countryCurrencyDataService
115 ms
sc.sc_header_footer.sc_hds
84 ms
countryCurrencyDataService
122 ms
categoryNaviViewService
55 ms
sc.sc_header_footer.sc_hds
16 ms
queryIpAjax.do
26 ms
queryIpAjax.do
93 ms
third-part-login.js
72 ms
69221370.png
10 ms
countryCurrencyDataService
64 ms
sc.sc_header_footer_ship_to.init
5 ms
thirdpart-login-min.js
3 ms
xman_config_sc.js
179 ms
iconfont.woff
32 ms
queryIpAjax.do
79 ms
O1CN01wlImAt1sGy58OFEjA_!!6000000005740-2-tps-79-79.png
5 ms
TB1gBp7SSzqK1RjSZPcXXbTepXa-40-40.png
23 ms
TB1mhSNafc3T1VjSZPfXXcWHXXa-40-32.png
15 ms
TB196hmTbPpK1RjSZFFXXa5PpXa-40-40.png
15 ms
TB1C7nRNFYqK1RjSZLeXXbXppXa-66-40.svg
16 ms
runmingtea.en.alibaba.com accessibility score
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
runmingtea.en.alibaba.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
runmingtea.en.alibaba.com SEO score
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
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runmingtea.en.alibaba.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Runmingtea.en.alibaba.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
runmingtea.en.alibaba.com
Open Graph description is not detected on the main page of Runmingtea En Alibaba. 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: