5.3 sec in total
373 ms
4.7 sec
197 ms
Click here to check amazing Fjord Line content. Otherwise, check out these important facts you probably never knew about fjordline.no
Fjord Line tilbyr reiser med ferge mellom Bergen, Stavanger, Kristiansand, Langesund og Hirtshals i Danmark, og mellom Sandefjord og Strømstad i Sverige.
Visit fjordline.noWe 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.
fjordline.no performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value17.8 s
0/100
25%
Value12.2 s
3/100
10%
Value3,010 ms
3/100
30%
Value0
100/100
15%
Value23.3 s
1/100
10%
373 ms
383 ms
1093 ms
126 ms
256 ms
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.
Page size can be reduced by 712.4 kB (46%)
1.5 MB
824.6 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. 30% of websites need less resources to load. Images take 708.6 kB which makes up the majority of the site volume.
Potential reduce by 26.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 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.
Potential reduce by 68.0 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. Fjord Line images are well optimized though.
Potential reduce by 368.2 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 368.2 kB or 74% of the original size.
Potential reduce by 250.2 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.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.
Number of requests can be reduced by 27 (69%)
39
12
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.
fjordline.no
373 ms
no
383 ms
no
1093 ms
app.min.css
126 ms
fl_override2.css
256 ms
fw.js
2039 ms
date-nb-NO.js
620 ms
angular-locale_nb-NO.js
375 ms
common.min.js
748 ms
layout.min.js
497 ms
fl_override2.js
388 ms
tt-96bb293aaa330ef307ee004448b92b75ffdc25ade2831ed23fc60ffa97fffb7f.js
43 ms
app.min-blessed1.css
628 ms
Fjordline-logo.png
125 ms
gtm.js
95 ms
flags.png
130 ms
list.png
129 ms
frontpage-ship2016_1920x780b.jpg
1507 ms
phone-flipped.png
125 ms
s-facebook.png
226 ms
twitter.png
237 ms
Colfax-Regular.otf
360 ms
Colfax-Medium.otf
497 ms
Colfax-Light.otf
474 ms
Colfax-Bold.otf
484 ms
entypo.woff
492 ms
fl-icons.woff
602 ms
fontawesome-webfont.woff
725 ms
conversion_async.js
26 ms
477 ms
bind
362 ms
tt-96bb293aaa330ef307ee004448b92b75ffdc25ade2831ed23fc60ffa97fffb7f.js
99 ms
analytics.js
52 ms
29 ms
30 ms
collect
12 ms
collect
50 ms
ga-audiences
16 ms
3693541.html
25 ms
activityi;src=4647584;type=retar0;cat=fjord000;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=8750345043372.363
64 ms
119 ms
118 ms
7539.iframe;c
209 ms
fbevents.js
166 ms
no.js
142 ms
e920e04_a.js
205 ms
activityi;src=4647584;type=retar0;cat=fjord000;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=4697019974701.106
51 ms
89 ms
print.min.css
125 ms
d7.js
409 ms
7539.image
108 ms
fjordline.no accessibility score
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
[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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fjordline.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fjordline.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NO
NO
UTF-8
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.
fjordline.no
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: