3.6 sec in total
367 ms
2.8 sec
456 ms
Click here to check amazing Aloes content. Otherwise, check out these important facts you probably never knew about aloes.info
... Why so serious? ...
Visit aloes.infoWe analyzed Aloes.info page load time and found that the first response time was 367 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
aloes.info performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value2.3 s
92/100
25%
Value2.7 s
96/100
10%
Value10 ms
100/100
30%
Value0.017
100/100
15%
Value2.7 s
97/100
10%
367 ms
165 ms
170 ms
290 ms
372 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 79% of them (52 requests) were addressed to the original Aloes.info, 11% (7 requests) were made to Pogodynka.pl and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Aloes.info.
Page size can be reduced by 366.3 kB (50%)
731.6 kB
365.3 kB
In fact, the total size of Aloes.info main page is 731.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 270.9 kB which makes up the majority of the site volume.
Potential reduce by 55.1 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. This page needs HTML code to be minified as it can gain 10.3 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 55.1 kB or 81% of the original size.
Potential reduce by 11.6 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. Aloes images are well optimized though.
Potential reduce by 159.9 kB
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 159.9 kB or 71% of the original size.
Potential reduce by 139.8 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. Aloes.info needs all CSS files to be minified and compressed as it can save up to 139.8 kB or 83% of the original size.
Number of requests can be reduced by 38 (59%)
64
26
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aloes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
aloes.info
367 ms
reset.css
165 ms
defaults.css
170 ms
style.css
290 ms
bootstrap.css
372 ms
shortcodes.css
204 ms
woocommerce-layout.css
188 ms
woocommerce.css
291 ms
sociable.css
249 ms
jquery.js
462 ms
jquery-migrate.min.js
298 ms
bootstrap.js
747 ms
superfish.js
377 ms
jquery.mobilemenu.js
366 ms
addtofavorites.js
379 ms
counter.css
486 ms
jquery.cycle.all.js
544 ms
760 ms
add-to-cart.min.js
422 ms
jquery.blockUI.min.js
509 ms
woocommerce.min.js
485 ms
jquery.cookie.min.js
518 ms
cart-fragments.min.js
495 ms
hoverIntent.min.js
574 ms
wp-embed.min.js
586 ms
css
24 ms
wp-emoji-release.min.js
345 ms
background.jpg
641 ms
header-bg.png
535 ms
aloekf.jpg
543 ms
twitter.png
537 ms
facebook.png
536 ms
gplus.png
535 ms
linkedin.png
539 ms
rss.png
537 ms
email.png
537 ms
menu-secondary-bg.png
539 ms
main-bg.png
542 ms
1.jpg
592 ms
2.jpg
548 ms
3.jpg
595 ms
4.jpg
550 ms
5.jpg
603 ms
featured-next.png
591 ms
featured-prev.png
605 ms
date.png
655 ms
comments.png
660 ms
search.png
667 ms
widgettitle-bg.png
702 ms
widget-list.png
687 ms
all.js
503 ms
footer-widgets-bg.png
675 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
17 ms
background.png
483 ms
6.png
475 ms
n8z60d.png
472 ms
5.png
474 ms
n8z00n.png
474 ms
logo.png
475 ms
1f609.png
183 ms
aloes.info
1098 ms
featured-pager.png
243 ms
128 ms
xd_arbiter.php
259 ms
xd_arbiter.php
416 ms
woocommerce-smallscreen.css
125 ms
aloes.info accessibility score
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
aloes.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
aloes.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
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
FR
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aloes.info can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed Polish language. Our system also found out that Aloes.info 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.
aloes.info
Open Graph description is not detected on the main page of Aloes. 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: