3.4 sec in total
287 ms
2.9 sec
222 ms
Visit stenaline.pl now to see the best up-to-date Stena Line content for Poland and also check out these interesting facts you probably never knew about stenaline.pl
Podróżuj ze Stena Line do Wielkiej Brytanii, Irlandii, Holandii i północnej Europy. Zapoznaj się z trasami, promami, ofertami specjalnymi i nie tylko. Zarezerwuj online, aby uzyskać najlepszą cenę.
Visit stenaline.plWe analyzed Stenaline.pl page load time and found that the first response time was 287 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
stenaline.pl performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value9.6 s
0/100
25%
Value6.3 s
42/100
10%
Value2,990 ms
3/100
30%
Value0.096
90/100
15%
Value12.4 s
15/100
10%
287 ms
583 ms
289 ms
191 ms
192 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 41% of them (46 requests) were addressed to the original Stenaline.pl, 11% (12 requests) were made to Eu-sonar.sociomantic.com and 8% (9 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (874 ms) belongs to the original domain Stenaline.pl.
Page size can be reduced by 366.3 kB (48%)
767.5 kB
401.1 kB
In fact, the total size of Stenaline.pl main page is 767.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. 65% of websites need less resources to load. Javascripts take 383.6 kB which makes up the majority of the site volume.
Potential reduce by 75.8 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.4 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 75.8 kB or 81% of the original size.
Potential reduce by 30.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. Obviously, Stena Line needs image optimization as it can save up to 30.6 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 260.0 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 260.0 kB or 68% of the original size.
Number of requests can be reduced by 88 (85%)
104
16
The browser has sent 104 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.
stenaline.pl
287 ms
www.stenaline.pl
583 ms
jquery
289 ms
globalSettings
191 ms
settings_pl-PL
192 ms
stena-map-widget-css
201 ms
stena-map-widget
314 ms
SiteCss
216 ms
SiteMainLessCss
474 ms
componentCss
285 ms
restrictedContentJs
303 ms
modernizrAndInlineBootstrapingJs
324 ms
bvapi.js
136 ms
resourcetexts.aspx
381 ms
resourcetexts.aspx
379 ms
backboneJs
545 ms
utag.sync.js
106 ms
WebResource.axd
559 ms
ScriptResource.axd
560 ms
ScriptResource.axd
541 ms
clientTemplatesJs
456 ms
backboneModels
572 ms
jqueryEffectsCore
480 ms
jqueryui
874 ms
globalPropertiesJs
505 ms
datePickerLocalizationJs
546 ms
componentJs
675 ms
modulesJs
677 ms
scripthandler
604 ms
bootstrap
644 ms
IeFixes
676 ms
bakgrund-winter.ashx
598 ms
bv.js
58 ms
mmcore.js
25 ms
j.php
22 ms
v.gif
9 ms
12 ms
logo.ashx
239 ms
ajax-loader.gif
262 ms
stena-line-logo.ashx
250 ms
nasze_promy_hub.ashx
254 ms
rejsy_turystyczne_hub.ashx
343 ms
gdynia_karlskrona_hub.ashx
344 ms
do_szwecji_hub.ashx
348 ms
magpie.js
172 ms
utag.js
146 ms
sprite.png
565 ms
selector-shadow.gif
454 ms
shadowDown.png
453 ms
ITCFranklinGothicW02-Dm812954.woff
625 ms
ITCFranklinGothicW10-Dm862375.woff
653 ms
230 ms
LoginService.ashx
155 ms
head
127 ms
body
127 ms
utag.1661.js
13 ms
utag.1689.js
5 ms
utag.1666.js
6 ms
utag.1678.js
10 ms
utag.1677.js
6 ms
utag.1692.js
10 ms
utag.1715.js
14 ms
conversion_async.js
24 ms
SessionCam-tag-v5-5.js
185 ms
plusone.js
181 ms
stenaline-pl
245 ms
gtm.js
43 ms
sdk.js
123 ms
78 ms
analytics.js
91 ms
148 ms
84 ms
ga.js
68 ms
219 ms
collect
67 ms
xd_arbiter.php
67 ms
xd_arbiter.php
95 ms
cb=gapi.loaded_0
63 ms
sessioncam.recorder.js
41 ms
__utm.gif
37 ms
__utm.gif
38 ms
view
101 ms
config.aspx
43 ms
UserMatch.ashx
16 ms
sync.cgi
266 ms
rum
20 ms
serve
23 ms
18 ms
pixel
59 ms
usersync
18 ms
match
83 ms
Pug
53 ms
70 ms
info.php
330 ms
tg-03.yieldpartners.com
198 ms
u.php
98 ms
merge
8 ms
39 ms
rum
35 ms
sd
33 ms
match
98 ms
match
395 ms
match
183 ms
match
187 ms
match
163 ms
match
394 ms
cm.gif
19 ms
mapuser
90 ms
match
107 ms
match
101 ms
match
102 ms
match
102 ms
tap.php
252 ms
stenaline.pl 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.pl 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
Missing source maps for large first-party JavaScript
stenaline.pl 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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stenaline.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Stenaline.pl 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.pl
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: