Tools & Wizards About Us
poezda.by screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

poezda.by

Расписание движения поездов. Бронирование и заказ жд билетов. - Poezda.by

Page Load Speed

7.6 sec in total

First Response

502 ms

Resources Loaded

7 sec

Page Rendered

93 ms

poezda.by screenshot

About Website

Click here to check amazing Poezda content for Belarus. Otherwise, check out these important facts you probably never knew about poezda.by

Информация о расписании движения поездов от станции Минск, стоимости железнодорожных билетов, правилах проезда, возможность бронирования, заказа жд билетов через Интернет

Visit poezda.by

Key Findings

We analyzed Poezda.by page load time and found that the first response time was 502 ms and then it took 7.1 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

poezda.by performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value26.8 s

0/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

poezda.by

502 ms

jquery.min.js

254 ms

jquery-noconflict.js

219 ms

jquery-migrate.min.js

223 ms

bootstrap.css

344 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 66% of them (23 requests) were addressed to the original Poezda.by, 9% (3 requests) were made to Fonts.googleapis.com and 9% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Poezda.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 395.9 kB (66%)

Content Size

597.1 kB

After Optimization

201.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Poezda.by main page is 597.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. 35% of websites need less resources to load. Images take 363.7 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 5.9 kB

  • Original 8.3 kB
  • After minification 7.1 kB
  • After compression 2.5 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 1.2 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 5.9 kB or 71% of the original size.

Image Optimization

-100%

Potential reduce by 362.6 kB

  • Original 363.7 kB
  • After minification 1.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, Poezda needs image optimization as it can save up to 362.6 kB or 100% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 10.6 kB

  • Original 165.2 kB
  • After minification 165.2 kB
  • After compression 154.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.

CSS Optimization

-28%

Potential reduce by 16.8 kB

  • Original 59.9 kB
  • After minification 59.8 kB
  • After compression 43.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. Poezda.by needs all CSS files to be minified and compressed as it can save up to 16.8 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (50%)

Requests Now

30

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

poezda.by

poezda.by

502 ms

jquery.min.js

jquery.min.js

254 ms

jquery-noconflict.js

jquery-noconflict.js

219 ms

jquery-migrate.min.js

jquery-migrate.min.js

223 ms

bootstrap.css

bootstrap.css

344 ms

theme.css

theme.css

361 ms

custom.css

custom.css

371 ms

uikit.js

uikit.js

330 ms

autocomplete.js

autocomplete.js

332 ms

search.js

search.js

379 ms

sticky.js

sticky.js

440 ms

Chart.js

Chart.js

554 ms

social.js

social.js

456 ms

theme.js

theme.js

478 ms

css

css

34 ms

css

css

50 ms

css

css

56 ms

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

645 ms

logo.png

logo.png

251 ms

contacts3.png

contacts3.png

112 ms

east.png

east.png

237 ms

west.png

west.png

225 ms

balt.png

balt.png

219 ms

nord.png

nord.png

5936 ms

south.png

south.png

331 ms

poezda.by

poezda.by

390 ms

tag.js

tag.js

973 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

28 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

30 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

427 ms

advert.gif

advert.gif

705 ms

sync_cookie_image_decide

sync_cookie_image_decide

144 ms

sync_cookie_image_decide

sync_cookie_image_decide

141 ms

1

1

145 ms

Accessibility Review

poezda.by accessibility score

89

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.

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

Links do not have a discernible name

Best Practices

poezda.by 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

poezda.by SEO score

99

Search Engine Optimization Advices

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 Poezda.by 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 Poezda.by 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

poezda.by

Open Graph description is not detected on the main page of Poezda. 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: