Tools & Wizards About Us
en.travelline.ru screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

en.travelline.ru

TravelLine — Единая платформа для гостиничного бизнеса

Page Load Speed

9.1 sec in total

First Response

648 ms

Resources Loaded

7.2 sec

Page Rendered

1.2 sec

en.travelline.ru screenshot

About Website

Visit en.travelline.ru now to see the best up-to-date En Travel Line content for Russia and also check out these interesting facts you probably never knew about en.travelline.ru

Разработчик IT-инструментов для отелей, гостиниц, хостелов, санаториев, апартаментов: модуль онлайн-бронирования TL: Booking Engine, инструмент для управления каналами продаж TL: Channel Manager, инст...

Visit en.travelline.ru

Key Findings

We analyzed En.travelline.ru page load time and found that the first response time was 648 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

en.travelline.ru performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.196

63/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

en.travelline.ru

648 ms

www.travelline.ru

1043 ms

style.min.css

539 ms

optimize.js

45 ms

page_797edafc71c199737bebfa23b252cbbf_v1.css

401 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original En.travelline.ru, 84% (78 requests) were made to Travelline.ru and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Travelline.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 225.0 kB (13%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of En.travelline.ru main page is 1.7 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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 82.9 kB

  • Original 98.5 kB
  • After minification 78.1 kB
  • After compression 15.6 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.3 kB, which is 21% 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 82.9 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 41.7 kB

  • Original 1.0 MB
  • After minification 970.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. En Travel Line images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 51.5 kB

  • Original 435.7 kB
  • After minification 435.2 kB
  • After compression 384.2 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 51.5 kB or 12% of the original size.

CSS Optimization

-27%

Potential reduce by 48.9 kB

  • Original 179.1 kB
  • After minification 179.0 kB
  • After compression 130.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. En.travelline.ru needs all CSS files to be minified and compressed as it can save up to 48.9 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (33%)

Requests Now

83

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.travelline.ru

en.travelline.ru

648 ms

www.travelline.ru

www.travelline.ru

1043 ms

style.min.css

style.min.css

539 ms

optimize.js

optimize.js

45 ms

page_797edafc71c199737bebfa23b252cbbf_v1.css

page_797edafc71c199737bebfa23b252cbbf_v1.css

401 ms

template_93cddc06c1d15330bb311de02ea47dbd_v1.css

template_93cddc06c1d15330bb311de02ea47dbd_v1.css

450 ms

core.min.js

core.min.js

1646 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

1646 ms

page_e272fde7a7db1553770b888782786550_v1.js

page_e272fde7a7db1553770b888782786550_v1.js

1646 ms

jquery.stellar.js

jquery.stellar.js

1644 ms

skrollr.min.js

skrollr.min.js

1644 ms

magnific.min.js

magnific.min.js

1644 ms

slick.min.js

slick.min.js

1871 ms

demo-provider-wizard-loader.js

demo-provider-wizard-loader.js

1867 ms

lazyvideo.min.js

lazyvideo.min.js

1773 ms

main.min.js

main.min.js

2162 ms

index-QAvtXYqw.js

index-QAvtXYqw.js

2262 ms

gtm.js

gtm.js

1131 ms

tag.js

tag.js

931 ms

ba.js

ba.js

281 ms

ns.html

ns.html

113 ms

rtrg

rtrg

579 ms

LOGO_TL_Portal-nologo.svg

LOGO_TL_Portal-nologo.svg

272 ms

LOGO_TL_Portal_logo_only.svg

LOGO_TL_Portal_logo_only.svg

357 ms

traingles_sprite.png

traingles_sprite.png

456 ms

main-menu-icons_new1.png

main-menu-icons_new1.png

407 ms

new-first-4-mob.png

new-first-4-mob.png

1036 ms

tl-rosreestr2.png

tl-rosreestr2.png

557 ms

tl-rfrit3.png

tl-rfrit3.png

615 ms

4vrow1.png

4vrow1.png

804 ms

main-3-111.png

main-3-111.png

838 ms

9-support-13.png

9-support-13.png

1155 ms

9-support-23.png

9-support-23.png

806 ms

TL-arrow1.svg

TL-arrow1.svg

855 ms

TL-sanatorium1.svg

TL-sanatorium1.svg

972 ms

TL-mini1.svg

TL-mini1.svg

990 ms

TL-hotel1.svg

TL-hotel1.svg

1055 ms

TL-apartaments1.svg

TL-apartaments1.svg

1089 ms

TL-zoibo1.svg

TL-zoibo1.svg

1140 ms

TL-lager1.svg

TL-lager1.svg

1188 ms

TL-car.png

TL-car.png

1239 ms

TL-bus1.png

TL-bus1.png

1288 ms

review_unis.png

review_unis.png

1339 ms

review_img_b.png

review_img_b.png

1522 ms

review_kruchinskyi.png

review_kruchinskyi.png

1459 ms

review_img_g.png

review_img_g.png

1489 ms

review_sahibgareeva.png

review_sahibgareeva.png

1539 ms

review_img_p.png

review_img_p.png

1589 ms

galochkin77.png

galochkin77.png

1903 ms

googleplay.png

googleplay.png

1688 ms

appstore.png

appstore.png

1737 ms

new-first-4.png

new-first-4.png

1727 ms

tl-platfrom-sprite.png

tl-platfrom-sprite.png

1775 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

1910 ms

OpenSans-Light.woff

OpenSans-Light.woff

1876 ms

OpenSans-SemiBold.woff

OpenSans-SemiBold.woff

1794 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

1903 ms

RobotoCondensed-Regular.woff

RobotoCondensed-Regular.woff

1868 ms

RobotoCondensed-Light.woff

RobotoCondensed-Light.woff

1871 ms

RobotoCondensed-Bold.woff

RobotoCondensed-Bold.woff

1742 ms

call.tracker.js

call.tracker.js

708 ms

hotels-on-main2.png

hotels-on-main2.png

1872 ms

main-4-11.svg

main-4-11.svg

1740 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

209 ms

bx_stat

bx_stat

187 ms

1775 ms

main-4-12.svg

main-4-12.svg

1724 ms

rtrg

rtrg

190 ms

main-4-13.svg

main-4-13.svg

1585 ms

main-4-14.svg

main-4-14.svg

1659 ms

main-4-15.svg

main-4-15.svg

1650 ms

main-4-16.svg

main-4-16.svg

1687 ms

main-4-17.svg

main-4-17.svg

1614 ms

advert.gif

advert.gif

669 ms

main-4-18.svg

main-4-18.svg

1650 ms

emoji--support.png

emoji--support.png

1653 ms

hotels_anim_bg4.png

hotels_anim_bg4.png

1682 ms

tl-bubble-top-g-l.png

tl-bubble-top-g-l.png

1698 ms

tl-bubble-top-g.png

tl-bubble-top-g.png

1697 ms

tl-bubble-top-g-r.png

tl-bubble-top-g-r.png

1735 ms

main-expert-mob.jpg

main-expert-mob.jpg

1883 ms

main-tg2.png

main-tg2.png

1750 ms

tg-ico2.png

tg-ico2.png

1755 ms

chat-face11.png

chat-face11.png

1751 ms

chat-arrow.png

chat-arrow.png

1679 ms

chat-face21.png

chat-face21.png

1701 ms

chat-face31.png

chat-face31.png

1716 ms

footer-logo.svg

footer-logo.svg

1749 ms

footer-social-sprite2.png

footer-social-sprite2.png

1749 ms

sync_cookie_image_decide

sync_cookie_image_decide

134 ms

1

1

141 ms

js

js

55 ms

index-DZ9xdH6G.css

index-DZ9xdH6G.css

953 ms

Accessibility Review

en.travelline.ru accessibility score

73

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

en.travelline.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

en.travelline.ru SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise En.travelline.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that En.travelline.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.

Social Sharing Optimization

en.travelline.ru

Open Graph data is detected on the main page of En Travel Line. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: