Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

alptis.org

Alptis : complémentaire santé, assurance de prêt et prévoyance

Page Load Speed

2.8 sec in total

First Response

213 ms

Resources Loaded

2.2 sec

Page Rendered

378 ms

alptis.org screenshot

About Website

Welcome to alptis.org homepage info - get ready to check Alptis best content for France right away, or after learning these important things about alptis.org

Devis en ligne : complémentaire santé, prévoyance, assurance de prêt. Particulier, travailleur indépendant et frontalier, retraité et entreprise, Alptis protège près d’un demi-million de personnes.

Visit alptis.org

Key Findings

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

alptis.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

alptis.org

213 ms

www.alptis.org

613 ms

wp-emoji-release.min.js

148 ms

css

33 ms

9ccf2ae.css

410 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 64% of them (32 requests) were addressed to the original Alptis.org, 8% (4 requests) were made to Googletagmanager.com and 8% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (770 ms) relates to the external source Matomo.alptis.org.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

1.2 MB

In fact, the total size of Alptis.org main page is 1.4 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. Images take 588.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 86.2 kB

  • Original 106.2 kB
  • After minification 80.7 kB
  • After compression 20.0 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 25.6 kB, which is 24% 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 86.2 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 18.2 kB

  • Original 588.1 kB
  • After minification 569.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. Alptis images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 46.0 kB

  • Original 559.0 kB
  • After minification 559.0 kB
  • After compression 512.9 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

-4%

Potential reduce by 3.7 kB

  • Original 104.2 kB
  • After minification 104.2 kB
  • After compression 100.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. Alptis.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (37%)

Requests Now

46

After Optimization

29

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

Accessibility Review

alptis.org accessibility score

88

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.

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

Links do not have a discernible name

Best Practices

alptis.org 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

alptis.org SEO score

86

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

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 Alptis.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 Alptis.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 Alptis. 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: