Report Summary

  • 75

    Performance

    Renders faster than
    83% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

l3fr.org

Forum - Lorraine 3 Frontières L3FR

Page Load Speed

3 sec in total

First Response

248 ms

Resources Loaded

2.3 sec

Page Rendered

404 ms

l3fr.org screenshot

About Website

Visit l3fr.org now to see the best up-to-date L3FR content and also check out these interesting facts you probably never knew about l3fr.org

Généalogie

Visit l3fr.org

Key Findings

We analyzed L3fr.org page load time and found that the first response time was 248 ms and then it took 2.7 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

l3fr.org performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value2.4 s

99/100

10%

Network Requests Diagram

l3fr.org

248 ms

forum.php

289 ms

e107.js

236 ms

sleight_js.php

243 ms

style.css

247 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that all of those requests were addressed to L3fr.org and no external sources were called. The less responsive or slowest element that took the longest time to load (902 ms) belongs to the original domain L3fr.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 127.0 kB (28%)

Content Size

457.5 kB

After Optimization

330.5 kB

In fact, the total size of L3fr.org main page is 457.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 366.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 38.7 kB

  • Original 48.0 kB
  • After minification 47.5 kB
  • After compression 9.2 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 38.7 kB or 81% of the original size.

Image Optimization

-15%

Potential reduce by 53.2 kB

  • Original 366.8 kB
  • After minification 313.6 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, L3FR needs image optimization as it can save up to 53.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-82%

Potential reduce by 24.3 kB

  • Original 29.6 kB
  • After minification 16.8 kB
  • After compression 5.2 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 24.3 kB or 82% of the original size.

CSS Optimization

-81%

Potential reduce by 10.8 kB

  • Original 13.2 kB
  • After minification 10.2 kB
  • After compression 2.5 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. L3fr.org needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (57%)

Requests Now

72

After Optimization

31

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

Accessibility Review

l3fr.org accessibility score

55

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

l3fr.org best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

l3fr.org SEO score

58

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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