4.1 sec in total
239 ms
3.5 sec
282 ms
Visit stenaline.nl now to see the best up-to-date Stena Line content for Netherlands and also check out these interesting facts you probably never knew about stenaline.nl
Reis naar het Verenigd Koninkrijk, Ierland, Nederland en Noord-Europa met Stena Line. Bekijk onze routes, ferry’s, speciale aanbiedingen en veel meer. Boek online voor de beste tarieven.
Visit stenaline.nlWe analyzed Stenaline.nl page load time and found that the first response time was 239 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
stenaline.nl performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value8.9 s
1/100
25%
Value4.9 s
65/100
10%
Value1,440 ms
15/100
30%
Value0.08
94/100
15%
Value10.6 s
23/100
10%
239 ms
376 ms
283 ms
202 ms
203 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 58% of them (46 requests) were addressed to the original Stenaline.nl, 11% (9 requests) were made to Tags.tiqcdn.com and 9% (7 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Tags.tiqcdn.com.
Page size can be reduced by 370.6 kB (48%)
768.5 kB
397.9 kB
In fact, the total size of Stenaline.nl main page is 768.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 396.1 kB which makes up the majority of the site volume.
Potential reduce by 70.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 19.4 kB, which is 23% 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 70.7 kB or 82% of the original size.
Potential reduce by 30.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 30.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 269.5 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 269.5 kB or 68% of the original size.
Number of requests can be reduced by 58 (78%)
74
16
The browser has sent 74 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 49 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
stenaline.nl
239 ms
www.stenaline.nl
376 ms
jquery
283 ms
globalSettings
202 ms
settings_nl-NL
203 ms
stena-map-widget-css
204 ms
stena-map-widget
319 ms
SiteCss
219 ms
SiteMainLessCss
498 ms
componentCss
302 ms
restrictedContentJs
306 ms
modernizrAndInlineBootstrapingJs
329 ms
bvapi.js
155 ms
resourcetexts.aspx
374 ms
resourcetexts.aspx
386 ms
backboneJs
559 ms
utag.sync.js
353 ms
WebResource.axd
585 ms
ScriptResource.axd
585 ms
ScriptResource.axd
384 ms
clientTemplatesJs
485 ms
backboneModels
572 ms
jqueryEffectsCore
515 ms
jqueryui
815 ms
globalPropertiesJs
529 ms
datePickerLocalizationJs
552 ms
componentJs
672 ms
modulesJs
845 ms
scripthandler
622 ms
bootstrap
663 ms
IeFixes
664 ms
bakgrund-winter.ashx
558 ms
bv.js
59 ms
mmcore.js
15 ms
j.php
8 ms
v.gif
13 ms
16 ms
magpie.js
90 ms
logo.ashx
219 ms
ajax-loader.gif
214 ms
stena-line-logo.ashx
236 ms
ferries-naar-engeland.ashx
337 ms
ferries-naar-ierland.ashx
336 ms
ferries-naar-zweden.ashx
398 ms
ferries-naar-noorwegen.ashx
397 ms
utag.js
95 ms
sprite.png
516 ms
selector-shadow.gif
380 ms
shadowDown.png
381 ms
ITCFranklinGothicW02-Dm812954.woff
637 ms
ITCFranklinGothicW10-Dm862375.woff
514 ms
655 ms
LoginService.ashx
117 ms
head
130 ms
body
159 ms
utag.882.js
9 ms
utag.1038.js
263 ms
utag.1055.js
1914 ms
utag.1054.js
263 ms
utag.1070.js
264 ms
utag.1043.js
264 ms
utag.1089.js
14 ms
analytics.js
23 ms
sdk.js
183 ms
ga.js
12 ms
__utm.gif
16 ms
__utm.gif
39 ms
183 ms
xd_arbiter.php
161 ms
xd_arbiter.php
262 ms
gtm.js
55 ms
conversion_async.js
22 ms
SessionCam-tag-v5-5.js
101 ms
85 ms
collect
23 ms
linkid.js
23 ms
47 ms
collect
11 ms
104 ms
stenaline.nl accessibility score
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
stenaline.nl 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
stenaline.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stenaline.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Stenaline.nl 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.nl
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: