Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

auvergne.org

La marque Auvergne - Marque Auvergne

Page Load Speed

8.2 sec in total

First Response

813 ms

Resources Loaded

6.5 sec

Page Rendered

851 ms

auvergne.org screenshot

About Website

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

L'association marque Auvergne fédère des adhérents auvergnats qui s'engagent pour l'Auvergne et ses 4 départements.

Visit auvergne.org

Key Findings

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

Performance Metrics

auvergne.org performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

www.auvergne.org

813 ms

css

43 ms

js

87 ms

smls-frontend-style-1.1.8.css

236 ms

smls-block-1.1.8.css

256 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 82% of them (98 requests) were addressed to the original Auvergne.org, 8% (9 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Auvergne.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.1 kB (11%)

Content Size

1.2 MB

After Optimization

1.1 MB

In fact, the total size of Auvergne.org main page is 1.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 135.4 kB

  • Original 161.5 kB
  • After minification 156.1 kB
  • After compression 26.1 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 135.4 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 643 B

  • Original 1.0 MB
  • After minification 1.0 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. Auvergne images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 63 B

  • Original 34.6 kB
  • After minification 34.6 kB
  • After compression 34.5 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.

Requests Breakdown

Number of requests can be reduced by 83 (79%)

Requests Now

105

After Optimization

22

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

Accessibility Review

auvergne.org accessibility score

82

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

auvergne.org SEO score

89

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

High

Tap targets are not sized appropriately

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 Auvergne.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 Auvergne.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 data is detected on the main page of Auvergne. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: