4 sec in total
203 ms
3.5 sec
283 ms
Welcome to fubicy.org homepage info - get ready to check Fubicy best content for France right away, or after learning these important things about fubicy.org
La FUB, Fédération française des Usagers de la Bicyclette, agit pour apporter des réponses concrètes aux préoccupations quotidiennes des cyclistes et promouvoir l’usage du vélo comme mode de déplaceme...
Visit fubicy.orgWe analyzed Fubicy.org page load time and found that the first response time was 203 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fubicy.org performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value10.2 s
0/100
25%
Value7.8 s
24/100
10%
Value1,200 ms
21/100
30%
Value0.537
14/100
15%
Value8.5 s
37/100
10%
203 ms
716 ms
97 ms
189 ms
190 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fubicy.org, 88% (29 requests) were made to Fub.fr and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Fub.fr.
Page size can be reduced by 354.9 kB (6%)
5.5 MB
5.1 MB
In fact, the total size of Fubicy.org main page is 5.5 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. 45% of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 37.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 37.0 kB or 78% of the original size.
Potential reduce by 69.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. Fubicy images are well optimized though.
Potential reduce by 152.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 152.6 kB or 66% of the original size.
Potential reduce by 95.4 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. Fubicy.org needs all CSS files to be minified and compressed as it can save up to 95.4 kB or 80% of the original size.
Number of requests can be reduced by 13 (50%)
26
13
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fubicy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
fubicy.org
203 ms
www.fub.fr
716 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
97 ms
css_WEB7VIop18CWg6cZjfF0ou3UQr7DxCY0hJ-S9dhO9RI.css
189 ms
css_9ZywY7OqVdOtyl-O9m9560EkcRZ4gahEkubNKZMgaNM.css
190 ms
css_AxQ1PBTGV0FtNmsiS0WtrSqiP0CsMJ-jLdjbCPrtA-g.css
192 ms
css_8DCGJ_wc8qjygFpnL2WnHJBhT0S8sinoXNEa8IUOo7w.css
198 ms
css__1bgOBnrGeK-W5gYCva-9Xl9z_8lHj5dqgL40XJregQ.css
193 ms
css_eGozKOEDn6ua7O11tXCBOAjTfer9PbnNlFRQ16vjDwM.css
202 ms
jquery-1.8.3.min.js
79 ms
js_IkgOrrVZK1UTp2HktvFi5vo1g7b25Muyr5GoySikuic.js
290 ms
js_R9UbiVw2xuTUI0GZoaqMDOdX0lrZtgX-ono8RVOUEVc.js
289 ms
js_T4Kt7xZSW2C965s0mW7Pl1kd7NzJTQfbgLrQjnqNb_I.js
391 ms
js_0tdiPU5igSiW9oC0AuWAq6LGGl-LUZjUJMvTZiwinT4.js
301 ms
js_diWL3aQY3h6RRBatVIE0RJfaXsBie-hoJ861ArHzvB0.js
312 ms
js_OudaiXesV_qdKiezwdZu3VF74iVn8VOiYymFT6CpQws.js
329 ms
analytics.js
139 ms
logo.png
123 ms
velocite-accueil.jpg
221 ms
carte-reseau.jpg
398 ms
logo.svg
294 ms
fontawesome-webfont.woff
303 ms
formata-regular-webfont.woff
205 ms
fontawesome-webfont.woff
302 ms
formata-light-webfont.woff
302 ms
blockbe-condensed-webfont.woff
399 ms
collect
13 ms
pictogramme.jpg
1094 ms
atelier.jpg
912 ms
velo.jpg
1113 ms
sonnette.jpg
590 ms
velo_parade.jpg
1883 ms
stationnement.jpg
1580 ms
fubicy.org accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
fubicy.org 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
fubicy.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fubicy.org 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 Fubicy.org 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.
fubicy.org
Open Graph description is not detected on the main page of Fubicy. 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: