Tools & Wizards About Us
vosges.fr screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

vosges.fr

Vosges.fr le site officiel du Conseil départemental

Page Load Speed

7 sec in total

First Response

254 ms

Resources Loaded

6 sec

Page Rendered

802 ms

vosges.fr screenshot

About Website

Welcome to vosges.fr homepage info - get ready to check Vosges best content for France right away, or after learning these important things about vosges.fr

Présentation des activités du conseil départemental des Vosges et de son actualité. Toutes les informations politique, touristiques, économiques et culturelles du Dép...

Visit vosges.fr

Key Findings

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

Performance Metrics

vosges.fr performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.92

3/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

vosges.fr

254 ms

www.vosges.fr

236 ms

www.vosges.fr

1532 ms

default.css

574 ms

SearchSkinObjectPreview.css

391 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 88% of them (106 requests) were addressed to the original Vosges.fr, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Tarteaucitron.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (31%)

Content Size

8.1 MB

After Optimization

5.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vosges.fr main page is 8.1 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. 80% 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 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 240.1 kB

  • Original 386.0 kB
  • After minification 320.6 kB
  • After compression 145.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. This page needs HTML code to be minified as it can gain 65.4 kB, which is 17% 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 240.1 kB or 62% of the original size.

Image Optimization

-5%

Potential reduce by 241.8 kB

  • Original 5.2 MB
  • After minification 5.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. Vosges images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 1.3 MB

  • Original 1.6 MB
  • After minification 1.3 MB
  • After compression 367.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.3 MB or 77% of the original size.

CSS Optimization

-87%

Potential reduce by 773.8 kB

  • Original 891.3 kB
  • After minification 742.8 kB
  • After compression 117.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. Vosges.fr needs all CSS files to be minified and compressed as it can save up to 773.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (51%)

Requests Now

114

After Optimization

56

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vosges.fr

vosges.fr

254 ms

www.vosges.fr

www.vosges.fr

236 ms

www.vosges.fr

www.vosges.fr

1532 ms

default.css

default.css

574 ms

SearchSkinObjectPreview.css

SearchSkinObjectPreview.css

391 ms

skin.css

skin.css

775 ms

HomePage7.css

HomePage7.css

508 ms

container.css

container.css

420 ms

container.css

container.css

456 ms

container.css

container.css

525 ms

container.css

container.css

543 ms

portal.css

portal.css

554 ms

Style.css

Style.css

623 ms

Style.css

Style.css

715 ms

Style.css

Style.css

665 ms

Style.css

Style.css

650 ms

font-icon.css

font-icon.css

687 ms

lightbox.css

lightbox.css

718 ms

images.css

images.css

764 ms

jquery.js

jquery.js

1060 ms

jquery-migrate.js

jquery-migrate.js

800 ms

css

css

36 ms

css

css

56 ms

jquery.mmenu.css

jquery.mmenu.css

808 ms

WebResource.axd

WebResource.axd

558 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

656 ms

dnn.js

dnn.js

604 ms

jquery.tmpl.min.js

jquery.tmpl.min.js

630 ms

jquery.validationEngine-fr.js

jquery.validationEngine-fr.js

639 ms

jquery.validationEngine.js

jquery.validationEngine.js

745 ms

jquery.timers.js

jquery.timers.js

720 ms

jquery.GalleryPostService.js

jquery.GalleryPostService.js

720 ms

jquery.easing.js

jquery.easing.js

755 ms

lightbox.js

lightbox.js

764 ms

jssor.js

jssor.js

840 ms

jssor.player.ytiframe.min.js

jssor.player.ytiframe.min.js

838 ms

jssor.slider.js

jssor.slider.js

932 ms

jssor.transitions.js

jssor.transitions.js

944 ms

slick.min.js

slick.min.js

882 ms

dnncore.js

dnncore.js

892 ms

js

js

45 ms

load.js

load.js

3672 ms

SearchSkinObjectPreview.js

SearchSkinObjectPreview.js

839 ms

dnn.analytics.Injected.js

dnn.analytics.Injected.js

818 ms

dnn.servicesframework.js

dnn.servicesframework.js

831 ms

script.js

script.js

909 ms

custom.js

custom.js

782 ms

dnngo-xplugin.js

dnngo-xplugin.js

786 ms

bootstrap.css

bootstrap.css

647 ms

shortcodes.css

shortcodes.css

540 ms

gtm.js

gtm.js

136 ms

ga.js

ga.js

66 ms

Vosges.png

Vosges.png

134 ms

Vosgesfr.png

Vosgesfr.png

135 ms

assembl%C3%A9e2023.jpg

assembl%C3%A9e2023.jpg

409 ms

AgrilocalSIA.jpg

AgrilocalSIA.jpg

227 ms

jeunesse5.jpg

jeunesse5.jpg

226 ms

vernissage.jpg

vernissage.jpg

135 ms

IMG_2279.JPG

IMG_2279.JPG

331 ms

CD88-ActionsJeunes.jpg

CD88-ActionsJeunes.jpg

286 ms

Jeune.jpg

Jeune.jpg

283 ms

Famille.jpg

Famille.jpg

284 ms

senior.jpg

senior.jpg

286 ms

insertion.jpg

insertion.jpg

406 ms

Handicap_1.jpg

Handicap_1.jpg

405 ms

HabitatLogement.jpg

HabitatLogement.jpg

407 ms

Economie.jpg

Economie.jpg

411 ms

TransitionEcologique.jpg

TransitionEcologique.jpg

411 ms

culture.jpg

culture.jpg

484 ms

sport.jpg

sport.jpg

481 ms

Territoire.jpg

Territoire.jpg

479 ms

GuichetCitoyen.jpg

GuichetCitoyen.jpg

482 ms

Pink.png

Pink.png

527 ms

DarkBlue.png

DarkBlue.png

522 ms

Orange.png

Orange.png

601 ms

Blue.png

Blue.png

592 ms

Red.png

Red.png

596 ms

TerritorialCharmes.JPG

TerritorialCharmes.JPG

601 ms

SaintDi%C3%A91.JPG

SaintDi%C3%A91.JPG

638 ms

Darneyvisuel16x9.jpg

Darneyvisuel16x9.jpg

653 ms

tourdefrance.jpg

tourdefrance.jpg

711 ms

Raonletapevisuel.JPG

Raonletapevisuel.JPG

716 ms

Mirecourt2.jpg

Mirecourt2.jpg

715 ms

W-Tourisme.png

W-Tourisme.png

702 ms

W-Sortir.png

W-Sortir.png

735 ms

W-J3V.png

W-J3V.png

756 ms

W-Inforoute.png

W-Inforoute.png

799 ms

logo-foret_1.png

logo-foret_1.png

819 ms

fbevents.js

fbevents.js

73 ms

4iCs6KVjbNBYlgoKfw7z.ttf

4iCs6KVjbNBYlgoKfw7z.ttf

70 ms

__utm.gif

__utm.gif

50 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

736 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

705 ms

W-Bike.png

W-Bike.png

700 ms

W-CultureCNous.png

W-CultureCNous.png

644 ms

W-Archives.png

W-Archives.png

688 ms

W-MDV.png

W-MDV.png

647 ms

mudaac.png

mudaac.png

661 ms

W-Agrilocal.png

W-Agrilocal.png

648 ms

insight.min.js

insight.min.js

47 ms

matomo.js

matomo.js

640 ms

js

js

53 ms

monpanierlocal.png

monpanierlocal.png

610 ms

W-Labo.png

W-Labo.png

623 ms

insight_tag_errors.gif

insight_tag_errors.gif

140 ms

Approved.png

Approved.png

609 ms

LogoCD88.png

LogoCD88.png

624 ms

line-bg.png

line-bg.png

623 ms

loading.gif

loading.gif

640 ms

grab.png

grab.png

631 ms

b04.png

b04.png

654 ms

a22.png

a22.png

662 ms

loading.gif

loading.gif

666 ms

postsum.png

postsum.png

674 ms

ajax-loader.gif

ajax-loader.gif

655 ms

img_bg_18.jpg

img_bg_18.jpg

615 ms

img_bg_29.jpg

img_bg_29.jpg

643 ms

img_bg_7.jpg

img_bg_7.jpg

638 ms

matomo.php

matomo.php

492 ms

top_ico.png

top_ico.png

242 ms

Accessibility Review

vosges.fr accessibility score

61

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

SEO Factors

vosges.fr SEO score

81

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

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

vosges.fr

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