13.8 sec in total
560 ms
12.4 sec
839 ms
Visit lekani.aliexpress.com now to see the best up-to-date LEKANI Ali Express content for Brazil and also check out these interesting facts you probably never knew about lekani.aliexpress.com
Discover the wide range of from AliExpress Top Seller LEKANI Official Store.Enjoy ✓Free Shipping Worldwide! ✓Limited Time Sale ✓Easy Return.
Visit lekani.aliexpress.comWe analyzed Lekani.aliexpress.com page load time and found that the first response time was 560 ms and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lekani.aliexpress.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value8.8 s
1/100
25%
Value5.5 s
55/100
10%
Value820 ms
35/100
30%
Value0
100/100
15%
Value8.7 s
36/100
10%
560 ms
328 ms
509 ms
35 ms
151 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Lekani.aliexpress.com, 30% (36 requests) were made to Assets.alicdn.com and 21% (26 requests) were made to Ae01.alicdn.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Assets.alicdn.com.
Page size can be reduced by 2.9 MB (66%)
4.3 MB
1.5 MB
In fact, the total size of Lekani.aliexpress.com main page is 4.3 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. 70% of websites need less resources to load. Javascripts take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 233.9 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 233.9 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, LEKANI 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.7 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.7 MB or 58% 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. Lekani.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 80 (71%)
113
33
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LEKANI 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 56 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lekani.aliexpress.com
560 ms
1101385898
328 ms
509 ms
next.min.css
35 ms
index.css
151 ms
index.js
160 ms
index.js
166 ms
index.js
49 ms
ae-header.css
159 ms
ae-header.js
164 ms
index.css
160 ms
index.js
164 ms
_cross_page_loader_.js
63 ms
register.js
13 ms
15 ms
index.js
4 ms
index.web.cmd.js
9 ms
15 ms
index.web.js
15 ms
index.web.js
15 ms
index.web.js
16 ms
index.web.js
22 ms
index.web.js
23 ms
index.web.js
18 ms
index.web.js
17 ms
index.web.js
33 ms
index.web.js
18 ms
index.web.js
21 ms
index.web.js
20 ms
index.web.js
22 ms
index.web.js
24 ms
index.web.js
24 ms
index.web.js
27 ms
index.web.js
27 ms
index.web.js
31 ms
gep-tracker.js
26 ms
gep-sdk.js
29 ms
10x10.png
106 ms
240x168.png
107 ms
65x70.gif
63 ms
20x20.png
104 ms
45 ms
41 ms
epssw.js
60 ms
11 ms
eg.js
1645 ms
et_n.js
737 ms
index.js
139 ms
rp
1502 ms
wcfg.json
1500 ms
138 ms
240x168.png
77 ms
renderPageData.htm
334 ms
mem8YaGs126MiZpBA-U1UQ.woff
5186 ms
open-sans.006320aa.woff
4914 ms
mem5YaGs126MiZpBA-UNirk-Vg.woff
4916 ms
mem5YaGs126MiZpBA-UN7rg-Vg.woff
4912 ms
H907757fdad184e31a1b58bd6507666deo.png
95 ms
g.gif
4825 ms
H6dea52a7c0df4bd4846cec6add0060acM.png
71 ms
40x40.png
4823 ms
20x20.png
68 ms
info
5078 ms
aes.1.1
5017 ms
execute
4375 ms
execute
3733 ms
3682 ms
execute
3118 ms
execute
2473 ms
execute
1846 ms
execute
1195 ms
execute
632 ms
363 ms
arrow-left.acf07a9d.png
305 ms
96x96.png
305 ms
Sdefcfef791df40b08694d22ed99945f0b.png
355 ms
S0cbfe6b5c56345648d665f187cc41f466.png
783 ms
S4f83fabda1de44da92a060bbb19805d4u.png
776 ms
S23b110a9bef64d5ea0c3219d4761d18dF.png
782 ms
Sdd06d14ae05a49619b001de32199aa9dG.png
783 ms
Sd633c04b876e433aa516a0d68df7430dx.png
776 ms
Sf8676f2acf5144749c9672e2598ff0f4l.png
777 ms
S7b09c4fdec0f4455b954ec2883440400N.png
1102 ms
48x48.png
780 ms
48x48.png
778 ms
H436514e3cf4a4b5b88acec4ba7aa545f9.jpg
840 ms
S8dba9169f83b482c98580a5e19da0858h.png
1103 ms
Scb162c96c0ed4e0fb1920617852878133.png
1102 ms
Sa7e5b98943d54add9a4079013044ca5bn.png
2781 ms
HTB1WkShPY2pK1RjSZFs761NlXXay.png
784 ms
HTB1QHqMP4naK1RjSZFt762C2VXa1.png
784 ms
app.gif
341 ms
eg.js
500 ms
aes.1.1
491 ms
ae.pc_ctr.statweb_ae_ctr
537 ms
index.web.js
28 ms
baxiaJsonpHandler.js
7 ms
punish:resource:template:AESpace:default_184083.html
2413 ms
330 ms
aes.1.1
266 ms
ae.pc_ctr.statweb_ae_ctr
1673 ms
1417 ms
1157 ms
860 ms
579 ms
270 ms
264 ms
flexible.js
261 ms
qrcode.min.js
263 ms
main.css
267 ms
punishpage.min.js
270 ms
267 ms
aes.1.1
496 ms
aes.1.1
465 ms
aes.1.1
238 ms
fsp.1.1
867 ms
O1CN01oSZaoy1rcfT5pA6JR_!!6000000005652-2-tps-498-120.png
143 ms
index.js
51 ms
O1CN01uX800r1KcmF5qDeNd_!!6000000001185-2-tps-276-284.png
102 ms
fsp.1.1
218 ms
aes.1.1
241 ms
lekani.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
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.
lekani.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
lekani.aliexpress.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
![]()
N/A
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lekani.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 Lekani.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.
lekani.aliexpress.com
Open Graph description is not detected on the main page of LEKANI 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: