5.3 sec in total
368 ms
4.7 sec
286 ms
Visit aferry.es now to see the best up-to-date AFerry content for Spain and also check out these interesting facts you probably never knew about aferry.es
Reserva ferris a Europa y más allá. ✔ Todas las navieras. ✔ Todas las rutas. ✔ Tus billetes de ferry al mejor precio. ✔ Comparador de tarifas. ✔ Las últimas ofertas. ✔ 100% Seguro.
Visit aferry.esWe analyzed Aferry.es page load time and found that the first response time was 368 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
aferry.es performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value7.3 s
5/100
25%
Value3.8 s
84/100
10%
Value440 ms
63/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
368 ms
2142 ms
479 ms
494 ms
210 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 63% of them (29 requests) were addressed to the original Aferry.es, 24% (11 requests) were made to Static.webres.co.uk and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Aferry.es.
Page size can be reduced by 1.2 MB (69%)
1.8 MB
553.2 kB
In fact, the total size of Aferry.es main page is 1.8 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. 25% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 53.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 14.5 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 53.8 kB or 81% of the original size.
Potential reduce by 60.0 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, AFerry needs image optimization as it can save up to 60.0 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 970.6 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 970.6 kB or 83% of the original size.
Potential reduce by 151.6 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.es needs all CSS files to be minified and compressed as it can save up to 151.6 kB or 87% of the original size.
Number of requests can be reduced by 24 (59%)
41
17
The browser has sent 41 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 25 to 1 for JavaScripts and as a result speed up the page load time.
aferry.es
368 ms
www.aferry.es
2142 ms
af_eng.css
479 ms
af_style.css
494 ms
smartbanner.css
210 ms
jquery-1.11.3.js
1518 ms
jquery-ui-1.11.4.js
1765 ms
modernizr-2.8.3.js
398 ms
testimonial-dialog.js
193 ms
googlemapdialog.js
195 ms
jquery.visible.js
100 ms
googlemapshelper.js
100 ms
event-debouncer.js
193 ms
jquery.flexslider-min.js
196 ms
flexslider-functions.js
194 ms
testimonials-panel.js
226 ms
review-panel.js
297 ms
timetabledetails-panel.js
301 ms
jquery.smartbanner.js
299 ms
cms.js
831 ms
af_nav.js
405 ms
jquery.color-2.1.1.js
409 ms
afs-ferryscanner.js
1317 ms
calendar-ferryscanner.js
1004 ms
imagepanner.js
906 ms
tabs.js
926 ms
MapsTabs.js
1002 ms
gtm.js
85 ms
af_logo-aferry.es.png
129 ms
aferry-sprite.png
381 ms
af_flag-spain.png
99 ms
afeng.png
656 ms
OpenSans-Regular-webfont.woff
421 ms
htOper-TRAS-11.jpg
620 ms
grimaldi-lines-es-june.jpg
182 ms
htLoca-Morocco-3.jpg
199 ms
htOper-CMAC-7.jpg
313 ms
htOper-STEN-5.jpg
215 ms
htOper-GRIF-5.jpg
306 ms
af_app-apple-logo-aferry.es.png
252 ms
af_app-google-logo-aferry.es.png
258 ms
analytics.js
59 ms
bat.js
57 ms
collect
12 ms
collect
61 ms
ga-audiences
33 ms
aferry.es accessibility score
aferry.es 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
Page has valid source maps
aferry.es SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aferry.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Aferry.es 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.
aferry.es
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: