Tools & Wizards About Us
fjordline.de screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

fjordline.de

Fjord Line – Ihre Reise nach Norwegen beginnt bei uns

Page Load Speed

4.5 sec in total

First Response

321 ms

Resources Loaded

3.9 sec

Page Rendered

313 ms

fjordline.de screenshot

About Website

Visit fjordline.de now to see the best up-to-date Fjord Line content and also check out these interesting facts you probably never knew about fjordline.de

Fjord Line - mit der Fähre nach Norwegen - von Hirtshals zwischen Stavanger, Bergen, Kristiansand, Langesund und zwischen Sandefjord und Strömstad.

Visit fjordline.de

Key Findings

We analyzed Fjordline.de page load time and found that the first response time was 321 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

fjordline.de performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value3,770 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

fjordline.de

321 ms

de

435 ms

de

777 ms

app.min.css

126 ms

fl_override2.css

261 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fjordline.de, 48% (25 requests) were made to Fjordline.com and 15% (8 requests) were made to Track.adform.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Fjordline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 684.3 kB (36%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fjordline.de main page is 1.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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 27.4 kB

  • Original 34.6 kB
  • After minification 28.1 kB
  • After compression 7.2 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 6.4 kB, which is 19% 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 27.4 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 45.1 kB

  • 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. Fjord Line images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 361.6 kB

  • Original 480.0 kB
  • After minification 407.2 kB
  • After compression 118.4 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 361.6 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 250.2 kB

  • Original 298.8 kB
  • After minification 296.0 kB
  • After compression 48.7 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. Fjordline.de needs all CSS files to be minified and compressed as it can save up to 250.2 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fjord 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 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fjordline.de

fjordline.de

321 ms

de

de

435 ms

de

de

777 ms

app.min.css

app.min.css

126 ms

fl_override2.css

fl_override2.css

261 ms

fw.js

fw.js

1221 ms

date-de-DE.js

date-de-DE.js

798 ms

angular-locale_de-DE.js

angular-locale_de-DE.js

386 ms

common.min.js

common.min.js

750 ms

layout.min.js

layout.min.js

501 ms

fl_override2.js

fl_override2.js

391 ms

app.min-blessed1.css

app.min-blessed1.css

745 ms

Fjordline-logo.png

Fjordline-logo.png

160 ms

gtm.js

gtm.js

101 ms

flags.png

flags.png

159 ms

list.png

list.png

160 ms

Frontpage_Germany.jpg

Frontpage_Germany.jpg

1325 ms

phone-flipped.png

phone-flipped.png

182 ms

Colfax-Regular.otf

Colfax-Regular.otf

576 ms

Colfax-Medium.otf

Colfax-Medium.otf

576 ms

Colfax-Light.otf

Colfax-Light.otf

576 ms

Colfax-Bold.otf

Colfax-Bold.otf

587 ms

entypo.woff

entypo.woff

587 ms

fl-icons.woff

fl-icons.woff

595 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

671 ms

pixel

pixel

60 ms

pixel

pixel

20 ms

conversion_async.js

conversion_async.js

83 ms

606 ms

bind

bind

573 ms

tt-96bb293aaa330ef307ee004448b92b75ffdc25ade2831ed23fc60ffa97fffb7f.js

tt-96bb293aaa330ef307ee004448b92b75ffdc25ade2831ed23fc60ffa97fffb7f.js

115 ms

analytics.js

analytics.js

55 ms

match-result

match-result

22 ms

collect

collect

11 ms

collect

collect

82 ms

55 ms

56 ms

ga-audiences

ga-audiences

37 ms

fbevents.js

fbevents.js

105 ms

tt-96bb293aaa330ef307ee004448b92b75ffdc25ade2831ed23fc60ffa97fffb7f.js

tt-96bb293aaa330ef307ee004448b92b75ffdc25ade2831ed23fc60ffa97fffb7f.js

120 ms

de.js

de.js

182 ms

24 ms

3693541.html

3693541.html

5 ms

activityi;src=4647584;type=retar0;cat=fjord000;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=7556022743228.823

activityi;src=4647584;type=retar0;cat=fjord000;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=7556022743228.823

95 ms

123 ms

224 ms

202 ms

108 ms

108 ms

113 ms

112 ms

print.min.css

print.min.css

126 ms

Accessibility Review

fjordline.de accessibility score

87

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

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

Buttons do not have an accessible name

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

Heading elements are not in a sequentially-descending order

Best Practices

fjordline.de 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

fjordline.de SEO score

89

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

fjordline.de

Open Graph data is detected on the main page of Fjord Line. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: