Tools & Wizards About Us
fengrise.aliexpress.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fengrise.aliexpress.com

FENGRISE Official Store - Amazing products with exclusive discounts on AliExpress

Page Load Speed

17.2 sec in total

First Response

536 ms

Resources Loaded

14.7 sec

Page Rendered

1.9 sec

fengrise.aliexpress.com screenshot

About Website

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

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

Visit fengrise.aliexpress.com

Key Findings

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

Performance Metrics

fengrise.aliexpress.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.713

7/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

fengrise.aliexpress.com

536 ms

1100396190

425 ms

242 ms

next.min.css

21 ms

index.css

40 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 Fengrise.aliexpress.com, 33% (38 requests) were made to Assets.alicdn.com and 23% (26 requests) were made to Ae01.alicdn.com. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Img.alicdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 836.9 kB (38%)

Content Size

2.2 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fengrise.aliexpress.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. 80% 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 242.7 kB

  • Original 318.4 kB
  • After minification 312.0 kB
  • After compression 75.7 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 242.7 kB or 76% of the original size.

Image Optimization

-35%

Potential reduce by 7.7 kB

  • Original 21.6 kB
  • After minification 13.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, FENGRISE Ali Express needs image optimization as it can save up to 7.7 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-30%

Potential reduce by 478.6 kB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 1.1 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 478.6 kB or 30% of the original size.

CSS Optimization

-42%

Potential reduce by 107.9 kB

  • Original 256.6 kB
  • After minification 256.5 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. Fengrise.aliexpress.com needs all CSS files to be minified and compressed as it can save up to 107.9 kB or 42% of the original size.

Requests Breakdown

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

Requests Now

107

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fengrise.aliexpress.com

fengrise.aliexpress.com

536 ms

1100396190

1100396190

425 ms

242 ms

next.min.css

next.min.css

21 ms

index.css

index.css

40 ms

index.js

index.js

62 ms

index.js

index.js

40 ms

index.js

index.js

67 ms

ae-header.css

ae-header.css

42 ms

ae-header.js

ae-header.js

50 ms

index.css

index.css

59 ms

index.js

index.js

47 ms

_cross_page_loader_.js

_cross_page_loader_.js

30 ms

register.js

register.js

8 ms

9 ms

index.js

index.js

8 ms

index.web.cmd.js

index.web.cmd.js

5 ms

10 ms

index.web.js

index.web.js

70 ms

index.web.js

index.web.js

137 ms

index.web.js

index.web.js

13 ms

index.web.js

index.web.js

12 ms

index.web.js

index.web.js

12 ms

index.web.js

index.web.js

16 ms

index.web.js

index.web.js

19 ms

index.web.js

index.web.js

17 ms

index.web.js

index.web.js

15 ms

index.web.js

index.web.js

19 ms

index.web.js

index.web.js

25 ms

index.web.js

index.web.js

19 ms

gep-tracker.js

gep-tracker.js

16 ms

gep-sdk.js

gep-sdk.js

15 ms

10x10.png

10x10.png

57 ms

240x168.png

240x168.png

57 ms

65x70.gif

65x70.gif

64 ms

20x20.png

20x20.png

63 ms

27 ms

11 ms

epssw.js

epssw.js

133 ms

512 ms

et_n.js

et_n.js

527 ms

index.js

index.js

23 ms

rp

rp

4328 ms

wcfg.json

wcfg.json

4326 ms

23 ms

index.js

index.js

118 ms

et_f.js

et_f.js

23 ms

240x168.png

240x168.png

484 ms

renderPageData.htm

renderPageData.htm

895 ms

H907757fdad184e31a1b58bd6507666deo.png

H907757fdad184e31a1b58bd6507666deo.png

410 ms

H6dea52a7c0df4bd4846cec6add0060acM.png

H6dea52a7c0df4bd4846cec6add0060acM.png

409 ms

40x40.png

40x40.png

406 ms

20x20.png

20x20.png

406 ms

mem8YaGs126MiZpBA-U1UQ.woff

mem8YaGs126MiZpBA-U1UQ.woff

403 ms

open-sans.006320aa.woff

open-sans.006320aa.woff

401 ms

mem5YaGs126MiZpBA-UNirk-Vg.woff

mem5YaGs126MiZpBA-UNirk-Vg.woff

400 ms

mem5YaGs126MiZpBA-UN7rg-Vg.woff

mem5YaGs126MiZpBA-UN7rg-Vg.woff

403 ms

eg.js

eg.js

3804 ms

aes.1.1

aes.1.1

3503 ms

96x96.png

96x96.png

2577 ms

arrow-left.acf07a9d.png

arrow-left.acf07a9d.png

2571 ms

H9721e3d49ad9496eb608985ff50d9949m.jpg

H9721e3d49ad9496eb608985ff50d9949m.jpg

3384 ms

execute

execute

2388 ms

execute

execute

2032 ms

execute

execute

1686 ms

execute

execute

1332 ms

execute

execute

959 ms

execute

execute

802 ms

351 ms

H75f2d9ebb4324190a2debaa92ef0de548.jpg

H75f2d9ebb4324190a2debaa92ef0de548.jpg

1539 ms

H64b888b025c24f5c83efa894269d5416g.jpg

H64b888b025c24f5c83efa894269d5416g.jpg

1295 ms

Hceb16911836f46cb97c8ef33b8e5dda6S.jpg

Hceb16911836f46cb97c8ef33b8e5dda6S.jpg

1299 ms

S5e61b24b8fd246dd8063f9e24bdcf3f1R.jpg

S5e61b24b8fd246dd8063f9e24bdcf3f1R.jpg

279 ms

Sc3ef93a0c67a4dc0adfc0462f129cabeR.jpg

Sc3ef93a0c67a4dc0adfc0462f129cabeR.jpg

279 ms

HTB1F8OrdL9TBuNjy0Fcq6zeiFXaR.jpg

HTB1F8OrdL9TBuNjy0Fcq6zeiFXaR.jpg

275 ms

HTB1b59vdFuWBuNjSszbq6AS7FXaI.jpg

HTB1b59vdFuWBuNjSszbq6AS7FXaI.jpg

305 ms

48x48.png

48x48.png

277 ms

48x48.png

48x48.png

309 ms

Sdaa171ae39e7404287de30de0dee74fdr.jpg

Sdaa171ae39e7404287de30de0dee74fdr.jpg

306 ms

H747a42572f6b477aa38210538168ff73y.jpg

H747a42572f6b477aa38210538168ff73y.jpg

543 ms

S596fbe14414f4d5bb57ef9cd1b3ee323R.jpg

S596fbe14414f4d5bb57ef9cd1b3ee323R.jpg

548 ms

HTB1WkShPY2pK1RjSZFs761NlXXay.png

HTB1WkShPY2pK1RjSZFs761NlXXay.png

306 ms

HTB1QHqMP4naK1RjSZFt762C2VXa1.png

HTB1QHqMP4naK1RjSZFt762C2VXa1.png

311 ms

S04c7a4b19235433c9896d4f9c1e53bcdC.jpg

S04c7a4b19235433c9896d4f9c1e53bcdC.jpg

317 ms

Sc96ed41043dc42b9ab9f1ed9f73e9785x.jpg

Sc96ed41043dc42b9ab9f1ed9f73e9785x.jpg

316 ms

Sca4074e3c8244da8b85608899d8c5aacm.jpg

Sca4074e3c8244da8b85608899d8c5aacm.jpg

547 ms

S63b3c33184784b2b8182b6def36f030fM.jpg

S63b3c33184784b2b8182b6def36f030fM.jpg

541 ms

Sbb72f36e09324fe885933fd3bf262c2fX.jpg

Sbb72f36e09324fe885933fd3bf262c2fX.jpg

542 ms

g.gif

g.gif

1079 ms

aes.1.1

aes.1.1

1081 ms

info

info

231 ms

baxiaJsonpHandler.js

baxiaJsonpHandler.js

227 ms

322 ms

punish:resource:template:AESpace:default_184083.html

punish:resource:template:AESpace:default_184083.html

1637 ms

aes.1.1

aes.1.1

480 ms

ae.pc_ctr.statweb_ae_ctr

ae.pc_ctr.statweb_ae_ctr

483 ms

218 ms

244 ms

app.gif

app.gif

417 ms

aes.1.1

aes.1.1

425 ms

eg.js

eg.js

241 ms

aes.1.1

aes.1.1

456 ms

aes.1.1

aes.1.1

232 ms

ae.pc_ctr.statweb_ae_ctr

ae.pc_ctr.statweb_ae_ctr

235 ms

flexible.js

flexible.js

5 ms

qrcode.min.js

qrcode.min.js

5 ms

main.css

main.css

8 ms

punishpage.min.js

punishpage.min.js

7 ms

17 ms

fsp.1.1

fsp.1.1

967 ms

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

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

5149 ms

index.js

index.js

221 ms

fsp.1.1

fsp.1.1

828 ms

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

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

234 ms

aes.1.1

aes.1.1

719 ms

Accessibility Review

fengrise.aliexpress.com accessibility score

78

Accessibility Issues

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

fengrise.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

fengrise.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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

fengrise.aliexpress.com

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