20.1 sec in total
937 ms
17 sec
2.1 sec
Welcome to vivilady.aliexpress.com homepage info - get ready to check VIVILADY Ali Express best content for Brazil right away, or after learning these important things about vivilady.aliexpress.com
Discover the wide range of from AliExpress Top Seller VIVILADY Official Store.Enjoy ✓Free Shipping Worldwide! ✓Limited Time Sale ✓Easy Return.
Visit vivilady.aliexpress.comWe analyzed Vivilady.aliexpress.com page load time and found that the first response time was 937 ms and then it took 19.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
vivilady.aliexpress.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value13.4 s
0/100
25%
Value14.2 s
1/100
10%
Value370 ms
70/100
30%
Value0.621
10/100
15%
Value14.4 s
9/100
10%
937 ms
419 ms
471 ms
91 ms
270 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 Vivilady.aliexpress.com, 33% (40 requests) were made to Assets.alicdn.com and 28% (34 requests) were made to Ae01.alicdn.com. The less responsive or slowest element that took the longest time to load (6.5 sec) relates to the external source Img.alicdn.com.
Page size can be reduced by 1.6 MB (54%)
3.0 MB
1.4 MB
In fact, the total size of Vivilady.aliexpress.com main page is 3.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.1 MB which makes up the majority of the site volume.
Potential reduce by 267.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 267.0 kB or 78% 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, VIVILADY Ali Express needs image optimization as it can save up to 7.7 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 990.7 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 990.7 kB or 47% of the original size.
Potential reduce by 316.3 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. Vivilady.aliexpress.com needs all CSS files to be minified and compressed as it can save up to 316.3 kB or 68% of the original size.
Number of requests can be reduced by 78 (69%)
113
35
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VIVILADY 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 53 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
vivilady.aliexpress.com
937 ms
1100438753
419 ms
471 ms
next.min.css
91 ms
index.css
270 ms
index.js
271 ms
index.js
271 ms
index.js
270 ms
ae-header.css
269 ms
ae-header.js
271 ms
index.css
276 ms
index.js
277 ms
_cross_page_loader_.js
272 ms
register.js
121 ms
125 ms
index.js
7 ms
index.web.cmd.js
125 ms
130 ms
index.web.js
160 ms
index.web.js
128 ms
index.web.js
128 ms
index.web.js
127 ms
index.web.js
166 ms
index.web.js
130 ms
index.web.js
131 ms
index.web.js
134 ms
index.web.js
202 ms
index.web.js
166 ms
index.web.js
133 ms
index.web.js
135 ms
gep-tracker.js
175 ms
gep-sdk.js
138 ms
10x10.png
66 ms
240x168.png
70 ms
65x70.gif
66 ms
20x20.png
69 ms
4 ms
10 ms
epssw.js
24 ms
19 ms
et_n.js
711 ms
index.js
30 ms
rp
4987 ms
wcfg.json
5500 ms
29 ms
index.js
29 ms
et_f.js
30 ms
eg.js
4961 ms
240x168.png
363 ms
renderPageData.htm
420 ms
H907757fdad184e31a1b58bd6507666deo.png
253 ms
mem8YaGs126MiZpBA-U1UQ.woff
254 ms
open-sans.006320aa.woff
255 ms
mem5YaGs126MiZpBA-UNirk-Vg.woff
254 ms
mem5YaGs126MiZpBA-UN7rg-Vg.woff
254 ms
H6dea52a7c0df4bd4846cec6add0060acM.png
287 ms
40x40.png
254 ms
20x20.png
285 ms
info
54 ms
aes.1.1
4079 ms
96x96.png
3698 ms
arrow-left.acf07a9d.png
3428 ms
execute
3178 ms
2929 ms
execute
2774 ms
execute
2390 ms
execute
2007 ms
execute
1619 ms
execute
1180 ms
execute
763 ms
284 ms
S7e9f9bd7efcf4a1784b54cd02aa1f16ay.jpg
270 ms
HTB1XCXgr25TBuNjSspcq6znGFXa1.jpg
265 ms
HTB1hj8Ar1OSBuNjy0Fdq6zDnVXaF.jpg
275 ms
HTB1smB6rYSYBuNjSspfq6AZCpXax.jpg
275 ms
HTB1XlUGjDdYBeNkSmLyq6xfnVXae.jpg
276 ms
HTB1kZ3hjsuYBuNkSmRyq6AA3pXaA.jpg
518 ms
HTB18nEZjDXYBeNkHFrdq6AiuVXaH.jpg
511 ms
HTB1GzTcr9tYBeNjSspkq6zU8VXa5.jpg
281 ms
HTB16JCGrWmWBuNjy1Xaq6xCbXXaI.jpg
510 ms
48x48.png
509 ms
48x48.png
506 ms
HTB16DzJjsuYBuNkSmRyq6AA3pXaR.jpg
508 ms
H674ff433cce14331bf0fc0ca31995b02P.png
509 ms
Haf27f9be5858476bbb53005f8600af05w.jpg
509 ms
Sf97f539a185b45368bf1438a8df5b781i.jpg
512 ms
He7290dc9abcc412cadbfbfd46d017f7bC.jpg
510 ms
Sa40aa12bcbdc48908f5d3f387f5cb4caJ.jpg
513 ms
HTB1WkShPY2pK1RjSZFs761NlXXay.png
512 ms
HTB1QHqMP4naK1RjSZFt762C2VXa1.png
511 ms
HTB14K7NbAxz61VjSZFrq6xeLFXaD.jpg
515 ms
Hacb8bb60fd05408baf8b58238b616475e.jpg
513 ms
H4804f4c9cf9847208e6c35e88c10f23a0.jpg
515 ms
g.gif
732 ms
aes.1.1
727 ms
index.web.js
14 ms
504 ms
baxiaJsonpHandler.js
19 ms
aes.1.1
732 ms
ae.pc_ctr.statweb_ae_ctr
731 ms
punish:resource:template:AESpace:default_184083.html
1074 ms
app.gif
523 ms
eg.js
460 ms
248 ms
aes.1.1
230 ms
ae.pc_ctr.statweb_ae_ctr
233 ms
H1ae6b346a06441d7ac7b26b5702efea9M.png
38 ms
H2c0f139f44264c2787f78eca23889b305.png
44 ms
aes.1.1
468 ms
flexible.js
14 ms
qrcode.min.js
18 ms
main.css
23 ms
punishpage.min.js
31 ms
19 ms
ae.pc_ctr.statweb_ae_ctr
233 ms
fsp.1.1
887 ms
O1CN01oSZaoy1rcfT5pA6JR_!!6000000005652-2-tps-498-120.png
6478 ms
index.js
235 ms
fsp.1.1
896 ms
O1CN01uX800r1KcmF5qDeNd_!!6000000001185-2-tps-276-284.png
265 ms
aes.1.1
700 ms
vivilady.aliexpress.com accessibility score
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.
vivilady.aliexpress.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
vivilady.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 Vivilady.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 Vivilady.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.
vivilady.aliexpress.com
Open Graph description is not detected on the main page of VIVILADY 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: