Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

tallinksilja.fi

Varaa Tallink Siljan risteilyt Itämeren yli - Tallink Silja Line

Page Load Speed

12.2 sec in total

First Response

1.7 sec

Resources Loaded

10 sec

Page Rendered

450 ms

tallinksilja.fi screenshot

About Website

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

Varaa matka jännittäviin kaupunkikohteisiin kuten Tukholmaan, Ahvenanmaalle ja Tallinnaan. Voit yhdistää risteilyysi hotellin, auton, konferenssin tai kylpylän

Visit tallinksilja.fi

Key Findings

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

Performance Metrics

tallinksilja.fi performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value32.6 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,380 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.75

6/100

15%

TTI (Time to Interactive)

Value30.9 s

0/100

10%

Network Requests Diagram

www.tallinksilja.fi

1748 ms

etsi-matka

1261 ms

aui.css

631 ms

main.css

247 ms

main.css

197 ms

Our browser made a total of 225 requests to load all elements on the main page. We found that 76% of them (170 requests) were addressed to the original Tallinksilja.fi, 5% (11 requests) were made to Inpref.com and 3% (7 requests) were made to Booking.tallink.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Tallinksilja.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (66%)

Content Size

2.9 MB

After Optimization

988.3 kB

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

HTML Optimization

-87%

Potential reduce by 167.1 kB

  • Original 191.6 kB
  • After minification 117.9 kB
  • After compression 24.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 73.7 kB, which is 38% 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 167.1 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 27.3 kB

  • Original 446.6 kB
  • After minification 419.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 Silja images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 910.8 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 411.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 910.8 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 791.6 kB

  • Original 924.5 kB
  • After minification 767.0 kB
  • After compression 132.9 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.fi needs all CSS files to be minified and compressed as it can save up to 791.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 185 (85%)

Requests Now

217

After Optimization

32

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

Accessibility Review

tallinksilja.fi accessibility score

77

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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.fi 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.fi SEO score

84

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

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FI

  • Language Claimed

    TA

  • Encoding

    UTF-8

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

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: