5.8 sec in total
231 ms
4.9 sec
702 ms
Visit cruise-express.be now to see the best up-to-date Cruise Express content and also check out these interesting facts you probably never knew about cruise-express.be
Cruise Express is a shuttle service from Zeebruges to Bruges. Our shuttle service starts immediately after disembarkation and has a bus running to Bruges every half hour.
Visit cruise-express.beWe analyzed Cruise-express.be page load time and found that the first response time was 231 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cruise-express.be performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value2.6 s
86/100
25%
Value21.6 s
0/100
10%
Value45,810 ms
0/100
30%
Value1.111
1/100
15%
Value55.9 s
0/100
10%
231 ms
723 ms
1113 ms
119 ms
92 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 63% of them (40 requests) were addressed to the original Cruise-express.be, 11% (7 requests) were made to Static.olark.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Knrpc.olark.com.
Page size can be reduced by 292.5 kB (53%)
551.7 kB
259.2 kB
In fact, the total size of Cruise-express.be main page is 551.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 210.7 kB which makes up the majority of the site volume.
Potential reduce by 49.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 18.9 kB, which is 31% 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 49.5 kB or 82% of the original size.
Potential reduce by 0 B
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. Cruise Express images are well optimized though.
Potential reduce by 137.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 137.4 kB or 65% of the original size.
Potential reduce by 105.5 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. Cruise-express.be needs all CSS files to be minified and compressed as it can save up to 105.5 kB or 82% of the original size.
Number of requests can be reduced by 21 (38%)
55
34
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cruise Express. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
cruise-express.be
231 ms
cruise-express.be
723 ms
1113 ms
gtm.js
119 ms
sdk.js
92 ms
BokunWidgetsLoader.js
927 ms
router.js
277 ms
routing
545 ms
jquery.min.js
278 ms
frontend.js
657 ms
logo.svg
497 ms
moneystamp_en.png
850 ms
IMABUS.png
870 ms
bruges.png
869 ms
boog.svg
583 ms
bus.svg
624 ms
excursie.svg
851 ms
taxi.svg
851 ms
signpost_en.png
854 ms
folder.png
857 ms
betaalmogelijkheden.png
867 ms
css
275 ms
sdk.js
141 ms
analytics.js
257 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
80 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
87 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
129 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
140 ms
collect
73 ms
collect
115 ms
loader0.js
50 ms
update.min.js
146 ms
star-on0.svg
142 ms
star-off0.svg
139 ms
star-off.svg
104 ms
app.js
5 ms
7365-486-10-9755.js
192 ms
frontend.css
311 ms
c
1379 ms
application2.js
691 ms
home.svg
435 ms
stempel_en.svg
436 ms
call.svg
419 ms
email.svg
422 ms
down.svg
420 ms
vlaggetje.png
422 ms
busje.svg
578 ms
tickets-bl.svg
575 ms
clock0.svg
578 ms
ship.jpg
715 ms
signs-1.svg
563 ms
brugge.jpg
580 ms
blueslant.svg
728 ms
chat.svg
737 ms
home0.svg
737 ms
call0.svg
720 ms
email0.svg
718 ms
clock.svg
792 ms
slick.woff
861 ms
fontawesome-webfont.woff
340 ms
storage.html
2 ms
storage.js
5 ms
visits
259 ms
jquery.js
127 ms
cruise-express.be 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-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
cruise-express.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
cruise-express.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cruise-express.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cruise-express.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.
cruise-express.be
Open Graph data is detected on the main page of Cruise Express. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: