2.7 sec in total
300 ms
2.2 sec
195 ms
Click here to check amazing Stena Line content for Sweden. Otherwise, check out these important facts you probably never knew about stenaline.se
Färja till Danmark, Tyskland eller Polen? Lettland eller Holland? Res med Stena Lines färjor, åk på kryssning eller dagstur.
Visit stenaline.seWe analyzed Stenaline.se page load time and found that the first response time was 300 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.se performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value11.3 s
0/100
25%
Value6.1 s
44/100
10%
Value1,400 ms
16/100
30%
Value0.022
100/100
15%
Value10.7 s
23/100
10%
300 ms
501 ms
298 ms
193 ms
204 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 56% of them (46 requests) were addressed to the original Stenaline.se, 11% (9 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 (814 ms) belongs to the original domain Stenaline.se.
Page size can be reduced by 325.7 kB (44%)
734.9 kB
409.3 kB
In fact, the total size of Stenaline.se main page is 734.9 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 353.1 kB which makes up the majority of the site volume.
Potential reduce by 66.5 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 17.8 kB, which is 22% 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 66.5 kB or 81% of the original size.
Potential reduce by 31.3 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 227.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 227.9 kB or 65% of the original size.
Number of requests can be reduced by 60 (79%)
76
16
The browser has sent 76 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 51 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
stenaline.se
300 ms
www.stenaline.se
501 ms
jquery
298 ms
globalSettings
193 ms
settings_sv-SE
204 ms
stena-map-widget-css
213 ms
stena-map-widget
320 ms
SiteCss
215 ms
SiteMainLessCss
476 ms
componentCss
311 ms
restrictedContentJs
318 ms
modernizrAndInlineBootstrapingJs
322 ms
bvapi.js
84 ms
resourcetexts.aspx
396 ms
resourcetexts.aspx
403 ms
backboneJs
542 ms
utag.sync.js
191 ms
WebResource.axd
541 ms
ScriptResource.axd
549 ms
ScriptResource.axd
539 ms
clientTemplatesJs
448 ms
backboneModels
568 ms
jqueryEffectsCore
501 ms
jqueryui
814 ms
globalPropertiesJs
557 ms
datePickerLocalizationJs
557 ms
componentJs
653 ms
modulesJs
699 ms
scripthandler
664 ms
bootstrap
662 ms
IeFixes
660 ms
bakgrund-winter.ashx
663 ms
bv.js
137 ms
mmcore.js
7 ms
j.php
5 ms
40 ms
v.gif
3 ms
logo.ashx
253 ms
ajax-loader.gif
265 ms
stena-line-logo.ashx
266 ms
resa-till-danmark-1280x802.ashx
296 ms
resa-till-tyskland-1280x802.ashx
360 ms
resa-till-polen-1280x802.ashx
403 ms
europa-1280x802.ashx
403 ms
utag.js
131 ms
sprite.png
585 ms
selector-shadow.gif
389 ms
shadowDown.png
405 ms
ITCFranklinGothicW02-Dm812954.woff
656 ms
ITCFranklinGothicW10-Dm862375.woff
617 ms
magpie.js
22 ms
403 ms
LoginService.ashx
168 ms
head
115 ms
body
230 ms
utag.1817.js
13 ms
utag.1893.js
7 ms
utag.1834.js
8 ms
utag.1833.js
12 ms
utag.1822.js
7 ms
utag.1848.js
6 ms
utag.1862.js
13 ms
sdk.js
29 ms
conversion_async.js
23 ms
SessionCam-tag-v5-5.js
245 ms
plusone.js
121 ms
gtm.js
70 ms
fbds.js
52 ms
67 ms
95 ms
105 ms
xd_arbiter.php
50 ms
xd_arbiter.php
107 ms
analytics.js
119 ms
81 ms
ga.js
176 ms
cb=gapi.loaded_0
50 ms
collect
22 ms
__utm.gif
36 ms
__utm.gif
11 ms
97 ms
collect
55 ms
stenaline.se accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
stenaline.se 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
stenaline.se 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
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
SV
SV
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stenaline.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it matches the claimed language. Our system also found out that Stenaline.se 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.se
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: