Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 0

    SEO

usages.openedition.org

Statistiques d'usages d'OpenEdition

Page Load Speed

11.8 sec in total

First Response

596 ms

Resources Loaded

4.2 sec

Page Rendered

7.1 sec

usages.openedition.org screenshot

About Website

Welcome to usages.openedition.org homepage info - get ready to check Usages Open Edition best content for France right away, or after learning these important things about usages.openedition.org

Statistiques d'usages d'OpenEdition

Visit usages.openedition.org

Key Findings

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

Performance Metrics

usages.openedition.org performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value1,710 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

usages.openedition.org

596 ms

jquery.js

3062 ms

fonctions.js

3378 ms

awstats.css

200 ms

en.png

271 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 17% of them (2 requests) were addressed to the original Usages.openedition.org, 83% (10 requests) were made to Logs.openedition.org. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Logs.openedition.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 945.5 kB (92%)

Content Size

1.0 MB

After Optimization

86.9 kB

In fact, the total size of Usages.openedition.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. 20% of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 938.4 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 81.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. 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 938.4 kB or 92% of the original size.

Image Optimization

-14%

Potential reduce by 562 B

  • Original 3.9 kB
  • After minification 3.3 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, Usages Open Edition needs image optimization as it can save up to 562 B or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-76%

Potential reduce by 6.5 kB

  • Original 8.6 kB
  • After minification 7.2 kB
  • After compression 2.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. Usages.openedition.org needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

9

After Optimization

2

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

Accessibility Review

usages.openedition.org accessibility score

74

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

Image elements do not have [alt] attributes

Best Practices

usages.openedition.org best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

usages.openedition.org SEO score

0

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 Usages.openedition.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 Usages.openedition.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 Usages Open Edition. 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: