2.7 sec in total
305 ms
2.2 sec
176 ms
Visit stenaline.com now to see the best up-to-date Stena Line content for Sweden and also check out these interesting facts you probably never knew about stenaline.com
Welcome to one of the world's largest ferry operators
Visit stenaline.comWe analyzed Stenaline.com page load time and found that the first response time was 305 ms and then it took 2.4 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.
stenaline.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value5.3 s
21/100
25%
Value6.6 s
37/100
10%
Value950 ms
29/100
30%
Value1.872
0/100
15%
Value5.6 s
69/100
10%
305 ms
488 ms
388 ms
216 ms
210 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 86% of them (42 requests) were addressed to the original Stenaline.com, 6% (3 requests) were made to Tags.tiqcdn.com and 4% (2 requests) were made to Ws.pushcall.com. The less responsive or slowest element that took the longest time to load (995 ms) belongs to the original domain Stenaline.com.
Page size can be reduced by 458.1 kB (49%)
926.2 kB
468.1 kB
In fact, the total size of Stenaline.com main page is 926.2 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. 40% of websites need less resources to load. Javascripts take 562.2 kB which makes up the majority of the site volume.
Potential reduce by 30.7 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 7.9 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 30.7 kB or 78% of the original size.
Potential reduce by 31.6 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.
Potential reduce by 395.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 395.9 kB or 70% of the original size.
Number of requests can be reduced by 32 (73%)
44
12
The browser has sent 44 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 30 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
stenaline.com
305 ms
www.stenaline.com
488 ms
jquery
388 ms
globalSettings
216 ms
stena-map-widget-css
210 ms
stena-map-widget
324 ms
SiteCss
223 ms
SiteMainLessCss
440 ms
componentCss
312 ms
restrictedContentJs
324 ms
modernizrAndInlineBootstrapingJs
335 ms
resourcetexts.aspx
435 ms
resourcetexts.aspx
477 ms
backboneJs
545 ms
utag.sync.js
140 ms
WebResource.axd
560 ms
ScriptResource.axd
582 ms
ScriptResource.axd
535 ms
clientTemplatesJs
562 ms
backboneModels
566 ms
jqueryEffectsCore
544 ms
jqueryui
886 ms
globalPropertiesJs
675 ms
datePickerLocalizationJs
585 ms
componentJs
751 ms
modulesJs
995 ms
scripthandler
675 ms
bootstrap
684 ms
IeFixes
785 ms
bakgrund-winter.ashx
758 ms
logo.ashx
424 ms
stena-line-logo.ashx
528 ms
Stena-Line-Route-Map_uppdat_feb_3_.ashx
577 ms
Kitchen_Staff_2013_3.ashx
671 ms
Horizon.ashx
673 ms
Frakta-med-oss.ashx
743 ms
utag.js
85 ms
sprite.png
924 ms
selector-shadow.gif
627 ms
ITCFranklinGothicW02-Dm812954.woff
863 ms
ITCFranklinGothicW10-Dm862375.woff
928 ms
276 ms
LoginService.ashx
240 ms
head
219 ms
body
282 ms
utag.1.js
9 ms
ga.js
25 ms
__utm.gif
38 ms
103 ms
stenaline.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
stenaline.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
stenaline.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
SV
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stenaline.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Swedish language. Our system also found out that Stenaline.com 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.
stenaline.com
Open Graph description is not detected on the main page of Stena Line. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: