6.5 sec in total
256 ms
6.1 sec
201 ms
Welcome to tallink.ee homepage info - get ready to check Tallink best content for Estonia right away, or after learning these important things about tallink.ee
Tallinki laevadel ootavad Sind parimad hinnad ja elamused. Viime Sind mugavalt Helsingisse, Stockholmi, Riiga, Turusse ja Ahvenamaale. Osta pilet siin.
Visit tallink.eeWe analyzed Tallink.ee page load time and found that the first response time was 256 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
tallink.ee performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value19.0 s
0/100
25%
Value16.9 s
0/100
10%
Value980 ms
28/100
30%
Value0.507
16/100
15%
Value17.9 s
4/100
10%
256 ms
511 ms
262 ms
1006 ms
608 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Tallink.ee, 64% (51 requests) were made to Ee.tallink.com and 14% (11 requests) were made to Res.cloudinary.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Sso.tallink.com.
Page size can be reduced by 378.2 kB (18%)
2.1 MB
1.8 MB
In fact, the total size of Tallink.ee main page is 2.1 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 191.3 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 51.9 kB, which is 23% 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 191.3 kB or 85% of the original size.
Potential reduce by 1.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. Tallink images are well optimized though.
Potential reduce by 185.6 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 185.6 kB or 23% of the original size.
Number of requests can be reduced by 45 (63%)
71
26
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 30 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
tallink.ee
256 ms
tallink.ee
511 ms
ee.tallink.com
262 ms
vali-reis
1006 ms
main.css
608 ms
combo
1206 ms
clay.css
870 ms
main.css
749 ms
combo
474 ms
js_loader_config
514 ms
combo
1789 ms
combo
1265 ms
combo
1265 ms
js_bundle_config
882 ms
combo
999 ms
main.css
1627 ms
combo
1126 ms
jquery-migrate-1.4.1.min.js
1265 ms
jquery-migrate-3.3.0.min.js
1331 ms
launch-ENaf7c1461e6c0454490c41c01dcff1d16.min.js
69 ms
sso.min.js
2092 ms
bookingEntry.css
641 ms
require.min.js
643 ms
main.js
1089 ms
lib.min.js
1390 ms
custom.min.js
1137 ms
common-object.js
1209 ms
common.shared.min.js
1211 ms
gtm.js
713 ms
jquery.cookie.js
128 ms
easyXDM.min.js
131 ms
masonry.pkgd.min.js
129 ms
slick.min.js
129 ms
bundle.production.min.js
606 ms
sdk.js
228 ms
1x1_transparent.png
878 ms
suvekampaania-desktop-est.jpg
270 ms
suvekampaania-mobile-est.jpg
324 ms
spring-brand-campaign-1264x768px-est.jpg
364 ms
spring-brand-campaign-912x1152px-est.jpg
367 ms
nublu-1264x768-est.jpg
429 ms
nublu-912x1152-est.jpg
365 ms
b2b-koosolekud-1264x768-est.jpg
366 ms
b2b-koosolekud-912x1152-est.jpg
366 ms
shopping-double-points-desktop-est.jpg
426 ms
shopping-double-points-mobile-est.jpg
427 ms
flag_et.svg
179 ms
pin.svg
176 ms
flag_int.svg
178 ms
chat.svg
177 ms
E-Store_432x200_et_EE.jpg
320 ms
b2b_432x200px_et_EE.jpg
428 ms
cargo_432x200px_et_EE.jpg
600 ms
club_one_432x200_et_EE.jpg
464 ms
white.gif
320 ms
shared.html
167 ms
GT-Walsheim-Pro-Regular.woff
729 ms
GT-Walsheim-Pro-Medium.woff
444 ms
GT-Walsheim-Pro-Bold.woff
692 ms
arrow_down_white.svg
431 ms
icon_search.svg
423 ms
close.svg
564 ms
logo_tallinksilja_white.svg
565 ms
main.js
170 ms
sdk.js
56 ms
cookies.js
213 ms
icon_facebook.svg
379 ms
icon_instagram.svg
379 ms
icon_youtube.svg
513 ms
icon_tiktok.svg
508 ms
icon_blog.svg
509 ms
icon_email.svg
511 ms
bookingEntry.js
1271 ms
157 ms
arrow-left-desktop-white.svg
255 ms
suveoo-erikruiis-desktop-est-2.jpg
64 ms
asset-manifest.json
136 ms
19 ms
1x1_transparent.png
127 ms
1x1_transparent.png
127 ms
tallink.ee 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
Image elements do not have [alt] attributes
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.
tallink.ee 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
tallink.ee SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Tap targets are not sized appropriately
ET
ET
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tallink.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and it matches the claimed language. Our system also found out that Tallink.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.
tallink.ee
Open Graph description is not detected on the main page of 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: