Tools & Wizards About Us
would.aliexpress.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

would.aliexpress.com

DealintheBest Store - Amazing products with exclusive discounts on AliExpress

Page Load Speed

12 sec in total

First Response

631 ms

Resources Loaded

10 sec

Page Rendered

1.4 sec

would.aliexpress.com screenshot

About Website

Welcome to would.aliexpress.com homepage info - get ready to check Would Ali Express best content for Brazil right away, or after learning these important things about would.aliexpress.com

Discover the wide range of from AliExpress Top Seller DealintheBest Store.Enjoy ✓Free Shipping Worldwide! ✓Limited Time Sale ✓Easy Return.

Visit would.aliexpress.com

Key Findings

We analyzed Would.aliexpress.com page load time and found that the first response time was 631 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

would.aliexpress.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value18.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value1.286

1/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

would.aliexpress.com

631 ms

1100497630

302 ms

484 ms

next.min.css

80 ms

index.css

33 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 Would.aliexpress.com, 36% (35 requests) were made to Assets.alicdn.com and 20% (20 requests) were made to Ae01.alicdn.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Ae.mmstat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 865.7 kB (41%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Would.aliexpress.com main page is 2.1 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 207.9 kB

  • Original 281.1 kB
  • After minification 274.8 kB
  • After compression 73.2 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 207.9 kB or 74% of the original size.

Image Optimization

-33%

Potential reduce by 7.7 kB

  • Original 23.6 kB
  • After minification 15.9 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, Would 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.

JavaScript Optimization

-34%

Potential reduce by 529.6 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 1.0 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 529.6 kB or 34% of the original size.

CSS Optimization

-45%

Potential reduce by 120.5 kB

  • Original 269.1 kB
  • After minification 269.0 kB
  • After compression 148.7 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. Would.aliexpress.com needs all CSS files to be minified and compressed as it can save up to 120.5 kB or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (75%)

Requests Now

91

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Would 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 46 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

would.aliexpress.com

would.aliexpress.com

631 ms

1100497630

1100497630

302 ms

484 ms

next.min.css

next.min.css

80 ms

index.css

index.css

33 ms

index.js

index.js

38 ms

index.js

index.js

106 ms

index.js

index.js

37 ms

ae-header.css

ae-header.css

35 ms

ae-header.js

ae-header.js

43 ms

index.css

index.css

36 ms

index.js

index.js

40 ms

_cross_page_loader_.js

_cross_page_loader_.js

39 ms

register.js

register.js

7 ms

5 ms

index.js

index.js

3 ms

index.web.cmd.js

index.web.cmd.js

4 ms

13 ms

index.web.js

index.web.js

152 ms

index.web.js

index.web.js

8 ms

index.web.js

index.web.js

8 ms

index.web.js

index.web.js

8 ms

index.web.js

index.web.js

9 ms

index.web.js

index.web.js

11 ms

index.web.js

index.web.js

12 ms

index.web.js

index.web.js

18 ms

index.web.js

index.web.js

13 ms

index.web.js

index.web.js

14 ms

gep-tracker.js

gep-tracker.js

15 ms

gep-sdk.js

gep-sdk.js

15 ms

10x10.png

10x10.png

283 ms

240x168.png

240x168.png

282 ms

65x70.gif

65x70.gif

282 ms

20x20.png

20x20.png

281 ms

5 ms

245 ms

epssw.js

epssw.js

12 ms

7 ms

eg.js

eg.js

3367 ms

et_n.js

et_n.js

378 ms

240x168.png

240x168.png

366 ms

renderPageData.htm

renderPageData.htm

289 ms

H907757fdad184e31a1b58bd6507666deo.png

H907757fdad184e31a1b58bd6507666deo.png

98 ms

H6dea52a7c0df4bd4846cec6add0060acM.png

H6dea52a7c0df4bd4846cec6add0060acM.png

102 ms

40x40.png

40x40.png

97 ms

20x20.png

20x20.png

97 ms

mem8YaGs126MiZpBA-U1UQ.woff

mem8YaGs126MiZpBA-U1UQ.woff

2149 ms

open-sans.006320aa.woff

open-sans.006320aa.woff

2150 ms

mem5YaGs126MiZpBA-UNirk-Vg.woff

mem5YaGs126MiZpBA-UNirk-Vg.woff

2147 ms

mem5YaGs126MiZpBA-UN7rg-Vg.woff

mem5YaGs126MiZpBA-UN7rg-Vg.woff

2149 ms

info

info

2792 ms

96x96.png

96x96.png

2062 ms

execute

execute

1837 ms

execute

execute

1493 ms

execute

execute

1142 ms

execute

execute

808 ms

execute

execute

468 ms

829 ms

arrow-left.acf07a9d.png

arrow-left.acf07a9d.png

226 ms

H27450d91abd942a68f6b378d0feb4307w.jpg

H27450d91abd942a68f6b378d0feb4307w.jpg

226 ms

Hb00a940098024607bf64478634a45834t.jpg

Hb00a940098024607bf64478634a45834t.jpg

226 ms

48x48.png

48x48.png

227 ms

48x48.png

48x48.png

226 ms

S59fc3f47eee84fbbaa7dd42e42908fc6t.jpg

S59fc3f47eee84fbbaa7dd42e42908fc6t.jpg

827 ms

Hfc02a03d04804978a4da65242dbf6e11e.jpg

Hfc02a03d04804978a4da65242dbf6e11e.jpg

649 ms

H2a9e392288c94af2bb0d941ca0f5db7cV.jpg

H2a9e392288c94af2bb0d941ca0f5db7cV.jpg

650 ms

Hce9aa07feb114e9a8030282127d90c7aS.jpg

Hce9aa07feb114e9a8030282127d90c7aS.jpg

651 ms

HTB1WkShPY2pK1RjSZFs761NlXXay.png

HTB1WkShPY2pK1RjSZFs761NlXXay.png

229 ms

HTB1QHqMP4naK1RjSZFt762C2VXa1.png

HTB1QHqMP4naK1RjSZFt762C2VXa1.png

648 ms

g.gif

g.gif

779 ms

index.js

index.js

186 ms

index.js

index.js

184 ms

aes.1.1

aes.1.1

818 ms

baxiaJsonpHandler.js

baxiaJsonpHandler.js

7 ms

punish:resource:template:AESpace:default_184083.html

punish:resource:template:AESpace:default_184083.html

1017 ms

baxiaCommon.js

baxiaCommon.js

358 ms

wcfg.json

wcfg.json

1654 ms

rp

rp

1467 ms

app.gif

app.gif

441 ms

ae.pc_ctr.statweb_ae_ctr

ae.pc_ctr.statweb_ae_ctr

443 ms

269 ms

ae.pc_ctr.statweb_ae_ctr

ae.pc_ctr.statweb_ae_ctr

244 ms

aes.1.1

aes.1.1

467 ms

eg.js

eg.js

468 ms

flexible.js

flexible.js

9 ms

qrcode.min.js

qrcode.min.js

7 ms

main.css

main.css

6 ms

punishpage.min.js

punishpage.min.js

14 ms

7 ms

fsp.1.1

fsp.1.1

1063 ms

191 ms

aes.1.1

aes.1.1

373 ms

punish

punish

185 ms

aes.1.1

aes.1.1

230 ms

O1CN01oSZaoy1rcfT5pA6JR_!!6000000005652-2-tps-498-120.png

O1CN01oSZaoy1rcfT5pA6JR_!!6000000005652-2-tps-498-120.png

2313 ms

fsp.1.1

fsp.1.1

432 ms

O1CN01uX800r1KcmF5qDeNd_!!6000000001185-2-tps-276-284.png

O1CN01uX800r1KcmF5qDeNd_!!6000000001185-2-tps-276-284.png

238 ms

aes.1.1

aes.1.1

230 ms

Accessibility Review

would.aliexpress.com accessibility score

75

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

would.aliexpress.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

would.aliexpress.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Would.aliexpress.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 Would.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.

Social Sharing Optimization

would.aliexpress.com

Open Graph description is not detected on the main page of Would 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: