10.6 sec in total
272 ms
9.9 sec
406 ms
Visit scandlines.eu now to see the best up-to-date Scandlines content and also check out these interesting facts you probably never knew about scandlines.eu
Sail with Scandlines via Puttgarden-Rødby or Rostock-Gedser and travel fast and easy between Germany and Denmark. Read more and book your ticket here.
Visit scandlines.euWe analyzed Scandlines.eu page load time and found that the first response time was 272 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
scandlines.eu performance score
272 ms
280 ms
740 ms
213 ms
9 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Scandlines.eu, 61% (46 requests) were made to Scandlines.com and 16% (12 requests) were made to Booking.scandlines.com. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Booking.scandlines.com.
Page size can be reduced by 812.2 kB (23%)
3.5 MB
2.7 MB
In fact, the total size of Scandlines.eu main page is 3.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. 50% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 88.9 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 20.9 kB, which is 20% 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 88.9 kB or 87% of the original size.
Potential reduce by 291.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. Scandlines images are well optimized though.
Potential reduce by 276.8 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 276.8 kB or 67% of the original size.
Potential reduce by 155.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. Scandlines.eu needs all CSS files to be minified and compressed as it can save up to 155.1 kB or 82% of the original size.
Number of requests can be reduced by 29 (41%)
71
42
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Scandlines. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
scandlines.eu
272 ms
www.scandlines.eu
280 ms
www.scandlines.com
740 ms
VisitorIdentification.aspx
213 ms
jquery-ui.css
9 ms
scandlines-dk-min.css
778 ms
scandlines-xx-min.css
582 ms
jquery.min.js
12 ms
jquery-ui.min.js
13 ms
scandlines-dk-min.js
764 ms
scandlines-xx-min.js
399 ms
WebResource.axd
485 ms
ScriptResource.axd
687 ms
ScriptResource.axd
767 ms
405 ms
print.css
195 ms
grd-bg.ashx
292 ms
gtm.js
81 ms
cloud.ashx
822 ms
sea_updated.ashx
752 ms
logo.ashx
279 ms
scl-sprite.png
656 ms
en-flag.jpg
553 ms
sv-flag-active.jpg
547 ms
sprite-scl-all.png
923 ms
top-menu-blue-bg.jpg
827 ms
express-link.ashx
1032 ms
logo.ashx
953 ms
trafficInfoIcon.png
1298 ms
tabbutton.png
1090 ms
new_map_UK.ashx
3086 ms
dp2.specificclick.net
180 ms
pin.png
1109 ms
logobordershop.gif
1240 ms
Banner_934x211_uk.ashx
1875 ms
Book_Now-engl-582x485_final.ashx
1817 ms
337x235_editorial_01_1korr.ashx
1774 ms
btn-search-blue.png
1441 ms
337x235_editorial_02_1korr.ashx
2025 ms
COM211x211_bundteaser_04.ashx
2003 ms
211x211_bundteaser_03_1korr.ashx
2424 ms
211x211_bundteaser_01_1korr.ashx
2479 ms
211x211-Travel-Shop1.ashx
2507 ms
8C06D7630FB04BEFBAA0E2E149825692.ashx
2286 ms
sprite2.png
2613 ms
cookiebadge.min.js
299 ms
scandlinesmobilenavigation
2855 ms
preloader.gif
2658 ms
icons.png
2710 ms
analytics.js
4 ms
collect
2 ms
collect
46 ms
BookingStarter3.aspx
582 ms
sprites.png
112 ms
bapi
46 ms
bookingstarter3
6166 ms
lang_en_btn.jpg
279 ms
lang_de_btn.jpg
276 ms
lang_da_btn.jpg
288 ms
lang_sv_btn.jpg
288 ms
lang_pl_btn.jpg
283 ms
lang_nl_btn.jpg
466 ms
BookingStarter
105 ms
BookingStarter
609 ms
BookingStarter3
312 ms
gtm.js
79 ms
radio.png
103 ms
calendar-background.png
103 ms
FindRejse.png
104 ms
ui-bg_highlight-soft_75_cccccc_1x100.png
174 ms
ui-icons_222222_256x240.png
176 ms
ui-bg_glass_75_e6e6e6_1x400.png
177 ms
ui-bg_glass_55_fbf9ee_1x400.png
273 ms
analytics.js
23 ms
80c422dd-a9cc-45e1-857f-40ffa73f5e36.js
31 ms
collect
3 ms
scandlines.eu SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Scandlines.eu 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 Scandlines.eu 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.
scandlines.eu
Open Graph description is not detected on the main page of Scandlines. 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: