Tools & Wizards About Us
poferries.be screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

poferries.be

Poferries

Page Load Speed

3.2 sec in total

First Response

348 ms

Resources Loaded

2.5 sec

Page Rendered

348 ms

poferries.be screenshot

About Website

Visit poferries.be now to see the best up-to-date Poferries content and also check out these interesting facts you probably never knew about poferries.be

Visit poferries.be

Key Findings

We analyzed Poferries.be page load time and found that the first response time was 348 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

poferries.be performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value7,170 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value33.2 s

0/100

10%

Network Requests Diagram

poferries.be

348 ms

portal

254 ms

portal

329 ms

fr-be

410 ms

genesys.min.js

574 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Poferries.be, 46% (24 requests) were made to Po-ecom-prod-xp-93-113810-cd-cdn.azureedge.net and 13% (7 requests) were made to Poferries.com. The less responsive or slowest element that took the longest time to load (872 ms) relates to the external source Analytics.poferries.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.8 kB (24%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Poferries.be main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 805.5 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 194.5 kB

  • Original 221.3 kB
  • After minification 183.0 kB
  • After compression 26.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 38.3 kB, which is 17% 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 194.5 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 2.5 kB

  • Original 485.3 kB
  • After minification 482.8 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. Poferries images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 161.2 kB

  • Original 805.5 kB
  • After minification 805.5 kB
  • After compression 644.2 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 161.2 kB or 20% of the original size.

CSS Optimization

-30%

Potential reduce by 48.6 kB

  • Original 159.7 kB
  • After minification 159.7 kB
  • After compression 111.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Poferries.be needs all CSS files to be minified and compressed as it can save up to 48.6 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (57%)

Requests Now

42

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poferries. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

poferries.be

poferries.be

348 ms

portal

portal

254 ms

portal

portal

329 ms

fr-be

fr-be

410 ms

genesys.min.js

genesys.min.js

574 ms

uc.js

uc.js

61 ms

20391842497.js

20391842497.js

129 ms

bundle.min.css

bundle.min.css

57 ms

js

js

76 ms

ProphetInsert.js

ProphetInsert.js

299 ms

VisitorIdentification.js

VisitorIdentification.js

326 ms

jquery.min.js

jquery.min.js

56 ms

jquery-migrate-3.3.0.min.js

jquery-migrate-3.3.0.min.js

50 ms

glassvox.min.js

glassvox.min.js

62 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

49 ms

jquery-calendar.css

jquery-calendar.css

414 ms

bundle.min.js

bundle.min.js

16 ms

offers.js

offers.js

17 ms

farefinder.min.js

farefinder.min.js

17 ms

passenger.min.js

passenger.min.js

22 ms

vehicleCO.min.js

vehicleCO.min.js

22 ms

minicruisedetails.js

minicruisedetails.js

21 ms

geo4.js

geo4.js

148 ms

gtm.js

gtm.js

132 ms

gtm.js

gtm.js

98 ms

session.json

session.json

872 ms

detector-dom.min.js

detector-dom.min.js

22 ms

amzn.js

amzn.js

34 ms

hrhc6p6pt5

hrhc6p6pt5

104 ms

logo.png

logo.png

19 ms

allaboardhomepage.png

allaboardhomepage.png

32 ms

mini-cruise-pod-harrogate.jpg

mini-cruise-pod-harrogate.jpg

20 ms

minicruise-eu-homepage-pod.jpg

minicruise-eu-homepage-pod.jpg

19 ms

bath-abbey-in-bath.jpg

bath-abbey-in-bath.jpg

19 ms

brighton-beach-sunrise.jpg

brighton-beach-sunrise.jpg

18 ms

christchurch-dorset.jpg

christchurch-dorset.jpg

20 ms

2024-sailings-doca-view.jpg

2024-sailings-doca-view.jpg

16 ms

MuseoSans-500.otf

MuseoSans-500.otf

12 ms

config.js

config.js

32 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

32 ms

a20391842497.html

a20391842497.html

710 ms

detector-bootstrap_es5.min.js

detector-bootstrap_es5.min.js

43 ms

calendar.svg

calendar.svg

21 ms

mini-cruise-pod-harrogate.jpg

mini-cruise-pod-harrogate.jpg

79 ms

minicruise-eu-homepage-pod.jpg

minicruise-eu-homepage-pod.jpg

80 ms

MuseoSans-700.otf

MuseoSans-700.otf

77 ms

SF-UI-Text-Light.woff

SF-UI-Text-Light.woff

78 ms

fr-be

fr-be

668 ms

clarity.js

clarity.js

16 ms

SF-UI-Text-Medium.woff

SF-UI-Text-Medium.woff

24 ms

sign-in-footer-bg.svg

sign-in-footer-bg.svg

22 ms

c.gif

c.gif

7 ms

Accessibility Review

poferries.be accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Document doesn't have a <title> element

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

poferries.be best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

poferries.be SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poferries.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Poferries.be 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

poferries.be

Open Graph description is not detected on the main page of Poferries. 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: