Tools & Wizards About Us
aferry.to screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

aferry.to

Ferry Tickets - Compare Ferry Prices & Crossings | AFerry

Page Load Speed

54.7 sec in total

First Response

401 ms

Resources Loaded

45 sec

Page Rendered

9.3 sec

aferry.to screenshot

About Website

Click here to check amazing AFerry content for Canada. Otherwise, check out these important facts you probably never knew about aferry.to

Compare prices for all the ferry companies and all the routes. See all the latest ferry deals. AFerry: The World's Leading Ferry Website. Save money today.

Visit aferry.to

Key Findings

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

Performance Metrics

aferry.to performance score

0

Network Requests Diagram

aferry.to

401 ms

www.aferry.co.uk

1785 ms

core_style.css

1348 ms

core_eng.css

1347 ms

af_style.css

1504 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Aferry.to, 30% (13 requests) were made to Static.aferry.co.uk and 26% (11 requests) were made to Aferry.co.uk. The less responsive or slowest element that took the longest time to load (18.5 sec) relates to the external source Bat.bing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (59%)

Content Size

2.4 MB

After Optimization

967.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aferry.to main page is 2.4 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. 55% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 91.9 kB

  • Original 115.0 kB
  • After minification 90.4 kB
  • After compression 23.1 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 24.6 kB, which is 21% 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 91.9 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 61.2 kB

  • Original 670.7 kB
  • After minification 609.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. AFerry images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 995.8 kB

  • Original 1.3 MB
  • After minification 820.0 kB
  • After compression 281.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 995.8 kB or 78% of the original size.

CSS Optimization

-84%

Potential reduce by 270.9 kB

  • Original 324.3 kB
  • After minification 261.8 kB
  • After compression 53.3 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. Aferry.to needs all CSS files to be minified and compressed as it can save up to 270.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (45%)

Requests Now

38

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aferry.to

aferry.to

401 ms

www.aferry.co.uk

www.aferry.co.uk

1785 ms

core_style.css

core_style.css

1348 ms

core_eng.css

core_eng.css

1347 ms

af_style.css

af_style.css

1504 ms

af_eng.css

af_eng.css

1504 ms

smartbanner.css

smartbanner.css

1502 ms

jqueryandui

jqueryandui

478 ms

contentbundle_15399

contentbundle_15399

751 ms

afrrydstl.js

afrrydstl.js

750 ms

FerryScanner

FerryScanner

750 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

1039 ms

gtm.js

gtm.js

1687 ms

af_logo-aferry.co.uk.png

af_logo-aferry.co.uk.png

666 ms

aferry-sprite.svgz

aferry-sprite.svgz

936 ms

afeng.svgz

afeng.svgz

770 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

704 ms

af_app-apple-logo-aferry.co.uk.png

af_app-apple-logo-aferry.co.uk.png

102 ms

af_app-google-logo-aferry.co.uk.png

af_app-google-logo-aferry.co.uk.png

428 ms

analytics.js

analytics.js

17748 ms

bat.js

bat.js

18513 ms

fbevents.js

fbevents.js

18246 ms

af_flag-united-kingdom.png

af_flag-united-kingdom.png

5548 ms

htOper-DFDS-deal-24hrs-return-button.jpg

htOper-DFDS-deal-24hrs-return-button.jpg

11502 ms

index.html

index.html

5226 ms

htOper-DFDS-deal-72hrs-return-button.jpg

htOper-DFDS-deal-72hrs-return-button.jpg

6517 ms

htOper-DFDS-deal-120hrs-return-button.jpg

htOper-DFDS-deal-120hrs-return-button.jpg

6516 ms

htOper-BRIT-offer-138gbp-car2-button.jpg

htOper-BRIT-offer-138gbp-car2-button.jpg

6516 ms

htOper-POXX-offer-15pc-off-button.jpg

htOper-POXX-offer-15pc-off-button.jpg

6760 ms

htOper-STEN-deal-50pc-holland-button.jpg

htOper-STEN-deal-50pc-holland-button.jpg

6834 ms

pets-july2011.jpg

pets-july2011.jpg

827 ms

collect

collect

6217 ms

sprite_star.png

sprite_star.png

5688 ms

collect

collect

938 ms

main.js

main.js

559 ms

432105023817755

432105023817755

506 ms

ga-audiences

ga-audiences

1399 ms

a

a

724 ms

472 ms

base-data

base-data

341 ms

nr-spa-1044.min.js

nr-spa-1044.min.js

345 ms

eu1e2e476734e9c50411eb2618ba7d4bb1a.js

eu1e2e476734e9c50411eb2618ba7d4bb1a.js

944 ms

c8380cba8f

c8380cba8f

155 ms

SEO Factors

aferry.to SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

aferry.to

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