Tools & Wizards About Us
tallinksilja.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

tallinksilja.com

Book cruise and ferry tickets on the Baltic Sea - Tallink Silja Line

Page Load Speed

10.1 sec in total

First Response

883 ms

Resources Loaded

9.1 sec

Page Rendered

128 ms

tallinksilja.com screenshot

About Website

Visit tallinksilja.com now to see the best up-to-date Tallink Silja content for Taiwan and also check out these interesting facts you probably never knew about tallinksilja.com

Route trips and roundtrip cruises to Helsinki, Stockholm, Tallinn, Turku or Åland. Travel in comfortable cabins on the nicest ships and enjoy tax-free shopping and international entertainment.

Visit tallinksilja.com

Key Findings

We analyzed Tallinksilja.com page load time and found that the first response time was 883 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

tallinksilja.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value47.0 s

0/100

25%

SI (Speed Index)

Value29.2 s

0/100

10%

TBT (Total Blocking Time)

Value29,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.476

18/100

15%

TTI (Time to Interactive)

Value55.6 s

0/100

10%

Network Requests Diagram

www.tallink.com

883 ms

aui.css

1956 ms

main.css

237 ms

main.css

245 ms

main.css

233 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tallinksilja.com, 1% (2 requests) were made to Google-analytics.com and 1% (2 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Tallink.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (55%)

Content Size

6.0 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tallinksilja.com main page is 6.0 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. Javascripts take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 40.2 kB

  • Original 49.3 kB
  • After minification 41.1 kB
  • After compression 9.1 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 8.1 kB, which is 17% 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 40.2 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 137.2 kB

  • Original 2.0 MB
  • After minification 1.8 MB

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 Silja images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.8 MB

  • Original 2.4 MB
  • After minification 2.4 MB
  • After compression 631.5 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 1.8 MB or 74% of the original size.

CSS Optimization

-84%

Potential reduce by 1.3 MB

  • Original 1.6 MB
  • After minification 1.3 MB
  • After compression 249.8 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. Tallinksilja.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 147 (93%)

Requests Now

158

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tallink Silja. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 98 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.tallink.com

www.tallink.com

883 ms

aui.css

aui.css

1956 ms

main.css

main.css

237 ms

main.css

main.css

245 ms

main.css

main.css

233 ms

main.css

main.css

245 ms

barebone.jsp

barebone.jsp

961 ms

main.js

main.js

506 ms

main.js

main.js

509 ms

main.css

main.css

385 ms

jquery.animate-enhanced.min.js

jquery.animate-enhanced.min.js

277 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

414 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

407 ms

storyjs-embed.js

storyjs-embed.js

521 ms

jquery.dd.js

jquery.dd.js

529 ms

jquery.fancybox-2.0.3.min.js

jquery.fancybox-2.0.3.min.js

545 ms

jquery.ui.datepicker.min.js

jquery.ui.datepicker.min.js

695 ms

jquery-ui-autocomplete.min.js

jquery-ui-autocomplete.min.js

664 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

668 ms

plugins.js

plugins.js

693 ms

script.js

script.js

810 ms

main.js

main.js

811 ms

aui_deprecated.css

aui_deprecated.css

713 ms

portal_1.css

portal_1.css

717 ms

portal_2.css

portal_2.css

835 ms

taglib_1.css

taglib_1.css

827 ms

taglib_2.css

taglib_2.css

864 ms

accessibility.css

accessibility.css

867 ms

add_content.css

add_content.css

141 ms

asset_category_selector.css

asset_category_selector.css

258 ms

asset_column.css

asset_column.css

261 ms

auto_row.css

auto_row.css

288 ms

device_preview.css

device_preview.css

292 ms

edit_layout.css

edit_layout.css

292 ms

flyout.css

flyout.css

385 ms

forms.css

forms.css

387 ms

generic_portal.css

generic_portal.css

417 ms

generic_portlet.css

generic_portlet.css

427 ms

header_row.css

header_row.css

430 ms

javascript_template.css

javascript_template.css

508 ms

notifications.css

notifications.css

510 ms

openid.css

openid.css

536 ms

page_settings.css

page_settings.css

548 ms

panel_component.css

panel_component.css

549 ms

panel_page.css

panel_page.css

621 ms

app_view_common.css

app_view_common.css

520 ms

app_view_entry.css

app_view_entry.css

563 ms

app_view_navigation_item.css

app_view_navigation_item.css

584 ms

app_view_search_entry.css

app_view_search_entry.css

583 ms

app_view_toolbar.css

app_view_toolbar.css

629 ms

asset_categories_summary.css

asset_categories_summary.css

630 ms

asset_links.css

asset_links.css

678 ms

button.css

button.css

711 ms

calendar.css

calendar.css

713 ms

captcha.css

captcha.css

746 ms

categorization_filter.css

categorization_filter.css

746 ms

ddm_template.css

ddm_template.css

799 ms

diff.css

diff.css

829 ms

diff_html.css

diff_html.css

829 ms

discussion.css

discussion.css

863 ms

flags.css

flags.css

859 ms

form_navigator.css

form_navigator.css

887 ms

header.css

header.css

922 ms

icon.css

icon.css

924 ms

icon_help.css

icon_help.css

872 ms

icon_list.css

icon_list.css

868 ms

icon_menu.css

icon_menu.css

844 ms

input_localized.css

input_localized.css

870 ms

input_move_boxes.css

input_move_boxes.css

923 ms

pagination.css

pagination.css

819 ms

panel_pagination.css

panel_pagination.css

855 ms

portlet_css_editor.css

portlet_css_editor.css

824 ms

portlet_item.css

portlet_item.css

818 ms

position_helper.css

position_helper.css

844 ms

preview.css

preview.css

807 ms

rich_editor.css

rich_editor.css

814 ms

search_combobox.css

search_combobox.css

817 ms

separator.css

separator.css

805 ms

tag_selector.css

tag_selector.css

812 ms

toolbar.css

toolbar.css

772 ms

translation_manager.css

translation_manager.css

811 ms

tree.css

tree.css

769 ms

undo_manager.css

undo_manager.css

773 ms

uploader.css

uploader.css

774 ms

field_wrapper.css

field_wrapper.css

739 ms

input_permissions.css

input_permissions.css

773 ms

input_repeat.css

input_repeat.css

771 ms

language.css

language.css

739 ms

logo_selector.css

logo_selector.css

754 ms

navbar.css

navbar.css

722 ms

preview.css

preview.css

729 ms

ratings.css

ratings.css

741 ms

rss_settings.css

rss_settings.css

779 ms

search_container.css

search_container.css

780 ms

search_iterator.css

search_iterator.css

770 ms

search_toggle.css

search_toggle.css

764 ms

sites_directory.css

sites_directory.css

731 ms

social_activities.css

social_activities.css

771 ms

social_bookmarks.css

social_bookmarks.css

804 ms

tags_summary.css

tags_summary.css

803 ms

trash_common.css

trash_common.css

751 ms

user_display.css

user_display.css

754 ms

webdav.css

webdav.css

750 ms

workflow_status.css

workflow_status.css

789 ms

analytics.js

analytics.js

18 ms

base.css

base.css

113 ms

application.css

application.css

117 ms

layout.css

layout.css

111 ms

dockbar.css

dockbar.css

126 ms

navigation.css

navigation.css

120 ms

portlet.css

portlet.css

120 ms

extras.css

extras.css

227 ms

custom.css

custom.css

996 ms

collect

collect

24 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

379 ms

Bootstrap.js

Bootstrap.js

21 ms

serverComponent.php

serverComponent.php

12 ms

jquery.cookie.js

jquery.cookie.js

133 ms

easyXDM.min.js

easyXDM.min.js

125 ms

bg_nav_1st.png

bg_nav_1st.png

128 ms

bg_nav_1st_link.png

bg_nav_1st_link.png

130 ms

bg_nav_1st_login.png

bg_nav_1st_login.png

126 ms

spacer.png

spacer.png

134 ms

search.png

search.png

130 ms

dbbb8df4-c360-4b0b-bb5e-e1f4f38ab023

dbbb8df4-c360-4b0b-bb5e-e1f4f38ab023

1220 ms

93f5383d-c88f-4821-a4e6-f6298c75554f

93f5383d-c88f-4821-a4e6-f6298c75554f

649 ms

de67c990-af1f-4554-94a8-b2f424ab0bde

de67c990-af1f-4554-94a8-b2f424ab0bde

1629 ms

cn.png

cn.png

263 ms

dk.png

dk.png

264 ms

ee.png

ee.png

262 ms

fi.png

fi.png

405 ms

fr.png

fr.png

408 ms

de.png

de.png

408 ms

it.png

it.png

549 ms

jp.png

jp.png

551 ms

lv.png

lv.png

550 ms

lt.png

lt.png

676 ms

nl.png

nl.png

675 ms

no.png

no.png

676 ms

pl.png

pl.png

789 ms

es.png

es.png

826 ms

se.png

se.png

829 ms

ru.png

ru.png

828 ms

gb.png

gb.png

932 ms

layout_set_logo

layout_set_logo

1023 ms

bg_fp_carousel.png

bg_fp_carousel.png

955 ms

bg_othersites_seperator.png

bg_othersites_seperator.png

960 ms

StagSansLCWeb-Book.woff

StagSansLCWeb-Book.woff

1195 ms

StagSansLCWeb-Light.woff

StagSansLCWeb-Light.woff

2794 ms

1401 ms

bg_control_nav.png

bg_control_nav.png

1107 ms

bg_direction_nav.png

bg_direction_nav.png

1233 ms

138 ms

137 ms

available_languages.jsp

available_languages.jsp

149 ms

201 ms

160 ms

289 ms

284 ms

456 ms

160 ms

Accessibility Review

tallinksilja.com accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<html> element does not have a valid value for its [lang] attribute.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tallinksilja.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

tallinksilja.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    TA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tallinksilja.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Tamil language. Our system also found out that Tallinksilja.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.

Social Sharing Optimization

tallinksilja.com

Open Graph description is not detected on the main page of Tallink Silja. 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: