Tools & Wizards About Us
francesoir.fr screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

francesoir.fr

Francesoir.fr - L'actualité politique, économie, tendances et culture

Page Load Speed

6.9 sec in total

First Response

337 ms

Resources Loaded

3.5 sec

Page Rendered

3 sec

francesoir.fr screenshot

About Website

Welcome to francesoir.fr homepage info - get ready to check Francesoir best content for France right away, or after learning these important things about francesoir.fr

Suivez l'actualité du moment, média gratuit et indépendant. Politique, économie, culture, tendance, sport, santé, écologie… toute l'info en continu.

Visit francesoir.fr

Key Findings

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

Performance Metrics

francesoir.fr performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value14.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.3 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.553

13/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

francesoir.fr

337 ms

www.francesoir.fr

1532 ms

load.js

574 ms

css_dhiV3xNPmuKcuWfwJLnwTU7KAsWrvVRBFS-dyJg9LZ4.css

238 ms

css_1rKjOEBtRhvcdM-2qxHxvbYFM4ZAmBPxt4qIoa18GWg.css

388 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 41% of them (20 requests) were addressed to the original Francesoir.fr, 18% (9 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Matomo.pprod.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Francesoir.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 878.4 kB (20%)

Content Size

4.3 MB

After Optimization

3.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Francesoir.fr main page is 4.3 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. 65% of websites need less resources to load. HTML takes 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-28%

Potential reduce by 844.6 kB

  • Original 3.0 MB
  • After minification 2.9 MB
  • After compression 2.1 MB

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

Image Optimization

-11%

Potential reduce by 32.1 kB

  • Original 285.2 kB
  • After minification 253.1 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, Francesoir needs image optimization as it can save up to 32.1 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

-0%

Potential reduce by 283 B

  • Original 950.1 kB
  • After minification 950.1 kB
  • After compression 949.8 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

-1%

Potential reduce by 1.4 kB

  • Original 99.0 kB
  • After minification 99.0 kB
  • After compression 97.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. Francesoir.fr has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (73%)

Requests Now

37

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

francesoir.fr

francesoir.fr

337 ms

www.francesoir.fr

www.francesoir.fr

1532 ms

load.js

load.js

574 ms

css_dhiV3xNPmuKcuWfwJLnwTU7KAsWrvVRBFS-dyJg9LZ4.css

css_dhiV3xNPmuKcuWfwJLnwTU7KAsWrvVRBFS-dyJg9LZ4.css

238 ms

css_1rKjOEBtRhvcdM-2qxHxvbYFM4ZAmBPxt4qIoa18GWg.css

css_1rKjOEBtRhvcdM-2qxHxvbYFM4ZAmBPxt4qIoa18GWg.css

388 ms

css2

css2

30 ms

all.min.js

all.min.js

956 ms

v4-shims.min.js

v4-shims.min.js

265 ms

js_WKDZQPdEAhKEZCUAQOq86_81ri2VCRodKsYnVfNW26g.js

js_WKDZQPdEAhKEZCUAQOq86_81ri2VCRodKsYnVfNW26g.js

314 ms

sib-styles.css

sib-styles.css

254 ms

main.js

main.js

398 ms

nadz-sdk.js

nadz-sdk.js

482 ms

sdk.js

sdk.js

370 ms

matomo.js

matomo.js

1011 ms

container_LFYEvdnC.js

container_LFYEvdnC.js

1025 ms

matomo.js

matomo.js

802 ms

Logos%20FS%20noir%20Home_0.PNG

Logos%20FS%20noir%20Home_0.PNG

223 ms

close.svg

close.svg

214 ms

search.svg

search.svg

215 ms

lecture2.png

lecture2.png

213 ms

Image%20%2845%29.jpeg

Image%20%2845%29.jpeg

814 ms

pxiEyp8kv8JHgFVrFJPUdVNF.woff

pxiEyp8kv8JHgFVrFJPUdVNF.woff

258 ms

pxiByp8kv8JHgFVrLGT9V1hvEv-L.woff

pxiByp8kv8JHgFVrLGT9V1hvEv-L.woff

392 ms

pxiByp8kv8JHgFVrLDz8V1hvEv-L.woff

pxiByp8kv8JHgFVrLDz8V1hvEv-L.woff

465 ms

pxiByp8kv8JHgFVrLFj_V1hvEv-L.woff

pxiByp8kv8JHgFVrLFj_V1hvEv-L.woff

466 ms

pxiGyp8kv8JHgFVrLPTedHFHGPc.woff

pxiGyp8kv8JHgFVrLPTedHFHGPc.woff

462 ms

pxiByp8kv8JHgFVrLEj6V1hvEv-L.woff

pxiByp8kv8JHgFVrLEj6V1hvEv-L.woff

461 ms

pxiByp8kv8JHgFVrLCz7V1hvEv-L.woff

pxiByp8kv8JHgFVrLCz7V1hvEv-L.woff

462 ms

pxiByp8kv8JHgFVrLDD4V1hvEv-L.woff

pxiByp8kv8JHgFVrLDD4V1hvEv-L.woff

463 ms

pxiByp8kv8JHgFVrLBT5V1hvEv-L.woff

pxiByp8kv8JHgFVrLBT5V1hvEv-L.woff

518 ms

sdk.js

sdk.js

109 ms

js_sHLtq76yzkwiZjifbgjdKlEgUTH7Sn4kV2aELjdNUcQ.js

js_sHLtq76yzkwiZjifbgjdKlEgUTH7Sn4kV2aELjdNUcQ.js

199 ms

page.js

page.js

326 ms

js_WYrsBp1LLbodoIxcgIbG9kZRWC5fh-ix0eQ-9ELIisE.js

js_WYrsBp1LLbodoIxcgIbG9kZRWC5fh-ix0eQ-9ELIisE.js

206 ms

widgets.js

widgets.js

542 ms

js_iqbZf74M4sgmcTAkNxLrm0NAXQMEjPNfUjRnhK3ZfYg.js

js_iqbZf74M4sgmcTAkNxLrm0NAXQMEjPNfUjRnhK3ZfYg.js

196 ms

mail-francesoir.png

mail-francesoir.png

197 ms

Youtube-ICO.png

Youtube-ICO.png

203 ms

mail-francesoir_0.png

mail-francesoir_0.png

325 ms

Shopping-Cart-32px.png

Shopping-Cart-32px.png

326 ms

Logo%20FS%20blanc%20fond%20transparent%20-%20footer.PNG

Logo%20FS%20blanc%20fond%20transparent%20-%20footer.PNG

326 ms

271 ms

embed.js

embed.js

338 ms

matomo.php

matomo.php

384 ms

matomo.php

matomo.php

119 ms

tarteaucitron.min.css

tarteaucitron.min.css

411 ms

tarteaucitron.en.min.js

tarteaucitron.en.min.js

453 ms

matomo.php

matomo.php

96 ms

tarteaucitron.services.min.js

tarteaucitron.services.min.js

163 ms

Accessibility Review

francesoir.fr accessibility score

81

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

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.

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 IDs are not unique

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

francesoir.fr best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

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

francesoir.fr SEO score

93

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

francesoir.fr

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