9 sec in total
362 ms
8.3 sec
333 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 362 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tallink.ee performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value24.2 s
0/100
25%
Value15.9 s
0/100
10%
Value3,600 ms
1/100
30%
Value0.614
10/100
15%
Value28.0 s
0/100
10%
362 ms
830 ms
562 ms
223 ms
235 ms
Our browser made a total of 205 requests to load all elements on the main page. We found that 85% of them (174 requests) were addressed to the original Tallink.ee, 4% (9 requests) were made to Booking.tallink.com and 1% (3 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Tallink.ee.
Page size can be reduced by 1.7 MB (59%)
2.9 MB
1.2 MB
In fact, the total size of Tallink.ee main page is 2.9 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 150.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 63.3 kB, which is 37% 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 150.5 kB or 87% of the original size.
Potential reduce by 29.8 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 751.1 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 751.1 kB or 69% of the original size.
Potential reduce by 792.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. Tallink.ee needs all CSS files to be minified and compressed as it can save up to 792.5 kB or 86% of the original size.
Number of requests can be reduced by 160 (81%)
198
38
The browser has sent 198 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 40 to 1 for JavaScripts and from 100 to 1 for CSS and as a result speed up the page load time.
www.tallink.ee
362 ms
vali-reis
830 ms
aui.css
562 ms
main.css
223 ms
main.css
235 ms
main.css
237 ms
main.css
233 ms
main.css
322 ms
main.css
332 ms
main.css
348 ms
barebone.jsp
1014 ms
main.js
464 ms
navigation.js
433 ms
main.js
445 ms
main.js
463 ms
main.css
542 ms
bookingEntry.css
767 ms
require.min.js
682 ms
jquery.animate-enhanced.min.js
367 ms
jquery.flexslider-min.js
373 ms
jquery.lazyload.min.js
371 ms
storyjs-embed.js
447 ms
jquery.dd.js
466 ms
jquery.fancybox-2.0.3.min.js
463 ms
jquery.ui.datepicker.min.js
490 ms
jquery-ui-autocomplete.min.js
491 ms
jquery.ui.core.min.js
556 ms
plugins.js
576 ms
script.js
901 ms
main.js
610 ms
upload.js
608 ms
main.js
663 ms
aui_deprecated.css
683 ms
portal_1.css
716 ms
portal_2.css
722 ms
taglib_1.css
767 ms
taglib_2.css
790 ms
accessibility.css
836 ms
add_content.css
140 ms
asset_category_selector.css
165 ms
asset_column.css
187 ms
auto_row.css
195 ms
device_preview.css
237 ms
edit_layout.css
253 ms
flyout.css
273 ms
forms.css
297 ms
generic_portal.css
618 ms
generic_portlet.css
304 ms
header_row.css
366 ms
javascript_template.css
367 ms
notifications.css
383 ms
openid.css
413 ms
page_settings.css
420 ms
panel_component.css
501 ms
panel_page.css
480 ms
pagination.css
502 ms
panel_pagination.css
520 ms
portlet_css_editor.css
528 ms
portlet_item.css
593 ms
position_helper.css
613 ms
preview.css
610 ms
rich_editor.css
628 ms
search_combobox.css
649 ms
separator.css
704 ms
tag_selector.css
719 ms
toolbar.css
720 ms
translation_manager.css
724 ms
tree.css
734 ms
undo_manager.css
756 ms
uploader.css
777 ms
app_view_common.css
763 ms
app_view_entry.css
763 ms
app_view_navigation_item.css
728 ms
app_view_search_entry.css
715 ms
app_view_toolbar.css
716 ms
asset_categories_summary.css
768 ms
asset_links.css
764 ms
button.css
756 ms
calendar.css
728 ms
captcha.css
713 ms
categorization_filter.css
717 ms
ddm_template.css
761 ms
diff.css
757 ms
diff_html.css
705 ms
discussion.css
717 ms
flags.css
694 ms
form_navigator.css
689 ms
header.css
754 ms
icon.css
691 ms
icon_help.css
679 ms
icon_list.css
682 ms
icon_menu.css
676 ms
input_localized.css
683 ms
input_move_boxes.css
686 ms
field_wrapper.css
678 ms
input_permissions.css
676 ms
input_repeat.css
681 ms
language.css
681 ms
logo_selector.css
672 ms
navbar.css
684 ms
preview.css
679 ms
ratings.css
684 ms
rss_settings.css
676 ms
search_container.css
716 ms
search_iterator.css
692 ms
search_toggle.css
683 ms
sites_directory.css
681 ms
social_activities.css
682 ms
social_bookmarks.css
680 ms
tags_summary.css
735 ms
trash_common.css
712 ms
user_display.css
678 ms
webdav.css
689 ms
workflow_status.css
685 ms
base.css
118 ms
application.css
114 ms
layout.css
113 ms
dockbar.css
118 ms
navigation.css
124 ms
portlet.css
120 ms
extras.css
224 ms
custom.css
849 ms
jquery-1.8.3.min.js
232 ms
Bootstrap.js
19 ms
frosmo.easy.js
262 ms
serverComponent.php
12 ms
f3e44d8a4314c0ebd17c09030dd3194c.js
4 ms
sessioncam.recorder.js
23 ms
analytics.js
24 ms
conversion_async.js
13 ms
74 ms
config.aspx
148 ms
43 ms
jquery.cookie.js
111 ms
tallink_ee.js
92 ms
easyXDM.min.js
115 ms
optimizerApi
235 ms
optimizerApi
242 ms
bg_nav_1st.png
156 ms
bg_nav_1st_link.png
156 ms
bg_nav_1st_link_active.png
157 ms
bg_nav_1st_login.png
160 ms
spacer.png
160 ms
search.png
158 ms
f3075d96-fc30-4621-a376-e3c1aac70f19
332 ms
bb1abe69-072b-4099-8bb1-da30d87a0015
553 ms
bd8cabe1-c980-4319-bcfe-5f2fb2f28211
424 ms
e50b0acc-c97c-4169-8631-abfedd03f8dd
454 ms
white.gif
231 ms
1c538faa-f664-4ec7-bded-cae15b0a5a9d
233 ms
dc52d059-6fce-43dc-9184-dc4e05112ea7
350 ms
15d2b3de-2981-465d-bdd9-da91ecdd9527
355 ms
StagSansLCWeb-Book.woff
552 ms
StagSansLCWeb-Medium.woff
706 ms
layout_set_logo
508 ms
bg_nav_2nd_link.png
522 ms
bg_nav_2nd_link_active.png
581 ms
bg_nav_2nd_marker.png
601 ms
bg_nav_2nd_link_clubone.png
630 ms
bg_nav_3rd_shadow.png
646 ms
bg_nav_3rd_li.gif
653 ms
bg_nav_4th_bg_bottom.png
692 ms
main.js
138 ms
bg_fp_carousel_mid.png
697 ms
bg_top_lmo.png
721 ms
bg_section_alt_top.png
752 ms
shadow_outer_top.png
753 ms
sprites.png
784 ms
circle_large.png
795 ms
bg_shadow_3_boxs.png
1144 ms
bg_button_priority_l.png
828 ms
bg_button_priority_r.png
841 ms
bg_divider_fd.png
848 ms
bg_footer.png
891 ms
icons_footer_cin.png
1086 ms
01cf1ad1a9da42a48b0aa56989d74326
1506 ms
collect
58 ms
397 ms
StagSansLCWeb-Light.woff
977 ms
973 ms
icons_footer_acc.png
970 ms
icons_footer.png
970 ms
bg_dd_arrow_high.png
970 ms
bg_dd_grad.png
973 ms
5174.js
9 ms
bookingEntry.js
589 ms
et_EE.png
902 ms
bg_control_nav.png
929 ms
bg_direction_nav.png
847 ms
be68afc5-7fb2-40fa-b628-670d61dd6f29
850 ms
a121584a-6142-4942-b99f-faf363ac603d
859 ms
be912346-3133-4862-b439-3472a87ef794
910 ms
6ad30aaf-0707-43dc-9b98-c7c5ca0dbcc2
831 ms
201 ms
e5edf054-3e79-4f57-b9d3-a20b84306be5
2219 ms
f18ebf28-f9b9-4b5b-875f-514cede5542c
869 ms
common.js
120 ms
booking.js
121 ms
spinner-s64a449eeb6.png
145 ms
search-button-left.png
129 ms
search-button-right.png
128 ms
pageconfig
42 ms
pageview
6 ms
s
30 ms
u
24 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
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.
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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
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
TA
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 does not match the claimed Tamil 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: