Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

eurolines.ee

Eurolines

Page Load Speed

7.7 sec in total

First Response

677 ms

Resources Loaded

6.7 sec

Page Rendered

356 ms

eurolines.ee screenshot

About Website

Visit eurolines.ee now to see the best up-to-date Eurolines content and also check out these interesting facts you probably never knew about eurolines.ee

Reisigem Euroopas bussidega

Visit eurolines.ee

Key Findings

We analyzed Eurolines.ee page load time and found that the first response time was 677 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 80% of websites can load faster.

Performance Metrics

eurolines.ee performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

677 ms

css

59 ms

css

73 ms

bootstrap.min.css

81 ms

font-awesome.min.css

49 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Eurolines.ee, 6% (6 requests) were made to Google-analytics.com and 3% (3 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Eurolines.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (37%)

Content Size

5.5 MB

After Optimization

3.5 MB

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

HTML Optimization

-79%

Potential reduce by 56.4 kB

  • Original 71.5 kB
  • After minification 63.4 kB
  • After compression 15.1 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 8.1 kB, which is 11% 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 56.4 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 360.3 kB

  • Original 3.2 MB
  • After minification 2.8 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. Obviously, Eurolines needs image optimization as it can save up to 360.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 1.5 MB

  • Original 2.1 MB
  • After minification 2.0 MB
  • After compression 590.4 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 1.5 MB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 186.8 kB

  • Original 228.0 kB
  • After minification 217.6 kB
  • After compression 41.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. Eurolines.ee needs all CSS files to be minified and compressed as it can save up to 186.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (55%)

Requests Now

87

After Optimization

39

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

Accessibility Review

eurolines.ee accessibility score

76

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 input fields do not have accessible names

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

eurolines.ee best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

eurolines.ee SEO score

85

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    ET

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eurolines.ee 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 Estonian. Our system also found out that Eurolines.ee 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

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