Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

aws-courrier.info

AWS-Achat, Profil d'acheteur du pouvoir adjudicateur , Dématérialisation des Marchés Publics, Solution de gestion des achats, AWS édite aussi AWS-Léga...

Page Load Speed

1.5 sec in total

First Response

253 ms

Resources Loaded

1.1 sec

Page Rendered

165 ms

aws-courrier.info screenshot

About Website

Welcome to aws-courrier.info homepage info - get ready to check AWS Courrier best content for France right away, or after learning these important things about aws-courrier.info

Visit aws-courrier.info

Key Findings

We analyzed Aws-courrier.info page load time and found that the first response time was 253 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

aws-courrier.info performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.204

61/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

aws-courrier.info

253 ms

accueil.htm

83 ms

signature.css

80 ms

menu.css

158 ms

haut.jpg

157 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 98.9 kB (57%)

Content Size

173.2 kB

After Optimization

74.3 kB

In fact, the total size of Aws-courrier.info main page is 173.2 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. Only 10% of websites need less resources to load. Images take 153.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 3.6 kB

  • Original 5.2 kB
  • After minification 3.9 kB
  • After compression 1.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 1.3 kB, which is 25% 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 3.6 kB or 70% of the original size.

Image Optimization

-54%

Potential reduce by 82.5 kB

  • Original 153.3 kB
  • After minification 70.9 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, AWS Courrier needs image optimization as it can save up to 82.5 kB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-87%

Potential reduce by 12.9 kB

  • Original 14.7 kB
  • After minification 6.9 kB
  • After compression 1.9 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. Aws-courrier.info needs all CSS files to be minified and compressed as it can save up to 12.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (43%)

Requests Now

21

After Optimization

12

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AWS Courrier. 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

aws-courrier.info accessibility score

95

Accessibility Issues

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

Best Practices

aws-courrier.info 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aws-courrier.info SEO score

69

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aws-courrier.info 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 Aws-courrier.info main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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