6.1 sec in total
310 ms
5.6 sec
169 ms
Welcome to faiveley.com homepage info - get ready to check Faiveley best content right away, or after learning these important things about faiveley.com
Our objective is to enhance these exceptional Burgundian terroirs through a style that combines strength, finesse and elegance.
Visit faiveley.comWe analyzed Faiveley.com page load time and found that the first response time was 310 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
faiveley.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value9.2 s
1/100
25%
Value13.2 s
2/100
10%
Value1,930 ms
8/100
30%
Value0
100/100
15%
Value11.1 s
20/100
10%
310 ms
379 ms
163 ms
168 ms
174 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Faiveley.com, 91% (42 requests) were made to Faiveleytransport.com and 7% (3 requests) were made to Faiveley.symexbelgium.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Faiveleytransport.com.
Page size can be reduced by 154.9 kB (10%)
1.6 MB
1.4 MB
In fact, the total size of Faiveley.com main page is 1.6 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. 15% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 13.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. 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 13.1 kB or 77% of the original size.
Potential reduce by 38.9 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. Faiveley images are well optimized though.
Potential reduce by 63.3 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 63.3 kB or 69% of the original size.
Potential reduce by 39.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. Faiveley.com needs all CSS files to be minified and compressed as it can save up to 39.6 kB or 84% of the original size.
Number of requests can be reduced by 29 (66%)
44
15
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faiveley. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
faiveley.com
310 ms
www.faiveleytransport.com
379 ms
panels.css
163 ms
panels_ipe.css
168 ms
twocol_stacked.css
174 ms
onecol.css
184 ms
html-reset.css
185 ms
droppy.css
185 ms
pages.css
247 ms
jquery.fo.js
418 ms
drupal.js
258 ms
panels.js
273 ms
jquery.droppy.js
554 ms
jquery.jshowoff.min.js
276 ms
swfobject.js
328 ms
script.js
342 ms
logo.png
666 ms
btn-recherche.png
185 ms
drapeau-en.png
85 ms
disabled-fr.png
93 ms
bg-menu-haut.png
94 ms
c-gauche.gif
87 ms
images-home-gb_01_v2.png
4298 ms
images-home-gb_02.png
3332 ms
images-home-gb_01_0.png
4289 ms
bg-finance.png
1223 ms
capsule_home.php
1810 ms
bg-titre-bleu.png
242 ms
bg-lien-more.png
333 ms
bg-link-more.png
425 ms
bg-titre-violet.png
517 ms
bg-activity.png
2388 ms
bg-titre-vertb.png
715 ms
bg-market.png
1798 ms
bg-titre-orange.png
1281 ms
bg-degrade-finance.png
1372 ms
icone-pdf.png
1463 ms
fleche-orange.png
1556 ms
bg-degrade-bourse.png
1648 ms
bg-titre-vert.png
1738 ms
vignettes-home_01.png
2013 ms
vignettes-home_02.png
2131 ms
vignettes-home_03.png
2560 ms
bg-titre-vert.png
91 ms
bg-degrade-bourse.png
181 ms
print.css
85 ms
faiveley.com 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.
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
Links do not have a discernible name
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.
faiveley.com 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
faiveley.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faiveley.com 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 Faiveley.com 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.
faiveley.com
Open Graph description is not detected on the main page of Faiveley. 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: