Access odessabus.com. МІЖНАРОДНИЙ АВТОВОКЗАЛ ОДЕСА

name

value

score

weighting

FCP (First Contentful Paint)

Value9.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

odessabus.com

470 ms

ua

1296 ms

bootstrap.css

752 ms

font-awesome.min.css

459 ms

main.old.css

588 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 91% of them (51 requests) were addressed to the original Odessabus.com, 2% (1 request) were made to Googleadservices.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Odessabus.com.

Content Size

1.5 MB

After Optimization

287.7 kB

In fact, the total size of Odessabus.com main page is 1.5 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. 20% of websites need less resources to load. Javascripts take 831.8 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 257.3 kB

Original 280.7 kB
After minification 169.3 kB
After compression 23.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 111.4 kB, which is 40% 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 257.3 kB or 92% of the original size.

Image Optimization

-12%

Potential reduce by 7.6 kB

Original 66.1 kB
After minification 58.5 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, Odessabus needs image optimization as it can save up to 7.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-80%

Potential reduce by 666.6 kB

Original 831.8 kB
After minification 772.8 kB
After compression 165.3 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 666.6 kB or 80% of the original size.

CSS Optimization

-86%

Potential reduce by 248.5 kB

Original 289.1 kB
After minification 230.3 kB
After compression 40.6 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. Odessabus.com needs all CSS files to be minified and compressed as it can save up to 248.5 kB or 86% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a valid value for its [lang] attribute.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

These are opportunities to improve keyboard navigation in your application.

High

Some elements have a [tabindex] value greater than 0

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

RU
Language Claimed

UA
Encoding

UTF-8

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

odessabus.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

МІЖНАРОДНИЙ АВТОВОКЗАЛ ОДЕСА

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

odessabus.com

ua

bootstrap.css

font-awesome.min.css

main.old.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

odessabus.com

ua

bootstrap.css

font-awesome.min.css

main.old.css

tooltips.css

owl.carousel.css

jquery.min.js

jquery-ui.min.js

owl.carousel.min.js

track

jquery.ui.datepicker-ua.js

jquery.validate.min.js

tooltipster.js

station_ua.js

bootstrap.js

jqueryui.min.js

script.js

conversion.js

gtm.js

language-nav-rus.png

language-nav-ukr.png

language-nav-gb.png

logo2018.png

contacts-phone.png

search-switch.png

search-dates.png

large_left.png

large_right.png

results-arrow-right.png

results-arrow-left.png

marshrut.svg

time-to.svg

price.svg

status.svg

time-from.svg

secondary-nav-1.png

secondary-nav-2.png

skype.png

social-nav-od.png

social-nav-tw.png

social-nav-fb.png

social-nav-vk.png