Tools & Wizards About Us
frontalier.org screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

frontalier.org

Groupement transfrontalier européen - Accueil - GTE

Page Load Speed

7.4 sec in total

First Response

1.2 sec

Resources Loaded

6 sec

Page Rendered

266 ms

frontalier.org screenshot

About Website

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

Vivant en France et travaillant en Suisse, le travailleur frontalier se trouve confronté à deux législations différentes. Le site du Groupement transfrontalier européen vous aide à faire le point et v...

Visit frontalier.org

Key Findings

We analyzed Frontalier.org page load time and found that the first response time was 1.2 sec and then it took 6.2 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

frontalier.org performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

www.frontalier.org

1189 ms

defaut.css

422 ms

menu-fr.css

225 ms

convertisseur.css

242 ms

jquery-1.7.1.min.js

627 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 98% of them (87 requests) were addressed to the original Frontalier.org, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Frontalier.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 579.7 kB (36%)

Content Size

1.6 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frontalier.org main page is 1.6 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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.1 kB

  • Original 32.2 kB
  • After minification 28.7 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 3.5 kB, which is 11% 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 24.1 kB or 75% of the original size.

Image Optimization

-21%

Potential reduce by 241.4 kB

  • Original 1.2 MB
  • After minification 934.3 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, Frontalier needs image optimization as it can save up to 241.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 233.7 kB

  • Original 323.2 kB
  • After minification 267.7 kB
  • After compression 89.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 233.7 kB or 72% of the original size.

CSS Optimization

-87%

Potential reduce by 80.6 kB

  • Original 92.5 kB
  • After minification 66.3 kB
  • After compression 11.8 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. Frontalier.org needs all CSS files to be minified and compressed as it can save up to 80.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (22%)

Requests Now

88

After Optimization

69

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.frontalier.org

www.frontalier.org

1189 ms

defaut.css

defaut.css

422 ms

menu-fr.css

menu-fr.css

225 ms

convertisseur.css

convertisseur.css

242 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

627 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

379 ms

nivo-slider.css

nivo-slider.css

318 ms

prototype.js

prototype.js

1003 ms

cookiechoicesbottom.js

cookiechoicesbottom.js

357 ms

lightview.css

lightview.css

116 ms

rdv.css

rdv.css

202 ms

ga.js

ga.js

30 ms

fondHTML.png

fondHTML.png

629 ms

logo.gif

logo.gif

208 ms

b_close.png

b_close.png

189 ms

connexionok.gif

connexionok.gif

241 ms

facebook.jpg

facebook.jpg

229 ms

twitter.jpg

twitter.jpg

385 ms

linkedin.jpg

linkedin.jpg

442 ms

google+.jpg

google+.jpg

442 ms

rss.jpg

rss.jpg

448 ms

home.jpg

home.jpg

561 ms

i-phone-petit.png

i-phone-petit.png

583 ms

i-pad-petit.png

i-pad-petit.png

624 ms

android-petit.png

android-petit.png

647 ms

135.gif

135.gif

1050 ms

141.jpg

141.jpg

1076 ms

14.gif

14.gif

963 ms

530.jpg

530.jpg

1095 ms

534.jpg

534.jpg

1084 ms

528.jpg

528.jpg

962 ms

537.jpg

537.jpg

1257 ms

504.jpg

504.jpg

1373 ms

520.jpg

520.jpg

1428 ms

535.jpg

535.jpg

1465 ms

news-head.jpg

news-head.jpg

1292 ms

1120276-1.jpg

1120276-1.jpg

1413 ms

1120270-1.jpg

1120270-1.jpg

1582 ms

1120263-1.jpg

1120263-1.jpg

1573 ms

1120253-1.jpg

1120253-1.jpg

1785 ms

azur.jpg

azur.jpg

1746 ms

__utm.gif

__utm.gif

12 ms

inscription-form.htm

inscription-form.htm

1315 ms

mon-espaces.jpg

mon-espaces.jpg

1301 ms

mon-box.jpg

mon-box.jpg

1408 ms

search.png

search.png

1403 ms

hautspacer.jpg

hautspacer.jpg

1479 ms

espace-menu.jpg

espace-menu.jpg

1521 ms

menu-top.jpg

menu-top.jpg

1684 ms

spanTop.png

spanTop.png

1581 ms

sousBox.png

sousBox.png

1582 ms

contenu.png

contenu.png

1601 ms

fond-droit.jpg

fond-droit.jpg

1665 ms

convertor.jpg

convertor.jpg

1688 ms

no7petit.png

no7petit.png

1720 ms

no8petit.png

no8petit.png

1724 ms

no9petit.png

no9petit.png

1771 ms

no4petit.png

no4petit.png

1690 ms

no5petit.png

no5petit.png

1683 ms

no6petit.png

no6petit.png

1665 ms

no1petit.png

no1petit.png

1722 ms

no2petit.png

no2petit.png

1707 ms

no3petit.png

no3petit.png

1443 ms

no0petit.png

no0petit.png

1500 ms

virgule-petit.png

virgule-petit.png

1404 ms

noCpetit.png

noCpetit.png

1401 ms

chf-bleue-petit.png

chf-bleue-petit.png

1450 ms

chf-rouge-petit.png

chf-rouge-petit.png

1458 ms

telechargezIpod.jpg

telechargezIpod.jpg

1489 ms

loading.gif

loading.gif

1581 ms

news-box.jpg

news-box.jpg

1286 ms

photoBorder.png

photoBorder.png

1460 ms

savoir-rouge.jpg

savoir-rouge.jpg

1444 ms

archives-news.jpg

archives-news.jpg

1425 ms

acces-head.jpg

acces-head.jpg

1294 ms

menuDossiers.jpg

menuDossiers.jpg

1365 ms

menuEmploi.jpg

menuEmploi.jpg

1381 ms

menuVideo.jpg

menuVideo.jpg

1366 ms

menuClub.jpg

menuClub.jpg

1323 ms

menuPublications.jpg

menuPublications.jpg

1294 ms

head-offre.jpg

head-offre.jpg

1294 ms

middle-offre.jpg

middle-offre.jpg

1344 ms

bottom-offre.jpg

bottom-offre.jpg

1390 ms

footer.jpg

footer.jpg

1351 ms

INSCRIPTION.jpg

INSCRIPTION.jpg

1542 ms

captation.png

captation.png

103 ms

captation-title.png

captation-title.png

102 ms

arrows.png

arrows.png

190 ms

bullets.png

bullets.png

192 ms

Accessibility Review

frontalier.org accessibility score

90

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

<frame> or <iframe> elements do not have a title

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.

Best Practices

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

Page has valid source maps

SEO Factors

frontalier.org SEO score

91

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frontalier.org can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Frontalier.org 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

frontalier.org

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