Tools & Wizards About Us
stenaline.no screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 70

    SEO

    Google-friendlier than
    29% of websites

stenaline.no

Reis med ferge til Danmark, Tyskland og Polen | Stena Line

Page Load Speed

2.8 sec in total

First Response

326 ms

Resources Loaded

2.2 sec

Page Rendered

246 ms

stenaline.no screenshot

About Website

Visit stenaline.no now to see the best up-to-date Stena Line content for Norway and also check out these interesting facts you probably never knew about stenaline.no

Reis til Storbritannia, Irland, Nederland og Nord-Europa med Stena Line. Se våre ruter, ferger, spesialtilbud og mye mer. Bestill på nettet for de beste billettprisene.

Visit stenaline.no

Key Findings

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

Performance Metrics

stenaline.no performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

stenaline.no

326 ms

www.stenaline.no

479 ms

jquery

387 ms

globalSettings

212 ms

settings_nb-NO

211 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 52% of them (45 requests) were addressed to the original Stenaline.no, 13% (11 requests) were made to Tags.tiqcdn.com and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (810 ms) belongs to the original domain Stenaline.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 335.9 kB (44%)

Content Size

759.5 kB

After Optimization

423.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Stenaline.no main page is 759.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 362.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 69.9 kB

  • Original 87.2 kB
  • After minification 71.0 kB
  • After compression 17.3 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 16.3 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 69.9 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 31.2 kB

  • Original 309.3 kB
  • After minification 278.1 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. Stena Line images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 234.8 kB

  • Original 362.9 kB
  • After minification 349.8 kB
  • After compression 128.1 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 234.8 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (80%)

Requests Now

82

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stenaline.no

stenaline.no

326 ms

www.stenaline.no

www.stenaline.no

479 ms

jquery

jquery

387 ms

globalSettings

globalSettings

212 ms

settings_nb-NO

settings_nb-NO

211 ms

stena-map-widget-css

stena-map-widget-css

207 ms

stena-map-widget

stena-map-widget

325 ms

SiteCss

SiteCss

223 ms

SiteMainLessCss

SiteMainLessCss

505 ms

componentCss

componentCss

310 ms

restrictedContentJs

restrictedContentJs

311 ms

modernizrAndInlineBootstrapingJs

modernizrAndInlineBootstrapingJs

333 ms

bvapi.js

bvapi.js

126 ms

resourcetexts.aspx

resourcetexts.aspx

412 ms

resourcetexts.aspx

resourcetexts.aspx

412 ms

backboneJs

backboneJs

566 ms

utag.sync.js

utag.sync.js

87 ms

WebResource.axd

WebResource.axd

578 ms

ScriptResource.axd

ScriptResource.axd

579 ms

ScriptResource.axd

ScriptResource.axd

563 ms

clientTemplatesJs

clientTemplatesJs

519 ms

backboneModels

backboneModels

714 ms

jqueryEffectsCore

jqueryEffectsCore

518 ms

jqueryui

jqueryui

768 ms

globalPropertiesJs

globalPropertiesJs

664 ms

datePickerLocalizationJs

datePickerLocalizationJs

587 ms

componentJs

componentJs

752 ms

modulesJs

modulesJs

761 ms

scripthandler

scripthandler

672 ms

bootstrap

bootstrap

809 ms

IeFixes

IeFixes

810 ms

bakgrund-winter.ashx

bakgrund-winter.ashx

660 ms

bv.js

bv.js

202 ms

mmcore.js

mmcore.js

15 ms

j.php

j.php

5 ms

v.gif

v.gif

5 ms

30 ms

logo.ashx

logo.ashx

317 ms

ajax-loader.gif

ajax-loader.gif

349 ms

stena-line-logo.ashx

stena-line-logo.ashx

349 ms

Ta-et-stenacruise.ashx

Ta-et-stenacruise.ashx

349 ms

Ferge-til-Danmark.ashx

Ferge-til-Danmark.ashx

348 ms

Ferge-til-Europa.ashx

Ferge-til-Europa.ashx

526 ms

Extra_hub_logo.ashx

Extra_hub_logo.ashx

442 ms

utag.js

utag.js

80 ms

sprite.png

sprite.png

671 ms

selector-shadow.gif

selector-shadow.gif

399 ms

ITCFranklinGothicW02-Dm812954.woff

ITCFranklinGothicW02-Dm812954.woff

736 ms

ITCFranklinGothicW10-Dm862375.woff

ITCFranklinGothicW10-Dm862375.woff

617 ms

magpie.js

magpie.js

81 ms

300 ms

LoginService.ashx

LoginService.ashx

245 ms

head

head

264 ms

body

body

338 ms

utag.996.js

utag.996.js

13 ms

utag.1001.js

utag.1001.js

5 ms

utag.1013.js

utag.1013.js

46 ms

utag.1012.js

utag.1012.js

6 ms

utag.1028.js

utag.1028.js

6 ms

utag.1024.js

utag.1024.js

5 ms

utag.1027.js

utag.1027.js

12 ms

utag.1049.js

utag.1049.js

13 ms

utag.1050.js

utag.1050.js

13 ms

SessionCam-tag-v5-5.js

SessionCam-tag-v5-5.js

321 ms

225 ms

fbds.js

fbds.js

10 ms

gtm.js

gtm.js

46 ms

conversion_async.js

conversion_async.js

30 ms

i.gif

i.gif

288 ms

sdk.js

sdk.js

4 ms

37 ms

plusone.js

plusone.js

114 ms

71 ms

119 ms

xd_arbiter.php

xd_arbiter.php

35 ms

xd_arbiter.php

xd_arbiter.php

49 ms

analytics.js

analytics.js

35 ms

collect

collect

28 ms

60 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

16 ms

113 ms

109 ms

ga.js

ga.js

10 ms

__utm.gif

__utm.gif

38 ms

__utm.gif

__utm.gif

31 ms

sessioncam.recorder.js

sessioncam.recorder.js

16 ms

9 ms

Accessibility Review

stenaline.no accessibility score

81

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

stenaline.no best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

stenaline.no SEO score

70

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

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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

    NO

  • Language Claimed

    NB

  • Encoding

    UTF-8

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

Social Sharing Optimization

stenaline.no

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