Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

tallink.ee

Laevapiletid - Tallink Silja Line

Page Load Speed

9 sec in total

First Response

362 ms

Resources Loaded

8.3 sec

Page Rendered

333 ms

tallink.ee screenshot

About Website

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.ee

Key Findings

We 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.

Performance Metrics

tallink.ee performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value24.2 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value3,600 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.614

10/100

15%

TTI (Time to Interactive)

Value28.0 s

0/100

10%

Network Requests Diagram

www.tallink.ee

362 ms

vali-reis

830 ms

aui.css

562 ms

main.css

223 ms

main.css

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 Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (59%)

Content Size

2.9 MB

After Optimization

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.

HTML Optimization

-87%

Potential reduce by 150.5 kB

  • Original 172.4 kB
  • After minification 109.1 kB
  • After compression 22.0 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.

Image Optimization

-4%

Potential reduce by 29.8 kB

  • Original 716.3 kB
  • After minification 686.5 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.

JavaScript Optimization

-69%

Potential reduce by 751.1 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 335.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 751.1 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 792.5 kB

  • Original 925.8 kB
  • After minification 766.8 kB
  • After compression 133.4 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.

Requests Breakdown

Number of requests can be reduced by 160 (81%)

Requests Now

198

After Optimization

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.

Accessibility Review

tallink.ee accessibility score

72

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

tallink.ee 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

tallink.ee 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

    ET

  • Language Claimed

    TA

  • Encoding

    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.

Social Sharing Optimization

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: