6.3 sec in total
1.3 sec
4.8 sec
291 ms
Visit aofeiqike.en.alibaba.com now to see the best up-to-date Aofeiqike En Alibaba content for China and also check out these interesting facts you probably never knew about aofeiqike.en.alibaba.com
Visit aofeiqike.en.alibaba.comWe analyzed Aofeiqike.en.alibaba.com page load time and found that the first response time was 1.3 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
aofeiqike.en.alibaba.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value5.0 s
26/100
25%
Value5.1 s
62/100
10%
Value450 ms
63/100
30%
Value0.118
85/100
15%
Value8.2 s
41/100
10%
1285 ms
61 ms
581 ms
318 ms
264 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Aofeiqike.en.alibaba.com, 47% (45 requests) were made to S.alicdn.com and 14% (13 requests) were made to Gj.mmstat.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Fourier.taobao.com.
Page size can be reduced by 1.1 MB (50%)
2.2 MB
1.1 MB
In fact, the total size of Aofeiqike.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 550.8 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 550.8 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. Aofeiqike 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. Aofeiqike.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 (66%)
87
30
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aofeiqike 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.
aofeiqike.en.alibaba.com
1285 ms
aofeiqike.en.alibaba.com
61 ms
error404.htm
581 ms
i.alicdn.com
318 ms
error.css
264 ms
atom.js
271 ms
259 ms
202212-image-hack.bundle.js
258 ms
index.css
90 ms
index.js
93 ms
polyfill.min.js
296 ms
index.js
264 ms
common.js
262 ms
error.js
263 ms
index.js
268 ms
266 ms
TB1VtZtebH1gK0jSZFwXXc7aXXa-65-70.gif
142 ms
TB1QhYprKT2gK0jSZFvXXXnFXXa-20-20.png
153 ms
13 ms
TB1hVGkvVP7gK0jSZFjXXc5aXXa-365-49.svg
46 ms
TB1mHDTXMaH3KVjSZFpXXbhKpXa-600-400.png
45 ms
eg.js
512 ms
O1CN01ghhT9i1HWsCDe82rV_!!6000000000766-2-tps-20-28.png
108 ms
AAA=
24 ms
AAA=
24 ms
font_3610275_m1jmy24w8q.woff
69 ms
queryNicheMaterial.do
506 ms
sc.enlogin.page
484 ms
iconfont.woff
44 ms
gatewayService
509 ms
footer.css
79 ms
TB1SU4upFT7gK0jSZFpXXaTkpXa-440-348.png
9 ms
font_1516980_tt14kzligp.woff
23 ms
i.alicdn.com
21 ms
package.js
12 ms
index.js
38 ms
async.css
27 ms
header.js
36 ms
sc.sc_header_footer.schd_coms
321 ms
index.js
133 ms
store-proxy.html
39 ms
need_show_cookie_setting.do
389 ms
sc.sc_header_footer.sc_hds
201 ms
sc.sc_header_footer.sc_hds
204 ms
sc.migrate.event
204 ms
sc.sc_header_footer.sc_hds
208 ms
queryIpAjax.do
82 ms
7.gif
4 ms
sc.error.exp
8 ms
H522339ab58e246ea8d965fe2ff46762eK.jpg_220x220.jpg
6 ms
H0a590dc44671474fb314e01252b1a7487.jpg_220x220.jpg
5 ms
H0ea4c9a857e7499889cc67b8b6a821aer.png_220x220.png
9 ms
Hf7b7f5c6c91c4a44a20666f9782f39b8M.jpg_220x220.jpg
118 ms
Hb6ba4ce3de814f05a3e12d5937c38d76R.jpg_220x220.jpg
7 ms
H27b4234597cb41c4ab056cdba6f397dbZ.jpg_220x220.jpg
4 ms
H770eaa06bcc846a186350f91be01d341e.png_220x220.png
9 ms
Hbe530ab6cb5b460d95894b25fb261d8eP.png_220x220.png
12 ms
Hf751249b26d2431f9d8543de81cac157t.jpg_220x220.jpg
10 ms
Hdc0e42570bd940f38cd70e0eff5f11641.jpg_220x220.jpg
9 ms
H42871cf49c4e47b6be5ea31d7665a54bb.jpg_220x220.jpg
24 ms
H52ca684922384ce2bd571203a66f8afb8.jpg_220x220.jpg
13 ms
H3456567a223b40b79c23e427aa44f441O.jpg_220x220.jpg
26 ms
sc.error.exp
7 ms
data
24 ms
defer-common.js
23 ms
defer-common.css
22 ms
index.js
156 ms
header.json
103 ms
personRoleInfo.do
255 ms
queryRedirectUrl.json
101 ms
unread.htm
306 ms
countryCurrencyDataService
269 ms
sc.sc_header_footer.sc_hds
58 ms
countryCurrencyDataService
299 ms
categoryNaviViewService
231 ms
sc.sc_header_footer.sc_hds
16 ms
index.js
6 ms
awsc.js
32 ms
baxiaCommon.js
42 ms
rp
1336 ms
queryIpAjax.do
28 ms
queryIpAjax.do
150 ms
third-part-login.js
18 ms
et_f.js
12 ms
thirdpart-login-min.js
143 ms
queryIpAjax.do
97 ms
xman_config_sc.js
370 ms
iconfont.woff
6 ms
69221370.png
32 ms
countryCurrencyDataService
48 ms
sc.sc_header_footer_ship_to.init
11 ms
O1CN01wlImAt1sGy58OFEjA_!!6000000005740-2-tps-79-79.png
6 ms
TB1gBp7SSzqK1RjSZPcXXbTepXa-40-40.png
11 ms
TB1mhSNafc3T1VjSZPfXXcWHXXa-40-32.png
10 ms
TB196hmTbPpK1RjSZFFXXa5PpXa-40-40.png
10 ms
TB1C7nRNFYqK1RjSZLeXXbXppXa-66-40.svg
36 ms
aofeiqike.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
aofeiqike.en.alibaba.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
aofeiqike.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 Aofeiqike.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 Aofeiqike.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.
aofeiqike.en.alibaba.com
Open Graph description is not detected on the main page of Aofeiqike 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: