Analyze

fjordline.no: Fjord Line – Reiser med ferge til Danmark og Sverige

Fjord Line tilbyr ferge mellom Bergen, Stavanger, Kristiansand og Langesund til Hirtshals i Danmark og fra Sandefjord til Strömstad i Sverige.

Page load speed analysis

  • 69/100

    Normal result
  • 8

    Successful tests
  • 0

    Failed test
  • First response

    373 ms

  • Resources loaded

    4.7 sec

  • Page rendered

    197 ms

  • Total page load time

    5.3 sec

Click here to check amazing Fjord Line content. Otherwise, check out these important facts you probably never knew about fjordline.no

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

Page optimization

  • HTML 32.9 kB
    Images 708.6 kB
    Javascripts 501.6 kB
    CSS 298.8 kB

    In fact, the total size of Fjordline.no main page is 1.5 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. 35% of websites need less resources to load. Images take 708.6 kB which makes up the majority of the site volume.

    • Original 32.9 kB
    • After minification 26.4 kB
    • After compression 6.9 kB

    HTML optimization

    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.5 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 26.0 kB or 79% of the original size.

    • Original 708.6 kB
    • After optimization 640.7 kB

    Image optimization

    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.

    • Original 501.6 kB
    • After minification 428.8 kB
    • After compression 102.6 kB

    JavaScript optimization

    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 399.0 kB or 80% of the original size.

    • Original 298.8 kB
    • After minification 296.0 kB
    • After compression 48.7 kB

    CSS optimization

    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.no needs all CSS files to be minified and compressed as it can save up to 250.2 kB or 84% of the original size.

Network requests diagram

  • fjordline.no
  • no
  • no
  • app.min.css
  • fl_override2.css
  • fw.js
  • date-nb-NO.js
  • angular-locale_nb-NO.js
  • common.min.js
  • layout.min.js
  • fl_override2.js
  • tt-96bb293aaa330ef307ee004448b92b75ffdc25ade2831ed23fc60ffa97fffb7f.js
  • app.min-blessed1.css
  • Fjordline-logo.png
  • gtm.js
  • flags.png
  • list.png
  • frontpage-ship2016_1920x780b.jpg
  • phone-flipped.png
  • s-facebook.png
  • twitter.png
  • Colfax-Regular.otf
  • Colfax-Medium.otf
  • Colfax-Light.otf
  • Colfax-Bold.otf
  • entypo.woff
  • fl-icons.woff
  • fontawesome-webfont.woff
  • conversion_async.js
  • bind
  • tt-96bb293aaa330ef307ee004448b92b75ffdc25ade2831ed23fc60ffa97fffb7f.js
  • analytics.js
  • collect
  • collect
  • ga-audiences
  • 3693541.html
  • activityi;src=4647584;type=retar0;cat=fjord000;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=8750345043372.363
  • 7539.iframe;c
  • fbevents.js
  • no.js
  • e920e04_a.js
  • activityi;src=4647584;type=retar0;cat=fjord000;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=4697019974701.106
  • print.min.css
  • d7.js
  • 7539.image

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fjordline.no, 53% (27 requests) were made to Fjordline.com and 6% (3 requests) were made to De17a.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Fjordline.com.

Additional info on fjordline.no

Requests

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

17

Javascripts

12

Images

4

CSS

6

AJAX

39

All

Possible request optimization

1

Javascripts

4

Images

1

CSS

6

AJAX

27

Optimized

12

All

Normal result

Redirects

As for redirects, our browser reached this domain in two steps. The first redirect led to http://www.fjordline.com/no, then it was forwarded to https://www.fjordline.com/no, and finally we managed to open this domain. We strongly recommend that the redirects should be reduced, as the more redirects a site has, the slower it loads.

IP address

Fjordline.no uses IP address which is currently shared with 2 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

fjordline.no

fjordline.de

booking.fjordline.com

178.22.98.117

DNS records

Type Host Target/ip TTL Other
A

fjordline.no

178.22.98.117 3599
NS

fjordline.no

ns2.telecomputing.no 3599
NS

fjordline.no

ns1.telecomputing.no 3599
SOA

fjordline.no

3599 Mname: ns1.telecomputing.no
Rname: admin.telecomputing.no
Serial: 2007010429
Refresh: 900
Retry: 600
Expire: 86400
Minimum-ttl: 3600
MX

fjordline.no

mx03.telecomputing.no 3599 Pri: 10

Language and encoding

Good result

Language

NO no language flag

Detected

NO no language flag

Claimed

Encoding

UTF-8

Claimed

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

HTTPS certificate

SSL Certificate

Fjordline.no has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of Fjordline.no is located in Norway, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Good result

Social Sharing Optimization

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:

fjordline.no

Share this report in social media

Analyze another website

Analyze