Tools & Wizards About Us
funry.aliexpress.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% 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

funry.aliexpress.com

FUNRY Official Store - Amazing products with exclusive discounts on AliExpress

Page Load Speed

10.6 sec in total

First Response

469 ms

Resources Loaded

8.8 sec

Page Rendered

1.3 sec

funry.aliexpress.com screenshot

About Website

Click here to check amazing FUNRY Ali Express content for Brazil. Otherwise, check out these important facts you probably never knew about funry.aliexpress.com

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

Visit funry.aliexpress.com

Key Findings

We analyzed Funry.aliexpress.com page load time and found that the first response time was 469 ms and then it took 10.1 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

funry.aliexpress.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value390 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.662

8/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

funry.aliexpress.com

469 ms

1101250185

1012 ms

84 ms

next.min.css

42 ms

index.css

38 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Funry.aliexpress.com, 39% (35 requests) were made to Assets.alicdn.com and 16% (14 requests) were made to Ae01.alicdn.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Fourier.taobao.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (55%)

Content Size

3.0 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Funry.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. 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 198.6 kB

  • Original 271.2 kB
  • After minification 264.8 kB
  • After compression 72.6 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 198.6 kB or 73% 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, FUNRY 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

-50%

Potential reduce by 1.1 MB

  • Original 2.2 MB
  • After minification 2.2 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 1.1 MB or 50% of the original size.

CSS Optimization

-68%

Potential reduce by 316.3 kB

  • Original 465.4 kB
  • After minification 465.2 kB
  • After compression 149.1 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. Funry.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.

Requests Breakdown

Number of requests can be reduced by 65 (78%)

Requests Now

83

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

funry.aliexpress.com

funry.aliexpress.com

469 ms

1101250185

1101250185

1012 ms

84 ms

next.min.css

next.min.css

42 ms

index.css

index.css

38 ms

index.js

index.js

75 ms

index.js

index.js

78 ms

index.js

index.js

74 ms

ae-header.css

ae-header.css

77 ms

ae-header.js

ae-header.js

82 ms

index.css

index.css

76 ms

index.js

index.js

81 ms

_cross_page_loader_.js

_cross_page_loader_.js

79 ms

register.js

register.js

130 ms

28 ms

622 ms

epssw.js

epssw.js

13 ms

10x10.png

10x10.png

926 ms

240x168.png

240x168.png

1062 ms

232 ms

eg.js

eg.js

3831 ms

451 ms

index.js

index.js

446 ms

index.web.cmd.js

index.web.cmd.js

445 ms

447 ms

index.web.js

index.web.js

450 ms

index.web.js

index.web.js

446 ms

index.web.js

index.web.js

469 ms

index.web.js

index.web.js

450 ms

index.web.js

index.web.js

455 ms

index.web.js

index.web.js

467 ms

index.web.js

index.web.js

468 ms

index.web.js

index.web.js

998 ms

index.web.js

index.web.js

469 ms

gep-tracker.js

gep-tracker.js

1006 ms

gep-sdk.js

gep-sdk.js

477 ms

65x70.gif

65x70.gif

448 ms

20x20.png

20x20.png

447 ms

et_f.js

et_f.js

1004 ms

index.js

index.js

449 ms

rp

rp

3887 ms

wcfg.json

wcfg.json

3731 ms

174 ms

index.js

index.js

553 ms

et_f.js

et_f.js

711 ms

info

info

543 ms

240x168.png

240x168.png

535 ms

renderPageData.htm

renderPageData.htm

378 ms

mem8YaGs126MiZpBA-U1UQ.woff

mem8YaGs126MiZpBA-U1UQ.woff

159 ms

open-sans.006320aa.woff

open-sans.006320aa.woff

164 ms

mem5YaGs126MiZpBA-UNirk-Vg.woff

mem5YaGs126MiZpBA-UNirk-Vg.woff

159 ms

mem5YaGs126MiZpBA-UN7rg-Vg.woff

mem5YaGs126MiZpBA-UN7rg-Vg.woff

158 ms

H907757fdad184e31a1b58bd6507666deo.png

H907757fdad184e31a1b58bd6507666deo.png

175 ms

H6dea52a7c0df4bd4846cec6add0060acM.png

H6dea52a7c0df4bd4846cec6add0060acM.png

176 ms

40x40.png

40x40.png

176 ms

20x20.png

20x20.png

177 ms

g.gif

g.gif

2483 ms

96x96.png

96x96.png

2200 ms

arrow-left.acf07a9d.png

arrow-left.acf07a9d.png

2191 ms

execute

execute

1895 ms

execute

execute

1395 ms

execute

execute

919 ms

execute

execute

488 ms

268 ms

aes.1.1

aes.1.1

562 ms

HTB1LBANiL1TBuNjy0Fjq6yjyXXaE.jpg

HTB1LBANiL1TBuNjy0Fjq6yjyXXaE.jpg

1013 ms

48x48.png

48x48.png

241 ms

48x48.png

48x48.png

236 ms

HTB1OZbAXmCWBuNjy0Fhq6z6EVXat.jpg

HTB1OZbAXmCWBuNjy0Fhq6z6EVXat.jpg

760 ms

eg.js

eg.js

552 ms

aes.1.1

aes.1.1

547 ms

app.gif

app.gif

270 ms

baxiaJsonpHandler.js

baxiaJsonpHandler.js

225 ms

278 ms

punish:resource:template:AESpace:default_184083.html

punish:resource:template:AESpace:default_184083.html

520 ms

aes.1.1

aes.1.1

452 ms

25 ms

aes.1.1

aes.1.1

239 ms

flexible.js

flexible.js

198 ms

qrcode.min.js

qrcode.min.js

199 ms

main.css

main.css

201 ms

punishpage.min.js

punishpage.min.js

205 ms

212 ms

aes.1.1

aes.1.1

228 ms

fsp.1.1

fsp.1.1

887 ms

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

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

874 ms

index.js

index.js

840 ms

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

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

222 ms

fsp.1.1

fsp.1.1

418 ms

aes.1.1

aes.1.1

230 ms

Accessibility Review

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

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

funry.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 Funry.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 Funry.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

funry.aliexpress.com

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