Tools & Wizards About Us
tallinksilja.no screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

tallinksilja.no

Tallink & Silja Line - Bestill din fergetur her - Tallink & Silja Line

Page Load Speed

5.9 sec in total

First Response

363 ms

Resources Loaded

5.3 sec

Page Rendered

186 ms

tallinksilja.no screenshot

About Website

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

Fergetur fra Stockholm til mange ulike destinasjoner. Bestill reise enkelt med Tallink & Silja Line. Blir kjent med våre destinasjoner, Helsingfors, Åbo, Åland, Tallinn og Riga.

Visit tallinksilja.no

Key Findings

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

Performance Metrics

tallinksilja.no performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.9 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,410 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value25.4 s

0/100

10%

Network Requests Diagram

tallinksilja.no

363 ms

no.tallink.com

506 ms

finn-reise

1019 ms

main.css

361 ms

combo

1250 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tallinksilja.no, 75% (51 requests) were made to No.tallink.com and 6% (4 requests) were made to Booking.tallink.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Sso.tallink.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.4 kB (16%)

Content Size

2.1 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Tallinksilja.no 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 157.0 kB

  • Original 184.4 kB
  • After minification 148.2 kB
  • After compression 27.4 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 36.2 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 157.0 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 169 B

  • Original 1.1 MB
  • After minification 1.1 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

-23%

Potential reduce by 185.2 kB

  • Original 805.5 kB
  • After minification 805.4 kB
  • After compression 620.3 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.2 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (71%)

Requests Now

59

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 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 28 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tallinksilja.no

tallinksilja.no

363 ms

no.tallink.com

no.tallink.com

506 ms

finn-reise

finn-reise

1019 ms

main.css

main.css

361 ms

combo

combo

1250 ms

clay.css

clay.css

1247 ms

main.css

main.css

750 ms

combo

combo

395 ms

js_loader_config

js_loader_config

388 ms

combo

combo

901 ms

combo

combo

1090 ms

combo

combo

1242 ms

js_bundle_config

js_bundle_config

883 ms

combo

combo

1013 ms

main.css

main.css

1424 ms

combo

combo

1142 ms

jquery-migrate-1.4.1.min.js

jquery-migrate-1.4.1.min.js

1221 ms

jquery-migrate-3.3.0.min.js

jquery-migrate-3.3.0.min.js

1420 ms

launch-ENaf7c1461e6c0454490c41c01dcff1d16.min.js

launch-ENaf7c1461e6c0454490c41c01dcff1d16.min.js

18 ms

sso.min.js

sso.min.js

1710 ms

bookingEntry.css

bookingEntry.css

661 ms

require.min.js

require.min.js

612 ms

main.js

main.js

1187 ms

lib.min.js

lib.min.js

1276 ms

custom.min.js

custom.min.js

1188 ms

common-object.js

common-object.js

1189 ms

common.shared.min.js

common.shared.min.js

1270 ms

gtm.js

gtm.js

1138 ms

jquery.cookie.js

jquery.cookie.js

124 ms

easyXDM.min.js

easyXDM.min.js

124 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

125 ms

slick.min.js

slick.min.js

125 ms

bundle.production.min.js

bundle.production.min.js

617 ms

sdk.js

sdk.js

125 ms

1x1_transparent.png

1x1_transparent.png

550 ms

flag_no.svg

flag_no.svg

128 ms

pin.svg

pin.svg

141 ms

flag_int.svg

flag_int.svg

142 ms

chat.svg

chat.svg

143 ms

430_megamenu_03.jpg

430_megamenu_03.jpg

281 ms

430_megamenu_05.jpg

430_megamenu_05.jpg

144 ms

430_megamenu_04.jpg

430_megamenu_04.jpg

373 ms

en_GB.png

en_GB.png

281 ms

960_SILJA-SYMPHONY-Mariehamn-230615-IMG_1215-%C2%A9-Marko-Stampehl.jpg

960_SILJA-SYMPHONY-Mariehamn-230615-IMG_1215-%C2%A9-Marko-Stampehl.jpg

855 ms

960_Kryssning_TallinkSilja.jpg

960_Kryssning_TallinkSilja.jpg

730 ms

960_Kryssning_Helsingfors.jpg

960_Kryssning_Helsingfors.jpg

609 ms

960_Kryssning_Mumin.jpg

960_Kryssning_Mumin.jpg

850 ms

960_ships_baltic_queen_day_jokemedia_RGB_004.jpg

960_ships_baltic_queen_day_jokemedia_RGB_004.jpg

730 ms

white.gif

white.gif

490 ms

shared.html

shared.html

168 ms

GT-Walsheim-Pro-Regular.woff

GT-Walsheim-Pro-Regular.woff

619 ms

GT-Walsheim-Pro-Medium.woff

GT-Walsheim-Pro-Medium.woff

753 ms

GT-Walsheim-Pro-Bold.woff

GT-Walsheim-Pro-Bold.woff

864 ms

arrow_down_white.svg

arrow_down_white.svg

736 ms

sdk.js

sdk.js

16 ms

logo_tallinksilja_white.svg

logo_tallinksilja_white.svg

728 ms

main.js

main.js

170 ms

cta_icons.svg

cta_icons.svg

772 ms

icon_facebook.svg

icon_facebook.svg

769 ms

icon_youtube.svg

icon_youtube.svg

752 ms

icon_instagram.svg

icon_instagram.svg

772 ms

cookies.js

cookies.js

203 ms

bookingEntry.js

bookingEntry.js

1204 ms

arrow-left-desktop-white.svg

arrow-left-desktop-white.svg

569 ms

Route-map.jpg

Route-map.jpg

1083 ms

1x1_transparent.png

1x1_transparent.png

263 ms

asset-manifest.json

asset-manifest.json

136 ms

1x1_transparent.png

1x1_transparent.png

508 ms

Accessibility Review

tallinksilja.no accessibility score

78

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

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.no best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tallinksilja.no SEO score

91

Search Engine Optimization Advices

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

    NO

  • Language Claimed

    SV

  • Encoding

    UTF-8

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

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: