7.7 sec in total
677 ms
6.7 sec
356 ms
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.eeWe 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.
eurolines.ee performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value15.0 s
0/100
25%
Value8.9 s
15/100
10%
Value2,200 ms
6/100
30%
Value0.027
100/100
15%
Value12.7 s
13/100
10%
677 ms
59 ms
73 ms
81 ms
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 size can be reduced by 2.1 MB (37%)
5.5 MB
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.
Potential reduce by 56.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 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.
Potential reduce by 360.3 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, 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.
Potential reduce by 1.5 MB
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.
Potential reduce by 186.8 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.
Number of requests can be reduced by 48 (55%)
87
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.
677 ms
css
59 ms
css
73 ms
bootstrap.min.css
81 ms
font-awesome.min.css
49 ms
lightbox.css
118 ms
jquery-ui.min.css
233 ms
perfect-scrollbar.min.css
236 ms
styles.css
254 ms
jquery.js
360 ms
jquery-migrate.min.js
255 ms
style.css
256 ms
jquery.min.js
115 ms
js
111 ms
jquery.cycle2.min.js
354 ms
jquery.cycle2.swipe.min.js
352 ms
jquery.cycle2.carousel.min.js
449 ms
jquery.jcarousellite.min.js
354 ms
jquery-ui.min.js
737 ms
fastfix.js
530 ms
bootstrap.min.js
533 ms
lightbox.min.js
529 ms
perfect-scrollbar.jquery.min.js
531 ms
jquery.validate.min.js
623 ms
search.js
721 ms
jsData.js
1460 ms
flowtype.js
720 ms
scripts.js
866 ms
jquery.form.min.js
873 ms
scripts.js
876 ms
wp-embed.min.js
982 ms
wp-emoji-release.min.js
753 ms
analytics.js
18 ms
close.png
556 ms
loading.gif
571 ms
prev.png
650 ms
next.png
652 ms
eurolines_ee.png
776 ms
trip_from.png
693 ms
trip_to.png
695 ms
trip_date.png
762 ms
arrow-right-r.png
763 ms
img1.png
1182 ms
icon1.png
813 ms
Media-centre-2.png
1642 ms
mediacentericon.png
1127 ms
seimosbilietas4x4.jpg
1491 ms
seimosicon.png
1188 ms
vip-front.png
1491 ms
vipicon1.png
1365 ms
map.png
1446 ms
mapicon.png
1448 ms
sdk.js
332 ms
gtm.js
76 ms
Zemelapis-4-1024x643.png
2180 ms
collect
36 ms
letter_icon.svg
1493 ms
Vilnius-by-bus.png
2457 ms
slider_text_before.png
1531 ms
slider-text.png
1529 ms
uYKcPVoh6c5R0NpdEY5A-Q.woff
52 ms
DXI1ORHCpsQm3Vp6mXoaTRsxEYwM7FgeyaSgU71cLG0.woff
92 ms
k3k702ZOKiLJc3WVjuplzBsxEYwM7FgeyaSgU71cLG0.woff
96 ms
fontawesome-webfont.woff
42 ms
collect
119 ms
iframe_api
69 ms
fbevents.js
147 ms
watch.js
2 ms
collect
23 ms
slider_text_price.png
1519 ms
www-widgetapi.js
58 ms
ga-audiences
159 ms
234 ms
393 ms
Warsaw.png
2080 ms
ryga_foto-min.jpg
2077 ms
berlynas_foto-min.jpg
1800 ms
218 ms
xd_arbiter.php
286 ms
xd_arbiter.php
506 ms
directions_a_bg.png
1401 ms
elem1.png
1520 ms
elem2.png
1651 ms
2430 ms
2695 ms
elem3.png
1789 ms
elem4.png
1920 ms
mail.png
1918 ms
fb.png
1904 ms
ins.png
1937 ms
collect
42 ms
collect
26 ms
collect
26 ms
pager.png
123 ms
collect
23 ms
ga-audiences
25 ms
eurolines.ee accessibility score
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
ARIA input fields do not have accessible names
[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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eurolines.ee best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
eurolines.ee SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
N/A
ET
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.
eurolines.ee
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: