5.5 sec in total
295 ms
4.8 sec
392 ms
Visit rusline.aero now to see the best up-to-date Rusline content for Russia and also check out these interesting facts you probably never knew about rusline.aero
Купить авиабилеты онлайн на сайте «РусЛайн». Регулярные и чартерные авиапервозки, Vip чартеры и бизнес-авиация
Visit rusline.aeroWe analyzed Rusline.aero page load time and found that the first response time was 295 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
rusline.aero performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value8.3 s
2/100
25%
Value11.7 s
4/100
10%
Value990 ms
27/100
30%
Value0
100/100
15%
Value17.1 s
4/100
10%
295 ms
447 ms
1256 ms
136 ms
402 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 60% of them (55 requests) were addressed to the original Rusline.aero, 13% (12 requests) were made to Fonts.gstatic.com and 10% (9 requests) were made to Tickets.rusline.aero. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Rusline.aero.
Page size can be reduced by 169.3 kB (46%)
366.1 kB
196.8 kB
In fact, the total size of Rusline.aero main page is 366.1 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. 60% of websites need less resources to load. HTML takes 175.3 kB which makes up the majority of the site volume.
Potential reduce by 145.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. This page needs HTML code to be minified as it can gain 20.2 kB, which is 12% 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 145.4 kB or 83% of the original size.
Potential reduce by 3 B
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. Rusline images are well optimized though.
Potential reduce by 3.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 20.9 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. Rusline.aero needs all CSS files to be minified and compressed as it can save up to 20.9 kB or 19% of the original size.
Number of requests can be reduced by 41 (62%)
66
25
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rusline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
rusline.aero
295 ms
rusline.aero
447 ms
www.rusline.aero
1256 ms
kernel_main_v1.css
136 ms
template_6539ea7225e331bbcdcdba44bb0f88cb_v1.css
402 ms
jquery.fancybox.min.css
456 ms
style.css
409 ms
itbeframes.css
428 ms
slick.css
52 ms
css
55 ms
styles.css
698 ms
flights.search.widget.min.css
1146 ms
flights.search.widget.min.css
275 ms
style.css
407 ms
style.css
846 ms
style.css
720 ms
style.css
518 ms
font-awesome.css
528 ms
kernel_main_v1.js
674 ms
jquery.min.js
638 ms
jquery.mousewheel.min.js
722 ms
jquery.fancybox.min.js
729 ms
classie.js
549 ms
selectFx.js
639 ms
scripts.js
652 ms
slick.min.js
53 ms
jquery-ui.min1.11.4.js
951 ms
jquery.maskedinput.min.js
763 ms
sip-0.12.0.js
1037 ms
scripts.js
806 ms
jquery.cookie.js
819 ms
element.js
60 ms
script.js
1015 ms
validate-foot-form.js
937 ms
js
84 ms
Leto_2024.jpg
1077 ms
charter_banner.jpg
1260 ms
title_pr.jpg
1261 ms
title_pr.jpg
1276 ms
title_pr.jpg
1259 ms
god_semi.jpg
1260 ms
flags.png
145 ms
banner_summer_2020.jpg
774 ms
phone.svg
241 ms
hill.svg
244 ms
cancel.svg
242 ms
ico_arrow.png
242 ms
slidearrow.png
244 ms
459c331e81a1e8153c6f62dfe7a35d8f.jpg
300 ms
7513d9b371e613c4b88ced8564cfb074.jpg
359 ms
c4681e74f35400ddcb00c1fbf302d3fc.jpg
359 ms
f1e0206d829fc657e7fbd3fd1d0b1f20.jpg
357 ms
971e0926eb665aa9a670afe316e704bd.png
357 ms
_logo-rusline.jpg
357 ms
Diktant_new.jpg
427 ms
Kotlas_new.jpg
490 ms
%D0%AF%D1%80%D0%BE%D1%81%D0%BB%D0%B0%D0%B2%D0%BB%D1%8C_new.jpg
483 ms
email.svg
488 ms
sitemap.svg
487 ms
ba.js
321 ms
KFOlCnqEu92Fr1MmSU5fABc-.woff
191 ms
KFOkCnqEu92Fr1MmgVxMIzQ.woff
208 ms
roboto-v16-latin_cyrillic-regular.woff
266 ms
KFOmCnqEu92Fr1Mu5mxM.woff
236 ms
roboto-v16-latin_cyrillic-500.woff
173 ms
KFOlCnqEu92Fr1MmEU9fABc-.woff
236 ms
roboto-v16-latin_cyrillic-700.woff
747 ms
KFOlCnqEu92Fr1MmWUlfABc-.woff
235 ms
KFOlCnqEu92Fr1MmYUtfABc-.woff
236 ms
KFOjCnqEu92Fr1Mu51TjASc-CsI.woff
286 ms
KFOiCnqEu92Fr1Mu51QrEzQdKQ.woff
265 ms
roboto-v16-latin_cyrillic-italic.woff
733 ms
KFOkCnqEu92Fr1Mu51xMIzQ.woff
236 ms
roboto-v16-latin_cyrillic-500italic.woff
821 ms
KFOjCnqEu92Fr1Mu51S7ACc-CsI.woff
263 ms
roboto-v16-latin_cyrillic-700italic.woff
839 ms
KFOjCnqEu92Fr1Mu51TzBic-CsI.woff
264 ms
KFOjCnqEu92Fr1Mu51TLBCc-CsI.woff
264 ms
fontawesome-webfont.woff
233 ms
watch.js
22 ms
best_offers.jpg
417 ms
bx_stat
198 ms
%D0%94%D0%BE%D0%BF.%D0%B1%D0%B0%D0%B3%D0%B0%D0%B6_2.jpg
266 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
241 ms
check-in.jpg
135 ms
rtrg
127 ms
business_hall.jpg
136 ms
cs-select.css
133 ms
cs-skin-border.css
133 ms
buttons.css
128 ms
cabin_seats.jpg
491 ms
rusline.aero 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
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
Links do not have a discernible name
rusline.aero 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
rusline.aero 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
N/A
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rusline.aero 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), while the claimed language is Russian. Our system also found out that Rusline.aero 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.
rusline.aero
Open Graph description is not detected on the main page of Rusline. 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: