4.6 sec in total
1.1 sec
3.4 sec
161 ms
Welcome to ferland.es homepage info - get ready to check Ferland best content right away, or after learning these important things about ferland.es
Shop powered by PrestaShop
Visit ferland.esWe analyzed Ferland.es page load time and found that the first response time was 1.1 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ferland.es performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value5.5 s
18/100
25%
Value10.7 s
7/100
10%
Value150 ms
95/100
30%
Value0.118
85/100
15%
Value12.9 s
13/100
10%
1091 ms
185 ms
249 ms
224 ms
232 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 87% of them (58 requests) were addressed to the original Ferland.es, 4% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ferland.es.
Page size can be reduced by 108.6 kB (14%)
754.8 kB
646.1 kB
In fact, the total size of Ferland.es main page is 754.8 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. 30% of websites need less resources to load. Javascripts take 346.0 kB which makes up the majority of the site volume.
Potential reduce by 29.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 29.0 kB or 76% of the original size.
Potential reduce by 13.4 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. Ferland images are well optimized though.
Potential reduce by 57.7 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 57.7 kB or 17% of the original size.
Potential reduce by 8.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. Ferland.es needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 26% of the original size.
Number of requests can be reduced by 39 (60%)
65
26
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ferland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
1091 ms
global.css
185 ms
jquery.fancybox.css
249 ms
blockcart.css
224 ms
blockcurrencies.css
232 ms
blocklanguages.css
233 ms
blocknewproducts.css
232 ms
jquery.autocomplete.css
309 ms
blocksearch.css
346 ms
blockspecials.css
358 ms
blockuserinfo.css
359 ms
blockpermanentlinks.css
359 ms
categoriestopmenu.css
366 ms
categoriestopmenu-responsive.css
430 ms
footercustom.css
463 ms
footercustom-responsive.css
478 ms
paypal.css
499 ms
timetable.css
500 ms
homecategories.css
493 ms
responsive.css
562 ms
css
42 ms
jquery-1.11.0.min.js
717 ms
jquery-migrate-1.2.1.min.js
613 ms
jquery.easing.js
655 ms
tools.js
634 ms
jquery.fancybox.js
623 ms
products-comparison.js
680 ms
ajax-cart.js
747 ms
jquery.scrollTo.js
762 ms
jquery.serialScroll.js
753 ms
jquery.bxslider.js
787 ms
jquery.autocomplete.js
813 ms
GoogleAnalyticActionLib.js
839 ms
js
75 ms
formstyle.js
870 ms
gridorlist.js
878 ms
quickview.js
880 ms
api.js
54 ms
hidraflex-1442917182.jpg
966 ms
1.jpg
966 ms
4.jpg
788 ms
13-category
862 ms
25-category
909 ms
55-category
830 ms
21-category
931 ms
49-category
983 ms
147-category
888 ms
310-category
878 ms
311-category
888 ms
312-category
908 ms
313-category
961 ms
314-category
965 ms
footer_img_1.png
983 ms
pago1.jpg
911 ms
pago2.jpg
906 ms
pago3.jpg
912 ms
cart.png
877 ms
carrito.png
877 ms
home.png
881 ms
dg45_pLmvrkcOkBnKsOzXyGWTBcmg-X6VjvYIg.ttf
20 ms
social_fb.png
881 ms
social_twi.png
892 ms
recaptcha__en.js
113 ms
analytics.js
53 ms
ec.js
50 ms
collect
12 ms
js
50 ms
ferland.es accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ferland.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
ferland.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ferland.es 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 Ferland.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.
ferland.es
Open Graph description is not detected on the main page of Ferland. 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: