Tools & Wizards About Us
fubicy.org screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fubicy.org

Fédération française des usagers de la bicyclette | Le vélo au quotidien

Page Load Speed

2.9 sec in total

First Response

245 ms

Resources Loaded

2.4 sec

Page Rendered

181 ms

fubicy.org screenshot

About Website

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.org

Key Findings

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

Performance Metrics

fubicy.org performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.471

18/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

fubicy.org

245 ms

www.fub.fr

341 ms

www.fub.fr

633 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

190 ms

css_dWBHPbSQWh-19e3Bc29cTHIsefj--RoEVftmVdOAMn4.css

265 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fubicy.org, 92% (34 requests) were made to Fub.fr and 3% (1 request) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (633 ms) relates to the external source Fub.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.5 kB (17%)

Content Size

1.0 MB

After Optimization

865.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fubicy.org main page is 1.0 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. 30% of websites need less resources to load. Images take 851.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 40.7 kB

  • Original 52.9 kB
  • After minification 51.4 kB
  • After compression 12.3 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 40.7 kB or 77% of the original size.

Image Optimization

-11%

Potential reduce by 90.3 kB

  • Original 851.0 kB
  • After minification 760.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. Obviously, Fubicy needs image optimization as it can save up to 90.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-36%

Potential reduce by 38.0 kB

  • Original 105.0 kB
  • After minification 101.3 kB
  • After compression 67.0 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 38.0 kB or 36% of the original size.

CSS Optimization

-18%

Potential reduce by 5.6 kB

  • Original 31.0 kB
  • After minification 31.0 kB
  • After compression 25.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 5.6 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (52%)

Requests Now

29

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 29 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 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fubicy.org

fubicy.org

245 ms

www.fub.fr

www.fub.fr

341 ms

www.fub.fr

www.fub.fr

633 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

190 ms

css_dWBHPbSQWh-19e3Bc29cTHIsefj--RoEVftmVdOAMn4.css

css_dWBHPbSQWh-19e3Bc29cTHIsefj--RoEVftmVdOAMn4.css

265 ms

css_1RVKPmjtnvePoLMEUB3Yru2hJOhB_oy822SaPJaxDxY.css

css_1RVKPmjtnvePoLMEUB3Yru2hJOhB_oy822SaPJaxDxY.css

293 ms

css_O0rTFPOd6CgqX5aeEXoVpqP5OrrbbAT1WTYR_MZn3Ds.css

css_O0rTFPOd6CgqX5aeEXoVpqP5OrrbbAT1WTYR_MZn3Ds.css

312 ms

css_wNj-ZYGRW4aKrxCZyc3_CiDn0Rc6YkarMbKnOoDhfLA.css

css_wNj-ZYGRW4aKrxCZyc3_CiDn0Rc6YkarMbKnOoDhfLA.css

373 ms

css_XXQxtEj4fX5yP5f72U5q5YMaRokYltqzbiS1YHB18uE.css

css_XXQxtEj4fX5yP5f72U5q5YMaRokYltqzbiS1YHB18uE.css

353 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

20 ms

js_uJR3Qfgc-bGacxkh36HU9Xm2Q98e_V5UWlFISwie5ro.js

js_uJR3Qfgc-bGacxkh36HU9Xm2Q98e_V5UWlFISwie5ro.js

426 ms

js_TVTqjz8JHRb2KK9hlzuk0YsjzD013dKyYX_OTz-2VXU.js

js_TVTqjz8JHRb2KK9hlzuk0YsjzD013dKyYX_OTz-2VXU.js

393 ms

js_R9UbiVw2xuTUI0GZoaqMDOdX0lrZtgX-ono8RVOUEVc.js

js_R9UbiVw2xuTUI0GZoaqMDOdX0lrZtgX-ono8RVOUEVc.js

409 ms

js_Xjx7_A44o1f5sWr-0nemEcwq3vZzCD573u62j0fNQQw.js

js_Xjx7_A44o1f5sWr-0nemEcwq3vZzCD573u62j0fNQQw.js

524 ms

js

js

64 ms

js_rdCx_LX20p-ZlKYkiqQdMPygG6P-P9djOpnSuTJzvsY.js

js_rdCx_LX20p-ZlKYkiqQdMPygG6P-P9djOpnSuTJzvsY.js

450 ms

js_0tdiPU5igSiW9oC0AuWAq6LGGl-LUZjUJMvTZiwinT4.js

js_0tdiPU5igSiW9oC0AuWAq6LGGl-LUZjUJMvTZiwinT4.js

470 ms

js_diWL3aQY3h6RRBatVIE0RJfaXsBie-hoJ861ArHzvB0.js

js_diWL3aQY3h6RRBatVIE0RJfaXsBie-hoJ861ArHzvB0.js

479 ms

js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js

js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js

423 ms

js_b5uBqrfPrs_UEmgBeVFSOcXgjdijNE3mS-ZnwQ0jdnU.js

js_b5uBqrfPrs_UEmgBeVFSOcXgjdijNE3mS-ZnwQ0jdnU.js

543 ms

logo.png

logo.png

118 ms

congres2024.png

congres2024.png

615 ms

cp_fub_240426.jpg

cp_fub_240426.jpg

214 ms

site_actu_880x400.jpg

site_actu_880x400.jpg

158 ms

rev_save_the_date_880x400_0.jpg

rev_save_the_date_880x400_0.jpg

340 ms

mai_velo_2024.png

mai_velo_2024.png

576 ms

bg-reseau.png

bg-reseau.png

218 ms

bg-veloecole.png

bg-veloecole.png

256 ms

bg-alveole.png

bg-alveole.png

313 ms

bg-actuvelo.png

bg-actuvelo.png

331 ms

bg-parlonsvelo.png

bg-parlonsvelo.png

353 ms

logo.svg

logo.svg

395 ms

formata-light-webfont.woff

formata-light-webfont.woff

407 ms

formata-regular-webfont.woff

formata-regular-webfont.woff

326 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

449 ms

blockbe-condensed-webfont.woff

blockbe-condensed-webfont.woff

428 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

587 ms

Accessibility Review

fubicy.org accessibility score

74

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fubicy.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fubicy.org SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    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.

Social Sharing Optimization

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: