Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fse.gouv.fr

Accueil | FSE

Page Load Speed

4.7 sec in total

First Response

276 ms

Resources Loaded

3.2 sec

Page Rendered

1.2 sec

About Website

Click here to check amazing FSE content for France. Otherwise, check out these important facts you probably never knew about fse.gouv.fr

Visit fse.gouv.fr

Key Findings

We analyzed Fse.gouv.fr page load time and found that the first response time was 276 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

fse.gouv.fr performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.088

93/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

fse.gouv.fr

276 ms

fse.gouv.fr

572 ms

xcX649.js

1092 ms

tarteaucitron.js

344 ms

tarteaucitron.services.js

349 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 82% of them (23 requests) were addressed to the original Fse.gouv.fr, 7% (2 requests) were made to Cnuw.fse.gouv.fr and 7% (2 requests) were made to App.mailjet.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Fse.gouv.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (26%)

Content Size

12.8 MB

After Optimization

9.5 MB

In fact, the total size of Fse.gouv.fr main page is 12.8 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. 25% of websites need less resources to load. Images take 12.4 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 103.4 kB

  • Original 152.0 kB
  • After minification 129.4 kB
  • After compression 48.5 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.5 kB, which is 15% 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 103.4 kB or 68% of the original size.

Image Optimization

-26%

Potential reduce by 3.2 MB

  • Original 12.4 MB
  • After minification 9.2 MB

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, FSE needs image optimization as it can save up to 3.2 MB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 15.8 kB

  • Original 268.7 kB
  • After minification 268.7 kB
  • After compression 252.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 617 B

  • Original 4.6 kB
  • After minification 4.6 kB
  • After compression 4.0 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. Fse.gouv.fr needs all CSS files to be minified and compressed as it can save up to 617 B or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (35%)

Requests Now

20

After Optimization

13

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FSE. 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 as a result speed up the page load time.

Accessibility Review

fse.gouv.fr accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

fse.gouv.fr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

fse.gouv.fr SEO score

86

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 Fse.gouv.fr 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 Fse.gouv.fr 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

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