Tools & Wizards About Us
relogio.tr.aliexpress.com screenshot

Report Summary

  • 0

    Performance

  • 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

relogio.tr.aliexpress.com

404 page

Page Load Speed

23.4 sec in total

First Response

866 ms

Resources Loaded

22.4 sec

Page Rendered

165 ms

relogio.tr.aliexpress.com screenshot

About Website

Visit relogio.tr.aliexpress.com now to see the best up-to-date Relogio Tr Aliexpress content for Brazil and also check out these interesting facts you probably never knew about relogio.tr.aliexpress.com

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

Visit relogio.tr.aliexpress.com

Key Findings

We analyzed Relogio.tr.aliexpress.com page load time and found that the first response time was 866 ms and then it took 22.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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

relogio.tr.aliexpress.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value22.6 s

0/100

10%

TBT (Total Blocking Time)

Value7,790 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.182

1/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

Network Requests Diagram

relogio.tr.aliexpress.com

866 ms

1100437611

456 ms

561 ms

next.min.css

86 ms

index.css

70 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Relogio.tr.aliexpress.com, 37% (34 requests) were made to Assets.alicdn.com and 19% (18 requests) were made to Ae01.alicdn.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Fourier.taobao.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (59%)

Content Size

3.3 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 204.1 kB

  • Original 276.9 kB
  • After minification 270.5 kB
  • After compression 72.8 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 204.1 kB or 74% of the original size.

Image Optimization

-37%

Potential reduce by 7.7 kB

  • Original 20.9 kB
  • After minification 13.2 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, Relogio Tr Aliexpress 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.

JavaScript Optimization

-57%

Potential reduce by 1.5 MB

  • Original 2.6 MB
  • After minification 2.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 1.5 MB or 57% of the original size.

CSS Optimization

-59%

Potential reduce by 208.5 kB

  • Original 356.2 kB
  • After minification 356.1 kB
  • After compression 147.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. Relogio.tr.aliexpress.com needs all CSS files to be minified and compressed as it can save up to 208.5 kB or 59% of the original size.

Requests Breakdown

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

Requests Now

85

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Relogio Tr Aliexpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

relogio.tr.aliexpress.com

relogio.tr.aliexpress.com

866 ms

1100437611

1100437611

456 ms

561 ms

next.min.css

next.min.css

86 ms

index.css

index.css

70 ms

index.js

index.js

72 ms

index.js

index.js

79 ms

index.js

index.js

75 ms

ae-header.css

ae-header.css

74 ms

ae-header.js

ae-header.js

75 ms

index.css

index.css

163 ms

index.js

index.js

114 ms

_cross_page_loader_.js

_cross_page_loader_.js

81 ms

register.js

register.js

79 ms

80 ms

index.js

index.js

16 ms

index.web.cmd.js

index.web.cmd.js

4 ms

12 ms

index.web.js

index.web.js

61 ms

index.web.js

index.web.js

5 ms

index.web.js

index.web.js

12 ms

index.web.js

index.web.js

5 ms

index.web.js

index.web.js

12 ms

index.web.js

index.web.js

12 ms

index.web.js

index.web.js

13 ms

index.web.js

index.web.js

47 ms

index.web.js

index.web.js

16 ms

gep-tracker.js

gep-tracker.js

15 ms

gep-sdk.js

gep-sdk.js

16 ms

10x10.png

10x10.png

136 ms

240x168.png

240x168.png

695 ms

65x70.gif

65x70.gif

170 ms

20x20.png

20x20.png

135 ms

8 ms

24 ms

epssw.js

epssw.js

54 ms

43 ms

et_n.js

et_n.js

1226 ms

index.js

index.js

582 ms

rp

rp

19830 ms

wcfg.json

wcfg.json

2288 ms

580 ms

index.js

index.js

577 ms

et_f.js

et_f.js

580 ms

eg.js

eg.js

2238 ms

240x168.png

240x168.png

638 ms

renderPageData.htm

renderPageData.htm

682 ms

mem8YaGs126MiZpBA-U1UQ.woff

mem8YaGs126MiZpBA-U1UQ.woff

401 ms

open-sans.006320aa.woff

open-sans.006320aa.woff

399 ms

mem5YaGs126MiZpBA-UNirk-Vg.woff

mem5YaGs126MiZpBA-UNirk-Vg.woff

398 ms

mem5YaGs126MiZpBA-UN7rg-Vg.woff

mem5YaGs126MiZpBA-UN7rg-Vg.woff

400 ms

H907757fdad184e31a1b58bd6507666deo.png

H907757fdad184e31a1b58bd6507666deo.png

64 ms

g.gif

g.gif

2928 ms

H6dea52a7c0df4bd4846cec6add0060acM.png

H6dea52a7c0df4bd4846cec6add0060acM.png

59 ms

40x40.png

40x40.png

68 ms

20x20.png

20x20.png

108 ms

info

info

34 ms

aes.1.1

aes.1.1

3121 ms

96x96.png

96x96.png

2918 ms

arrow-left.acf07a9d.png

arrow-left.acf07a9d.png

2906 ms

execute

execute

2186 ms

execute

execute

1679 ms

execute

execute

1174 ms

execute

execute

655 ms

418 ms

app.gif

app.gif

332 ms

48x48.png

48x48.png

299 ms

48x48.png

48x48.png

298 ms

HTB1n1k6ck9E3KVjSZFGq6A19XXa6.jpg

HTB1n1k6ck9E3KVjSZFGq6A19XXa6.jpg

299 ms

HTB1FpeBcmtYBeNjSspaq6yOOFXa5.jpg

HTB1FpeBcmtYBeNjSspaq6yOOFXa5.jpg

996 ms

HTB1eUONcnJYBeNjy1zeq6yhzVXav.jpg

HTB1eUONcnJYBeNjy1zeq6yhzVXav.jpg

740 ms

HTB1L7ARb4SYBuNjSsphq6zGvVXap.jpg

HTB1L7ARb4SYBuNjSsphq6zGvVXap.jpg

1281 ms

HTB1WkShPY2pK1RjSZFs761NlXXay.png

HTB1WkShPY2pK1RjSZFs761NlXXay.png

313 ms

HTB1QHqMP4naK1RjSZFt762C2VXa1.png

HTB1QHqMP4naK1RjSZFt762C2VXa1.png

392 ms

eg.js

eg.js

443 ms

aes.1.1

aes.1.1

720 ms

ae.pc_ctr.statweb_ae_ctr

ae.pc_ctr.statweb_ae_ctr

698 ms

baxiaJsonpHandler.js

baxiaJsonpHandler.js

7 ms

punish:resource:template:AESpace:default_184083.html

punish:resource:template:AESpace:default_184083.html

935 ms

287 ms

aes.1.1

aes.1.1

544 ms

303 ms

flexible.js

flexible.js

299 ms

qrcode.min.js

qrcode.min.js

308 ms

main.css

main.css

307 ms

punishpage.min.js

punishpage.min.js

306 ms

304 ms

aes.1.1

aes.1.1

530 ms

aes.1.1

aes.1.1

235 ms

fsp.1.1

fsp.1.1

1182 ms

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

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

181 ms

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

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

153 ms

fsp.1.1

fsp.1.1

217 ms

Accessibility Review

relogio.tr.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

relogio.tr.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

relogio.tr.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 Relogio.tr.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 Relogio.tr.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

relogio.tr.aliexpress.com

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