8.2 sec in total
254 ms
7.6 sec
299 ms
Click here to check amazing En Tallink content for Finland. Otherwise, check out these important facts you probably never knew about en.tallink.com
Tallink and Silja Line ships offer an access to the entire Baltic Sea region with the most modern fleet. Book a memorable mini cruise, overnight sea voyage or a comfortable and fast ferry crossing. Ci...
Visit en.tallink.comWe analyzed En.tallink.com page load time and found that the first response time was 254 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
en.tallink.com performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value28.5 s
0/100
25%
Value15.5 s
0/100
10%
Value1,100 ms
23/100
30%
Value0.218
57/100
15%
Value27.8 s
0/100
10%
254 ms
524 ms
898 ms
1131 ms
627 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 49% of them (62 requests) were addressed to the original En.tallink.com, 41% (52 requests) were made to Booking.tallink.com and 3% (4 requests) were made to Sso.tallink.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain En.tallink.com.
Page size can be reduced by 455.4 kB (20%)
2.3 MB
1.8 MB
In fact, the total size of En.tallink.com main page is 2.3 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 223.8 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 63.4 kB, which is 25% 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 223.8 kB or 87% of the original size.
Potential reduce by 67.9 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. En Tallink images are well optimized though.
Potential reduce by 163.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 163.7 kB or 22% of the original size.
Number of requests can be reduced by 90 (76%)
118
28
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of En Tallink. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
en.tallink.com
254 ms
en.tallink.com
524 ms
book-a-cruise
898 ms
combo
1131 ms
main.css
627 ms
clay.css
911 ms
main.css
783 ms
combo
405 ms
js_loader_config
397 ms
combo
751 ms
combo
746 ms
combo
1301 ms
js_bundle_config
1234 ms
combo
1235 ms
main.css
1046 ms
closest.js
1042 ms
core-js-bundle.min.js
1304 ms
css.escape.js
1184 ms
fetch.js
1256 ms
svg.contains.js
1308 ms
uint16array.slice.js
1355 ms
combo
1415 ms
picturefill.min.js
1418 ms
jquery-migrate-1.4.1.min.js
1427 ms
jquery-migrate-3.3.0.min.js
1434 ms
launch-ENaf7c1461e6c0454490c41c01dcff1d16.min.js
20 ms
sso.min.js
1682 ms
bookingEntry.css
622 ms
require.min.js
641 ms
main.js
1193 ms
lib.min.js
1706 ms
custom.min.js
1405 ms
common-object.js
1292 ms
common.shared.min.js
1301 ms
aui_deprecated.css
389 ms
custom-extra.css
404 ms
gtm.js
666 ms
jquery.cookie.js
132 ms
easyXDM.min.js
132 ms
masonry.pkgd.min.js
132 ms
slick.min.js
132 ms
bundle.production.min.js
651 ms
sdk.js
129 ms
flag_int_white.svg
163 ms
pin.svg
128 ms
flag_int.svg
159 ms
chat.svg
160 ms
3a22c941-439c-2e2b-cfd2-b3a4e859f842
161 ms
464x224_route-map_Liferay.png
565 ms
4a78d094-eebb-4070-baf1-ad6657dc916a
450 ms
2022+general_megamenu_E-Store_432x200_ENG.jpg
270 ms
430_megamenu_05.jpg
262 ms
08_2023_Shuttle-carousel-banner.jpg
1180 ms
632x384_tallink_BQ_-STO-TAL.jpg
1868 ms
white.gif
450 ms
shared.html
146 ms
persistence
332 ms
GT-Walsheim-Pro-Regular.woff
447 ms
GT-Walsheim-Pro-Medium.woff
622 ms
GT-Walsheim-Pro-Bold.woff
531 ms
arrow_down_white.svg
523 ms
sdk.js
41 ms
icon_search.svg
495 ms
close.svg
584 ms
logo_tallinksilja_white.svg
618 ms
main.js
142 ms
cookies.js
310 ms
icon_cin.svg
459 ms
icon_wheelchair.svg
536 ms
icon_facebook.svg
547 ms
icon_instagram.svg
584 ms
icon_youtube.svg
585 ms
icon_email.svg
666 ms
bookingEntry.js
1245 ms
41 ms
arrow-left-desktop-white.svg
340 ms
asset-manifest.json
131 ms
28 ms
bookingEntry.js
126 ms
SearchPanelView.js
244 ms
CalendarView.js
250 ms
locale.js
364 ms
pubsub.js
373 ms
AttributeValidator.js
375 ms
env.js
378 ms
VoyageType.js
374 ms
booking.tallink.com
505 ms
booking.tallink.com
381 ms
SearchPanelViewModel.js
256 ms
BookingModel.js
386 ms
bookingModelHelper.js
257 ms
DateLocale.js
376 ms
format.js
381 ms
jquery.continuousCalendar.js
381 ms
booking.tallink.com
407 ms
localeFunctions.js
386 ms
pubsub.js
377 ms
DateTime.js
370 ms
BookingRoutes.js
376 ms
Passengers.js
367 ms
rx.util.js
369 ms
booking.tallink.com
399 ms
booking.tallink.com
274 ms
FI.js
252 ms
EN.js
268 ms
AU.js
518 ms
ET.js
519 ms
RU.js
522 ms
SV.js
518 ms
LV.js
521 ms
LT.js
518 ms
DE.js
638 ms
ZH.js
642 ms
JA.js
641 ms
KO.js
637 ms
SailDirection.js
642 ms
ShoppingCruiseHelper.js
642 ms
DateFormat.js
755 ms
DateRange.js
760 ms
CalendarBody.js
761 ms
RangeEvents.js
766 ms
SingleDateEvents.js
764 ms
booking.tallink.com
786 ms
booking.tallink.com
151 ms
booking.tallink.com
162 ms
booking.tallink.com
144 ms
en.tallink.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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 valid value for its [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.
en.tallink.com 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
Missing source maps for large first-party JavaScript
en.tallink.com 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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise En.tallink.com 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 En.tallink.com 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.
en.tallink.com
Open Graph description is not detected on the main page of En Tallink. 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: