11.9 sec in total
733 ms
10.1 sec
1 sec
Visit hoto.aliexpress.com now to see the best up-to-date HOTO Ali Express content for Brazil and also check out these interesting facts you probably never knew about hoto.aliexpress.com
Discover the wide range of from AliExpress Top Seller HOTO Official Store.Enjoy ✓Free Shipping Worldwide! ✓Limited Time Sale ✓Easy Return.
Visit hoto.aliexpress.comWe analyzed Hoto.aliexpress.com page load time and found that the first response time was 733 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hoto.aliexpress.com performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value15.3 s
0/100
25%
Value12.5 s
3/100
10%
Value1,630 ms
12/100
30%
Value0.303
39/100
15%
Value15.2 s
7/100
10%
733 ms
321 ms
457 ms
85 ms
295 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Hoto.aliexpress.com, 28% (34 requests) were made to Assets.alicdn.com and 24% (29 requests) were made to Ae01.alicdn.com. The less responsive or slowest element that took the longest time to load (4.9 sec) relates to the external source Bdc.alibabachengdun.com.
Page size can be reduced by 2.8 MB (66%)
4.2 MB
1.4 MB
In fact, the total size of Hoto.aliexpress.com main page is 4.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. 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.8 MB which makes up the majority of the site volume.
Potential reduce by 234.4 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 234.4 kB or 75% 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, HOTO Ali Express 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.
Potential reduce by 1.6 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.6 MB or 58% of the original size.
Potential reduce by 962.6 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. Hoto.aliexpress.com needs all CSS files to be minified and compressed as it can save up to 962.6 kB or 86% of the original size.
Number of requests can be reduced by 82 (73%)
113
31
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HOTO 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 49 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
hoto.aliexpress.com
733 ms
1101600054
321 ms
457 ms
next.min.css
85 ms
index.css
295 ms
index.js
298 ms
index.js
299 ms
index.js
16 ms
ae-header.css
301 ms
ae-header.js
299 ms
index.css
300 ms
index.js
305 ms
_cross_page_loader_.js
5 ms
register.js
4 ms
6 ms
index.js
7 ms
index.web.cmd.js
6 ms
15 ms
index.web.js
7 ms
index.web.js
13 ms
index.web.js
9 ms
index.web.js
9 ms
index.web.js
10 ms
index.web.js
12 ms
index.web.js
14 ms
index.web.js
14 ms
index.web.js
15 ms
index.web.js
19 ms
index.web.js
19 ms
index.web.js
19 ms
index.web.js
17 ms
index.web.js
20 ms
index.web.js
18 ms
gep-tracker.js
18 ms
gep-sdk.js
19 ms
10x10.png
2564 ms
240x168.png
2564 ms
65x70.gif
2565 ms
20x20.png
2641 ms
4 ms
6 ms
epssw.js
163 ms
15 ms
et_n.js
154 ms
index.js
29 ms
rp
3445 ms
wcfg.json
4871 ms
28 ms
eg.js
3174 ms
renderPageData.htm
908 ms
H907757fdad184e31a1b58bd6507666deo.png
2434 ms
H6dea52a7c0df4bd4846cec6add0060acM.png
2376 ms
40x40.png
2475 ms
mem8YaGs126MiZpBA-U1UQ.woff
58 ms
open-sans.006320aa.woff
59 ms
mem5YaGs126MiZpBA-UNirk-Vg.woff
58 ms
mem5YaGs126MiZpBA-UN7rg-Vg.woff
58 ms
aes.1.1
2584 ms
arrow-left.acf07a9d.png
1465 ms
execute
1597 ms
926 ms
execute
1182 ms
423 ms
96x96.png
367 ms
S952fdbf73ec746a4b0708ed5180ac77bi.jpg
935 ms
S60d9b9994a1446eaaa55260b34d57a1ax.jpg
936 ms
Sc99d6e82c9c649958095a7650a5d61a3x.jpg
934 ms
Sddbcdd1628544febbfcb0fb87ffe745eO.jpg
934 ms
Sa64d29b04439483188b12b9f864a3115A.jpg
941 ms
S76ec4533f24247d884fa23f262234146m.jpg
941 ms
S42e21e896b9b407295fc95f03ecbadc1h.jpg
2551 ms
Saedf77c0ac3d4be5868253c866707aefE.jpg
2551 ms
Sfb3ba64d672c460b9a3e723d96457bech.jpg
2552 ms
H61b77831129548c8a01f03588f4f369cm.jpg
2315 ms
Sbd95fdbc084e4c3e99f1cea6edc9a16eh.jpg
2551 ms
48x48.png
948 ms
48x48.png
953 ms
S70da0184c5084e76b1f023e523b70995g.jpg
2549 ms
S7eb14c6d9cbb410bb9332728ae8c695aG.jpg
2549 ms
S5a8962b740354e778239d0b0d4a34038z.jpg
2834 ms
S92676a56b2cb4d8dbceae840241b25b85.jpg
2860 ms
Sf119d353fdba4a45b249f21f39e57630o.jpg
2682 ms
Sd6a3c805f126401bb5207bbbd3d1cd6ez.jpg
3148 ms
HTB1WkShPY2pK1RjSZFs761NlXXay.png
2557 ms
HTB1QHqMP4naK1RjSZFt762C2VXa1.png
2556 ms
g.gif
2289 ms
aes.1.1
2289 ms
info
21 ms
index.web.js
3 ms
aes.1.1
2250 ms
527 ms
aes.1.1
1858 ms
ae.pc_ctr.statweb_ae_ctr
1857 ms
baxiaJsonpHandler.js
4 ms
punish:resource:template:AESpace:default_184083.html
2120 ms
1140 ms
958 ms
709 ms
509 ms
293 ms
eg.js
470 ms
app.gif
213 ms
aes.1.1
258 ms
ae.pc_ctr.statweb_ae_ctr
255 ms
aes.1.1
244 ms
aes.1.1
255 ms
aes.1.1
247 ms
aes.1.1
426 ms
aes.1.1
439 ms
flexible.js
3 ms
qrcode.min.js
6 ms
main.css
8 ms
punishpage.min.js
9 ms
9 ms
fsp.1.1
2599 ms
O1CN01oSZaoy1rcfT5pA6JR_!!6000000005652-2-tps-498-120.png
167 ms
index.js
4 ms
fsp.1.1
267 ms
O1CN01uX800r1KcmF5qDeNd_!!6000000001185-2-tps-276-284.png
138 ms
aes.1.1
237 ms
hoto.aliexpress.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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.
hoto.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
Page has valid source maps
hoto.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 Hoto.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 Hoto.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.
hoto.aliexpress.com
Open Graph description is not detected on the main page of HOTO 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: