Tools & Wizards About Us
infobus.ru screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

infobus.ru

Билеты на автобус: покупай, заказывай, бронируй в INFOBUS

Page Load Speed

4.9 sec in total

First Response

420 ms

Resources Loaded

3.7 sec

Page Rendered

789 ms

infobus.ru screenshot

About Website

Click here to check amazing INFOBUS content for Russia. Otherwise, check out these important facts you probably never knew about infobus.ru

Автобусные билеты: онлайн продажа автобусных билетов по РБ, Европе и СНГ. Сравнение цен перевозчиков. Отзывы пассажиров о поездке. Легкая покупка.

Visit infobus.ru

Key Findings

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

Performance Metrics

infobus.ru performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

54/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value4.4 s

84/100

10%

Network Requests Diagram

infobus.ru

420 ms

infobus.by

1158 ms

38.jpg

797 ms

1715588591c0cc0006fedf5c27156513975fb15b6d.js

409 ms

23.jpg

811 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Infobus.ru, 92% (45 requests) were made to Infobus.by and 6% (3 requests) were made to Ws.bussystem.by. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Infobus.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 597.8 kB (14%)

Content Size

4.2 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Infobus.ru 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. 45% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 330.1 kB

  • Original 402.4 kB
  • After minification 390.0 kB
  • After compression 72.3 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 330.1 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 261.1 kB

  • Original 3.6 MB
  • After minification 3.4 MB

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. INFOBUS images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 6.6 kB

  • Original 151.2 kB
  • After minification 151.2 kB
  • After compression 144.6 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.

Requests Breakdown

Number of requests can be reduced by 7 (16%)

Requests Now

44

After Optimization

37

  • Images
  • JavaScript

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INFOBUS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

infobus.ru

infobus.ru

420 ms

infobus.by

infobus.by

1158 ms

38.jpg

38.jpg

797 ms

1715588591c0cc0006fedf5c27156513975fb15b6d.js

1715588591c0cc0006fedf5c27156513975fb15b6d.js

409 ms

23.jpg

23.jpg

811 ms

18.png

18.png

814 ms

logo.svg

logo.svg

360 ms

iconsprites.svg

iconsprites.svg

856 ms

arrow_white.svg

arrow_white.svg

402 ms

ru.svg

ru.svg

405 ms

All_front_active.svg

All_front_active.svg

403 ms

form-cross-icon.svg

form-cross-icon.svg

478 ms

6633b40a32a83.png

6633b40a32a83.png

797 ms

65f849ee4a1ab.png

65f849ee4a1ab.png

930 ms

6639f61c78011.png

6639f61c78011.png

800 ms

65e07ba1a4ed7.jpg

65e07ba1a4ed7.jpg

676 ms

65e07c4b8c0fd.png

65e07c4b8c0fd.png

1074 ms

65e07c92d1d74.png

65e07c92d1d74.png

811 ms

65e07cf682987.jpg

65e07cf682987.jpg

1457 ms

65e07d2b400e8.png

65e07d2b400e8.png

1729 ms

65e07d544cc4e.jpg

65e07d544cc4e.jpg

945 ms

65e07d63b7e1a.jpg

65e07d63b7e1a.jpg

1583 ms

6639f5ea76913.jpg

6639f5ea76913.jpg

1458 ms

660d689810f5e.png

660d689810f5e.png

1080 ms

6617afcb2e465.png

6617afcb2e465.png

1312 ms

6639f6462bbd1.png

6639f6462bbd1.png

1215 ms

warsaw-city-icon.svg

warsaw-city-icon.svg

1350 ms

path.svg

path.svg

1431 ms

vilnus-city-icon.svg

vilnus-city-icon.svg

1485 ms

random-5-city-icon.svg

random-5-city-icon.svg

1550 ms

prague-city-icon.svg

prague-city-icon.svg

1589 ms

berlin-city-icon.svg

berlin-city-icon.svg

1590 ms

random-4-city-icon.svg

random-4-city-icon.svg

1622 ms

left_top_app.svg

left_top_app.svg

1668 ms

right_bottom_app.svg

right_bottom_app.svg

1704 ms

IphoneX-01.png

IphoneX-01.png

1720 ms

app_store.svg

app_store.svg

1721 ms

google_play.svg

google_play.svg

1757 ms

arrow.png

arrow.png

1787 ms

phones_by.png

phones_by.png

1825 ms

Exo20-Bold.woff

Exo20-Bold.woff

1851 ms

Exo20-Regular.woff

Exo20-Regular.woff

1509 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1467 ms

menu-icon-white-instagram.svg

menu-icon-white-instagram.svg

1491 ms

menu-icon-white-telegram.svg

menu-icon-white-telegram.svg

1505 ms

menu-icon-white-facebook.svg

menu-icon-white-facebook.svg

1535 ms

pay_system_by.png

pay_system_by.png

1642 ms

loading_display_6_RU.svg

loading_display_6_RU.svg

1319 ms

loading_mobile_display_6_RU.svg

loading_mobile_display_6_RU.svg

1335 ms

Accessibility Review

infobus.ru accessibility score

88

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

Best Practices

infobus.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

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

High

Missing source maps for large first-party JavaScript

SEO Factors

infobus.ru SEO score

91

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 Infobus.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 Infobus.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

infobus.ru

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