Tools & Wizards About Us
stenaline.de screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

stenaline.de

Fähre nach Schweden, Großbritannien & Lettland | Stena Line

Page Load Speed

2.6 sec in total

First Response

319 ms

Resources Loaded

2.2 sec

Page Rendered

146 ms

stenaline.de screenshot

About Website

Click here to check amazing Stena Line content for Germany. Otherwise, check out these important facts you probably never knew about stenaline.de

Reisen Sie mit Stena Line nach Großbritannien, Irland, Holland und Nordeuropa. Unsere Reiserouten, Fähren, Angebote sowie die günstigsten Tarife und vieles mehr finden Sie online.

Visit stenaline.de

Key Findings

We analyzed Stenaline.de page load time and found that the first response time was 319 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

stenaline.de performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value2,390 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.104

89/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

stenaline.de

319 ms

www.stenaline.de

467 ms

jquery

295 ms

globalSettings

195 ms

settings_de-DE

198 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 55% of them (45 requests) were addressed to the original Stenaline.de, 12% (10 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 (701 ms) belongs to the original domain Stenaline.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 328.2 kB (49%)

Content Size

666.0 kB

After Optimization

337.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Stenaline.de main page is 666.0 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. 60% of websites need less resources to load. Javascripts take 360.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 64.3 kB

  • Original 79.7 kB
  • After minification 62.9 kB
  • After compression 15.4 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.7 kB, which is 21% 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 64.3 kB or 81% of the original size.

Image Optimization

-14%

Potential reduce by 31.5 kB

  • Original 226.0 kB
  • After minification 194.5 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. Obviously, Stena Line needs image optimization as it can save up to 31.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 232.4 kB

  • Original 360.3 kB
  • After minification 347.3 kB
  • After compression 127.9 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 232.4 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (81%)

Requests Now

77

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 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 54 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.de

stenaline.de

319 ms

www.stenaline.de

www.stenaline.de

467 ms

jquery

jquery

295 ms

globalSettings

globalSettings

195 ms

settings_de-DE

settings_de-DE

198 ms

stena-map-widget-css

stena-map-widget-css

202 ms

stena-map-widget

stena-map-widget

308 ms

SiteCss

SiteCss

220 ms

SiteMainLessCss

SiteMainLessCss

479 ms

componentCss

componentCss

290 ms

restrictedContentJs

restrictedContentJs

310 ms

modernizrAndInlineBootstrapingJs

modernizrAndInlineBootstrapingJs

328 ms

bvapi.js

bvapi.js

163 ms

resourcetexts.aspx

resourcetexts.aspx

384 ms

resourcetexts.aspx

resourcetexts.aspx

390 ms

backboneJs

backboneJs

529 ms

utag.sync.js

utag.sync.js

124 ms

WebResource.axd

WebResource.axd

542 ms

ScriptResource.axd

ScriptResource.axd

555 ms

ScriptResource.axd

ScriptResource.axd

442 ms

clientTemplatesJs

clientTemplatesJs

441 ms

backboneModels

backboneModels

585 ms

jqueryEffectsCore

jqueryEffectsCore

488 ms

jqueryui

jqueryui

701 ms

globalPropertiesJs

globalPropertiesJs

509 ms

datePickerLocalizationJs

datePickerLocalizationJs

509 ms

componentJs

componentJs

684 ms

modulesJs

modulesJs

683 ms

scripthandler

scripthandler

605 ms

bootstrap

bootstrap

608 ms

IeFixes

IeFixes

673 ms

bg-sea-and-sky.ashx

bg-sea-and-sky.ashx

403 ms

bv.js

bv.js

65 ms

mmcore.js

mmcore.js

43 ms

j.php

j.php

20 ms

v.gif

v.gif

5 ms

17 ms

magpie.js

magpie.js

174 ms

logo.ashx

logo.ashx

230 ms

ajax-loader.gif

ajax-loader.gif

268 ms

stena-line-logo.ashx

stena-line-logo.ashx

268 ms

HUB_Skandinavien_792x440.ashx

HUB_Skandinavien_792x440.ashx

385 ms

HUB_Grossbritannien_Irland_792x440.ashx

HUB_Grossbritannien_Irland_792x440.ashx

382 ms

HUB_Baltikum_792x440.ashx

HUB_Baltikum_792x440.ashx

393 ms

utag.js

utag.js

132 ms

sprite.png

sprite.png

640 ms

selector-shadow.gif

selector-shadow.gif

307 ms

shadowDown.png

shadowDown.png

337 ms

ITCFranklinGothicW02-Dm812954.woff

ITCFranklinGothicW02-Dm812954.woff

639 ms

ITCFranklinGothicW10-Dm862375.woff

ITCFranklinGothicW10-Dm862375.woff

590 ms

385 ms

LoginService.ashx

LoginService.ashx

218 ms

head

head

170 ms

body

body

180 ms

utag.1301.js

utag.1301.js

121 ms

utag.1319.js

utag.1319.js

39 ms

utag.1318.js

utag.1318.js

48 ms

utag.1317.js

utag.1317.js

136 ms

utag.1306.js

utag.1306.js

100 ms

utag.1357.js

utag.1357.js

41 ms

utag.1356.js

utag.1356.js

144 ms

utag.1371.js

utag.1371.js

243 ms

conversion_async.js

conversion_async.js

25 ms

plusone.js

plusone.js

90 ms

34 ms

SessionCam-tag-v5-5.js

SessionCam-tag-v5-5.js

173 ms

35 ms

gtm.js

gtm.js

123 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

n.js

n.js

16 ms

ga.js

ga.js

45 ms

__utm.gif

__utm.gif

49 ms

__utm.gif

__utm.gif

43 ms

pixel

pixel

30 ms

analytics.js

analytics.js

18 ms

sdk.js

sdk.js

36 ms

95 ms

collect

collect

51 ms

143 ms

xd_arbiter.php

xd_arbiter.php

36 ms

xd_arbiter.php

xd_arbiter.php

58 ms

sessioncam.recorder.js

sessioncam.recorder.js

15 ms

Accessibility Review

stenaline.de 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.de best practices score

83

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

SEO Factors

stenaline.de SEO score

78

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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 Stenaline.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 Stenaline.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

stenaline.de

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: