3.8 sec in total
476 ms
2.9 sec
448 ms
Welcome to alean.ru homepage info - get ready to check Alean best content for Russia right away, or after learning these important things about alean.ru
Visit alean.ruWe analyzed Alean.ru page load time and found that the first response time was 476 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.
alean.ru performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value37.7 s
0/100
25%
Value23.7 s
0/100
10%
Value20,750 ms
0/100
30%
Value0.279
43/100
15%
Value52.5 s
0/100
10%
476 ms
462 ms
530 ms
680 ms
229 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 56% of them (50 requests) were addressed to the original Alean.ru, 26% (23 requests) were made to Uploads.stells.info and 8% (7 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (955 ms) relates to the external source Uploads.stells.info.
Page size can be reduced by 839.7 kB (39%)
2.2 MB
1.3 MB
In fact, the total size of Alean.ru 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 88.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 14.8 kB, which is 14% 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 88.1 kB or 83% of the original size.
Potential reduce by 167.1 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, Alean needs image optimization as it can save up to 167.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 333.4 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 333.4 kB or 67% of the original size.
Potential reduce by 251.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. Alean.ru needs all CSS files to be minified and compressed as it can save up to 251.1 kB or 85% of the original size.
Number of requests can be reduced by 17 (22%)
79
62
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alean. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
alean.ru
476 ms
www.alean.ru
462 ms
frontend.css
530 ms
frontend.lib.js
680 ms
229 ms
api.js
60 ms
watch.js
1 ms
frontend.js
855 ms
620 ms
combine.xml
581 ms
recaptcha__ru.js
330 ms
3fce55b8267f3cefeced1e527592f80c.jpg
335 ms
banner-88x31-rambler-darkblue2.gif
316 ms
bg_top.jpg
306 ms
anniversary_22.png
304 ms
logo.png
303 ms
pr_links_bg.png
305 ms
icon_home.png
312 ms
menu_sep.png
310 ms
searchbar.png
306 ms
quick_pay.png
306 ms
odno.png
313 ms
vk.png
309 ms
facebook.png
310 ms
dirs_title_bg.png
311 ms
bg_bottom.jpg
364 ms
footer_shadow.png
365 ms
life.png
366 ms
hor_sep.png
366 ms
aeroflot.png
366 ms
rst.gif
367 ms
ATA.png
418 ms
no_borders.png
420 ms
ator.png
428 ms
f8b70bf31701ce5152522a13af24e120.jpg
371 ms
d0d89eb813f52538f4ec94e2841c4dbd.jpg
374 ms
9e6ebc0d7cc57d258169d7b06da73243.jpg
361 ms
d833d103169591f91e6b344597ec2b6b.jpg
361 ms
7bd2c33c391b653182295e54388bf92a.png
360 ms
d6e2e9bce3acee736c380f4374f85487.png
373 ms
f7a0b11deec7c760e15ef3e7e751ab8b.png
389 ms
33cf975d6397dad291f784c25c2b42ab.png
494 ms
06aae3e960b455f9ddbe7e045a130213.png
494 ms
d0a5d719beaa4ca6fe98c4c1f225923e.png
488 ms
4078067cee733575e27463a2ae64ea59.png
491 ms
053a37c18b9a65f22371f01a8558b98a.png
540 ms
efbfaea6776f58667dede0440abfb18a.png
639 ms
368f68c078f437cd2131f769b9b9a092.png
540 ms
7c0a495fa3b3227da5e00b559f1e4085.png
543 ms
1cc62f0a1636ea8d84ff55639ee89c3e.png
930 ms
96f276a4525107a113579261f0ca042a.png
930 ms
6f3a64c4f5b29bd0ac960418285103b6.png
874 ms
406773150e4c7ad3428b82eaf18193da.png
951 ms
5b1e33dfde263496dd49e94e6bd50405.png
955 ms
04908e2cee48d92861fbd378d3f869ac.png
875 ms
8c2b647f90a9e9a451adfbf02e58c7ff.png
952 ms
hit
287 ms
analytics.js
271 ms
index.html
152 ms
regions.html
159 ms
init
690 ms
index.html
158 ms
close.svg
199 ms
hit
182 ms
collect
16 ms
get
517 ms
get
493 ms
av-req-icon.png
100 ms
tsp.html
157 ms
begin-dt-common.html
305 ms
begin-dt-uncommon.html
230 ms
duration-common.html
364 ms
ages.html
379 ms
abode-select.html
392 ms
ring.svg
442 ms
glyphicons-halflings-regular.woff
462 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
370 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
320 ms
4965b66fe115b2f2ed500ece66514d86.cur
346 ms
77492cf358d8b12629399322926c93f2.cur
398 ms
ru.png
80 ms
ua.png
80 ms
bl.png
78 ms
uz.png
82 ms
kz.png
80 ms
ab.png
80 ms
am.png
153 ms
counter2
159 ms
region_select.png
94 ms
alean.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
alean.ru 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
alean.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alean.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Alean.ru 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.
alean.ru
Open Graph description is not detected on the main page of Alean. 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: