Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

vivea.fr

Accueil - VIVEA

Page Load Speed

3.9 sec in total

First Response

341 ms

Resources Loaded

2.8 sec

Page Rendered

787 ms

vivea.fr screenshot

About Website

Visit vivea.fr now to see the best up-to-date VIVEA content for France and also check out these interesting facts you probably never knew about vivea.fr

Découvrez VIVEA, fonds pour la formation des entrepreneurs du vivant, ses missions, les formations destinées aux chefs d’entreprise du secteur agricole pour développer leurs compétences, les financeme...

Visit vivea.fr

Key Findings

We analyzed Vivea.fr page load time and found that the first response time was 341 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

vivea.fr performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

vivea.fr

341 ms

vivea.fr

412 ms

all-04dd265761e9724ced2fb25565b91e8c.js

415 ms

style.min.css

240 ms

theme.min.css

238 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 72% of them (62 requests) were addressed to the original Vivea.fr, 22% (19 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (861 ms) belongs to the original domain Vivea.fr.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

1.6 MB

In fact, the total size of Vivea.fr main page is 1.7 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.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 184.1 kB

  • Original 218.9 kB
  • After minification 204.5 kB
  • After compression 34.9 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 184.1 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 42 (67%)

Requests Now

63

After Optimization

21

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

Accessibility Review

vivea.fr accessibility score

91

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Links do not have a discernible name

Best Practices

vivea.fr best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

vivea.fr SEO score

92

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 Vivea.fr 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 Vivea.fr 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 VIVEA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: