Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

eckeroline.com

Helsinki-Tallinn, Tallinn-Helsinki, ferry trips and hotel packages | Eckerö Line

Page Load Speed

6.6 sec in total

First Response

357 ms

Resources Loaded

5.8 sec

Page Rendered

458 ms

eckeroline.com screenshot

About Website

Welcome to eckeroline.com homepage info - get ready to check Eckero Line best content for Finland right away, or after learning these important things about eckeroline.com

Find and book easily one way and return trips between Tallinn and Helsinki on our web site. Check out the convenient car packages if you are travelling with a car. Hotel Package are a good choice for ...

Visit eckeroline.com

Key Findings

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

Performance Metrics

eckeroline.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.406

24/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

eckeroline.com

357 ms

eckeroline.com

456 ms

www.eckeroline.com

837 ms

calendar.css

28 ms

flatpickr.min.css

21 ms

Our browser made a total of 217 requests to load all elements on the main page. We found that 96% of them (209 requests) were addressed to the original Eckeroline.com, 1% (2 requests) were made to Googletagmanager.com and 1% (2 requests) were made to Eckeroline.fi. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Eckeroline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 420.8 kB (25%)

Content Size

1.7 MB

After Optimization

1.3 MB

In fact, the total size of Eckeroline.com main page is 1.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 652.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 213.0 kB

  • Original 261.8 kB
  • After minification 260.1 kB
  • After compression 48.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 213.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

  • Original 652.7 kB
  • After minification 651.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. Eckero Line images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 47.5 kB

  • Original 488.5 kB
  • After minification 487.1 kB
  • After compression 441.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-55%

Potential reduce by 158.8 kB

  • Original 287.2 kB
  • After minification 132.6 kB
  • After compression 128.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. Eckeroline.com needs all CSS files to be minified and compressed as it can save up to 158.8 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 172 (86%)

Requests Now

200

After Optimization

28

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

Accessibility Review

eckeroline.com accessibility score

79

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

eckeroline.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

eckeroline.com SEO score

86

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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