Tools & Wizards About Us
fc-richwiller.footeo.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fc-richwiller.footeo.com

FC RED STAR RICHWILLER 1920 : site officiel du club de foot de Richwiller - footeo

Page Load Speed

3.8 sec in total

First Response

176 ms

Resources Loaded

3.1 sec

Page Rendered

505 ms

fc-richwiller.footeo.com screenshot

About Website

Click here to check amazing FC RICHWILLER Foot Eo content for France. Otherwise, check out these important facts you probably never knew about fc-richwiller.footeo.com

Bienvenue sur le site officiel du club FC RED STAR RICHWILLER 1920. Retrouvez toute l'actualité, le calendrier et les résultats des équipes, ainsi que toute la vie du club.

Visit fc-richwiller.footeo.com

Key Findings

We analyzed Fc-richwiller.footeo.com page load time and found that the first response time was 176 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

fc-richwiller.footeo.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value3,010 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

fc-richwiller.footeo.com

176 ms

fc-richwiller.footeo.com

643 ms

js

168 ms

clubeo-app__qcsgwx.js

537 ms

core.bundle.js

105 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Fc-richwiller.footeo.com, 39% (17 requests) were made to S1.static-footeo.com and 18% (8 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source S3.static-footeo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 914.6 kB (33%)

Content Size

2.7 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fc-richwiller.footeo.com main page is 2.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 117.8 kB

  • Original 138.4 kB
  • After minification 115.5 kB
  • After compression 20.6 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 22.9 kB, which is 17% 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 117.8 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 477.9 kB
  • After minification 476.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. FC RICHWILLER Foot Eo images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 793.8 kB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 1.2 MB

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 793.8 kB or 39% of the original size.

CSS Optimization

-2%

Potential reduce by 1.9 kB

  • Original 106.7 kB
  • After minification 106.7 kB
  • After compression 104.8 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. Fc-richwiller.footeo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (64%)

Requests Now

33

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FC RICHWILLER Foot Eo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fc-richwiller.footeo.com

fc-richwiller.footeo.com

176 ms

fc-richwiller.footeo.com

fc-richwiller.footeo.com

643 ms

js

js

168 ms

clubeo-app__qcsgwx.js

clubeo-app__qcsgwx.js

537 ms

core.bundle.js

core.bundle.js

105 ms

gpt.js

gpt.js

138 ms

xo73.js

xo73.js

548 ms

slm.prebid.footeo.js

slm.prebid.footeo.js

652 ms

jsapi

jsapi

52 ms

frontend_default__sh4n2l.css

frontend_default__sh4n2l.css

982 ms

specific__sa027s.css

specific__sa027s.css

518 ms

sdk.js

sdk.js

50 ms

loader.js

loader.js

42 ms

modernizr__qcsgww.js

modernizr__qcsgww.js

611 ms

common__sh4n2v.js

common__sh4n2v.js

1025 ms

frontend_default__sh4n2s.js

frontend_default__sh4n2s.js

1025 ms

search__sgtkjp.js

search__sgtkjp.js

711 ms

pubads_impl.js

pubads_impl.js

15 ms

sdk.js

sdk.js

11 ms

logo__76a9t1pr0.jpg

logo__76a9t1pr0.jpg

87 ms

banner__sae68s.jpg

banner__sae68s.jpg

315 ms

Montserrat-Medium__sa021n.ttf

Montserrat-Medium__sa021n.ttf

238 ms

Montserrat-Bold__sa021n.ttf

Montserrat-Bold__sa021n.ttf

670 ms

klavika-medium__sa021n.otf

klavika-medium__sa021n.otf

90 ms

klavika-bold__sa021n.otf

klavika-bold__sa021n.otf

238 ms

roboto-regular__qcsgwx.woff

roboto-regular__qcsgwx.woff

669 ms

roboto-bold__qcsgwx.woff

roboto-bold__qcsgwx.woff

672 ms

roboto-light__qcsgwx.woff

roboto-light__qcsgwx.woff

670 ms

icomoon__sa021n.ttf

icomoon__sa021n.ttf

317 ms

background__sa027s.jpg

background__sa027s.jpg

188 ms

no_shield__nqrpbx.png

no_shield__nqrpbx.png

281 ms

planning-des-rencontres-richwiller-du-24-et-25-aout__sih8a6.jpg

planning-des-rencontres-richwiller-du-24-et-25-aout__sih8a6.jpg

581 ms

20240811_112330__sicnjv.jpg

20240811_112330__sicnjv.jpg

581 ms

planning-des-rencontres-richwiller-du-12-et-18-aout7__sifeh2.jpg

planning-des-rencontres-richwiller-du-12-et-18-aout7__sifeh2.jpg

147 ms

sprite_big_members__qcsgwx.png

sprite_big_members__qcsgwx.png

436 ms

head__qcsgwx.gif

head__qcsgwx.gif

435 ms

loader.js

loader.js

104 ms

facebookSubdomainLogin

facebookSubdomainLogin

368 ms

tooltip.css

tooltip.css

5 ms

util.css

util.css

8 ms

jsapi_compiled_default_module.js

jsapi_compiled_default_module.js

13 ms

jsapi_compiled_graphics_module.js

jsapi_compiled_graphics_module.js

5 ms

jsapi_compiled_ui_module.js

jsapi_compiled_ui_module.js

24 ms

jsapi_compiled_corechart_module.js

jsapi_compiled_corechart_module.js

4 ms

Accessibility Review

fc-richwiller.footeo.com accessibility score

85

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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.

Best Practices

fc-richwiller.footeo.com best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

fc-richwiller.footeo.com SEO score

92

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

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 Fc-richwiller.footeo.com 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 Fc-richwiller.footeo.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.

Social Sharing Optimization

fc-richwiller.footeo.com

Open Graph description is not detected on the main page of FC RICHWILLER Foot Eo. 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: