23.6 sec in total
490 ms
21.4 sec
1.7 sec
Welcome to yunshan.aliexpress.com homepage info - get ready to check Yunshan Ali Express best content for Brazil right away, or after learning these important things about yunshan.aliexpress.com
Discover the wide range of from AliExpress Top Seller LOSSKY Official Store.Enjoy ✓Free Shipping Worldwide! ✓Limited Time Sale ✓Easy Return.
Visit yunshan.aliexpress.comWe analyzed Yunshan.aliexpress.com page load time and found that the first response time was 490 ms and then it took 23.1 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.
yunshan.aliexpress.com performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value15.3 s
0/100
25%
Value25.4 s
0/100
10%
Value5,900 ms
0/100
30%
Value1.302
1/100
15%
Value32.0 s
0/100
10%
490 ms
284 ms
347 ms
39 ms
56 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Yunshan.aliexpress.com, 27% (31 requests) were made to Ae01.alicdn.com and 26% (30 requests) were made to Assets.alicdn.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Fourier.taobao.com.
Page size can be reduced by 2.6 MB (66%)
4.0 MB
1.4 MB
In fact, the total size of Yunshan.aliexpress.com main page is 4.0 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 2.5 MB which makes up the majority of the site volume.
Potential reduce by 245.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. 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 245.0 kB or 76% of the original size.
Potential reduce by 7.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. Obviously, Yunshan Ali Express needs image optimization as it can save up to 7.7 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.4 MB
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 1.4 MB or 56% of the original size.
Potential reduce by 962.6 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. Yunshan.aliexpress.com needs all CSS files to be minified and compressed as it can save up to 962.6 kB or 86% of the original size.
Number of requests can be reduced by 73 (68%)
107
34
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yunshan Ali Express. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
yunshan.aliexpress.com
490 ms
1100537426
284 ms
347 ms
next.min.css
39 ms
index.css
56 ms
index.js
65 ms
index.js
56 ms
index.js
52 ms
ae-header.css
59 ms
ae-header.js
50 ms
index.css
44 ms
index.js
50 ms
_cross_page_loader_.js
41 ms
register.js
14 ms
8 ms
index.js
5 ms
index.web.cmd.js
9 ms
14 ms
index.web.js
12 ms
index.web.js
12 ms
index.web.js
13 ms
index.web.js
13 ms
index.web.js
15 ms
index.web.js
17 ms
index.web.js
20 ms
index.web.js
18 ms
index.web.js
17 ms
index.web.js
18 ms
index.web.js
20 ms
index.web.js
20 ms
index.web.js
20 ms
index.web.js
22 ms
gep-tracker.js
20 ms
gep-sdk.js
24 ms
10x10.png
1477 ms
240x168.png
1488 ms
65x70.gif
1485 ms
20x20.png
1484 ms
5 ms
6 ms
epssw.js
22 ms
18 ms
et_n.js
641 ms
index.js
34 ms
rp
19911 ms
wcfg.json
6211 ms
33 ms
eg.js
5578 ms
renderPageData.htm
564 ms
mem8YaGs126MiZpBA-U1UQ.woff
382 ms
open-sans.006320aa.woff
360 ms
mem5YaGs126MiZpBA-UNirk-Vg.woff
382 ms
mem5YaGs126MiZpBA-UN7rg-Vg.woff
381 ms
H907757fdad184e31a1b58bd6507666deo.png
382 ms
H6dea52a7c0df4bd4846cec6add0060acM.png
383 ms
40x40.png
389 ms
aes.1.1
4479 ms
info
27 ms
g.gif
4677 ms
96x96.png
3669 ms
arrow-left.acf07a9d.png
3926 ms
execute
3306 ms
execute
2775 ms
execute
2263 ms
execute
1724 ms
execute
1191 ms
execute
623 ms
364 ms
Hb4f2fc43d9614698925ea14e962e2f6cW.png
871 ms
S8e1dd157ee6b4c24ac549e608c1fd686c.png
1650 ms
S7933d156ee8944f6856303383ab5926e1.png
871 ms
S15550e797d384a60891fae6b5f81ec905.png
1651 ms
Sc31112ee15024b7cb6603e14312fc69a9.png
1649 ms
S0484bd6049c2438e8a22576781bdd9b4g.png
1937 ms
S224ba1cdd87a4af18ea2ef88691a1c8bq.png
1912 ms
Sb00372abf1de4c2c8cb6111d4e7e097es.png
1923 ms
S0a0def3fc3d14816a40e92cf71182736v.png
1910 ms
S076001bb6cfa4d89821a4011ce6c6545n.png
1910 ms
S5ccc32ddeda04c4daa9a4438fe48a6f8h.png
1908 ms
S32bf64e26355433185dacfe4dcfcd50eZ.png
2052 ms
Sd777d60f2fef42d8a7c5bccc0f12d8e0y.png
1923 ms
HTB1gtHRRhjaK1RjSZFAq6zdLFXae.jpg
2581 ms
48x48.png
1920 ms
48x48.png
1930 ms
Sd683e7d2fba049eab8755fab90c72d4f7.png
2159 ms
Sba3e788ec8ab43788f449c58a832d4f3K.jpg
2306 ms
S501fba8f68754379b702f36e477e99946.jpg
2499 ms
S3f3e41a1883e41378570ce5cf2454d233.jpg
2397 ms
S13435f4d2e2e43c2acb7b65755e490caj.jpg
2432 ms
HTB1WkShPY2pK1RjSZFs761NlXXay.png
2163 ms
HTB1QHqMP4naK1RjSZFt762C2VXa1.png
2180 ms
eg.js
618 ms
aes.1.1
1385 ms
ae.pc_ctr.statweb_ae_ctr
1614 ms
baxiaJsonpHandler.js
7 ms
punish:resource:template:AESpace:default_184083.html
1584 ms
273 ms
aes.1.1
1286 ms
app.gif
1037 ms
780 ms
578 ms
312 ms
flexible.js
22 ms
qrcode.min.js
24 ms
main.css
27 ms
punishpage.min.js
31 ms
28 ms
aes.1.1
255 ms
aes.1.1
256 ms
fsp.1.1
966 ms
aes.1.1
259 ms
aes.1.1
254 ms
O1CN01oSZaoy1rcfT5pA6JR_!!6000000005652-2-tps-498-120.png
130 ms
O1CN01uX800r1KcmF5qDeNd_!!6000000001185-2-tps-276-284.png
109 ms
fsp.1.1
218 ms
yunshan.aliexpress.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yunshan.aliexpress.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
Detected JavaScript libraries
Page has valid source maps
yunshan.aliexpress.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 doesn't use legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yunshan.aliexpress.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 Yunshan.aliexpress.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.
yunshan.aliexpress.com
Open Graph description is not detected on the main page of Yunshan Ali Express. 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: