2.8 sec in total
282 ms
2.3 sec
203 ms
Click here to check amazing Eurolines content for Belgium. Otherwise, check out these important facts you probably never knew about eurolines.be
This domain may be for sale!
Visit eurolines.beWe analyzed Eurolines.be page load time and found that the first response time was 282 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
eurolines.be performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.3 s
42/100
25%
Value4.4 s
75/100
10%
Value330 ms
75/100
30%
Value0.258
48/100
15%
Value4.7 s
80/100
10%
282 ms
532 ms
125 ms
384 ms
230 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 77% of them (54 requests) were addressed to the original Eurolines.be, 6% (4 requests) were made to Google-analytics.com and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (833 ms) belongs to the original domain Eurolines.be.
Page size can be reduced by 321.4 kB (22%)
1.4 MB
1.1 MB
In fact, the total size of Eurolines.be main page is 1.4 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 975.8 kB which makes up the majority of the site volume.
Potential reduce by 56.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 21.5 kB, which is 33% 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.1 kB or 86% of the original size.
Potential reduce by 10.6 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. Eurolines images are well optimized though.
Potential reduce by 254.7 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 254.7 kB or 65% of the original size.
Number of requests can be reduced by 45 (71%)
63
18
The browser has sent 63 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 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
eurolines.be
282 ms
www.eurolines.be
532 ms
min.php
125 ms
min.php
384 ms
min.php
230 ms
min.php
254 ms
min.php
438 ms
header_bg.png
87 ms
home.png
89 ms
icon-NLD.jpg
86 ms
icon-ENG.jpg
87 ms
icon-FRA.jpg
89 ms
logo-header.jpg
178 ms
icon-booking.gif
179 ms
image.php
182 ms
image.php
182 ms
left.png
179 ms
right.png
180 ms
image.php
576 ms
btn_left.png
254 ms
btn_right.png
254 ms
image.php
493 ms
image.php
412 ms
image.php
413 ms
image.php
493 ms
image.php
411 ms
image.php
660 ms
image.php
747 ms
image.php
495 ms
image.php
576 ms
image.php
657 ms
transdev.png
577 ms
icon-main-navigation-white.png
650 ms
meta_agenticon.gif
651 ms
gtm.js
92 ms
ga.js
24 ms
EurolinesDefines.js
601 ms
JSONResponse.js
680 ms
bm.js
682 ms
BMGeneral.js
681 ms
Storage.js
685 ms
StepController.js
685 ms
FlowController.js
762 ms
Parser.js
763 ms
DictionaryController.js
763 ms
LanguageController.js
747 ms
BookingDetails.js
747 ms
steps_errors.js
748 ms
LabelService.php
833 ms
__utm.gif
17 ms
jsonrpc.js
809 ms
collect
65 ms
conversion_async.js
37 ms
analytics.js
12 ms
affiliate.min.js
47 ms
model.js
738 ms
Config.js.php
776 ms
ModuleController.js
741 ms
RequestValueParser.js
740 ms
btn_bg.png
815 ms
ga-audiences
73 ms
collect
17 ms
47 ms
collect
14 ms
fbevents.js
18 ms
ga-audiences
25 ms
315694818869089
12 ms
16 ms
19 ms
StepController1.js
85 ms
eurolines.be accessibility score
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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
eurolines.be 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eurolines.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Eurolines.be 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.be
Open Graph description is not detected on the main page of Eurolines. 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: