10 sec in total
439 ms
9.4 sec
203 ms
Click here to check amazing CA Frontalier content. Otherwise, check out these important facts you probably never knew about ca-frontalier.com
Bienvenue sur la plateforme dédiée aux frontaliers franco-suisses avec toutes les informations pratiques, les bonnes idées et les actualités de la vie frontalière.
Visit ca-frontalier.comWe analyzed Ca-frontalier.com page load time and found that the first response time was 439 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ca-frontalier.com performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value7.5 s
4/100
25%
Value10.9 s
6/100
10%
Value1,750 ms
10/100
30%
Value0.356
31/100
15%
Value20.0 s
2/100
10%
439 ms
699 ms
277 ms
540 ms
157 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ca-frontalier.com, 80% (96 requests) were made to Ca-des-savoie.fr and 3% (4 requests) were made to Libs.de.coremetrics.com. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Data.de.coremetrics.com.
Page size can be reduced by 854.8 kB (36%)
2.4 MB
1.5 MB
In fact, the total size of Ca-frontalier.com main page is 2.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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 67.7 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 14.7 kB, which is 18% 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 67.7 kB or 81% of the original size.
Potential reduce by 37.5 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. CA Frontalier images are well optimized though.
Potential reduce by 456.3 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 456.3 kB or 74% of the original size.
Potential reduce by 293.3 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. Ca-frontalier.com needs all CSS files to be minified and compressed as it can save up to 293.3 kB or 87% of the original size.
Number of requests can be reduced by 76 (67%)
113
37
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CA 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 36 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
ca-frontalier.com
439 ms
www.ca-frontaliers-suisse.com
699 ms
ca-frontaliers-suisse.html
277 ms
ca-frontaliers-suisse.html
540 ms
eluminate.js
157 ms
referrer.js
193 ms
global.css
268 ms
produit.css
285 ms
EngagementRelationnel.css
285 ms
jquery.min.js
383 ms
jquery.pngFix.pack.js
299 ms
ap_full.js
298 ms
commun.js
353 ms
utils.js
377 ms
monitor.js
378 ms
tools.js
395 ms
recherche.js
395 ms
browser.js
440 ms
xiti.js
469 ms
xtplugF.js
470 ms
jquery-ui.min.js
571 ms
bamv3.js
489 ms
indFinancier.js
404 ms
header.js
500 ms
convertissor.js
474 ms
during-exchange.js
474 ms
simulator.js
519 ms
common.css
520 ms
style.css
576 ms
home.css
567 ms
dossiers_conseil.css
578 ms
actualites.css
585 ms
carrousel.css
612 ms
onglets.css
614 ms
jquery.min.js
81 ms
jquery-ui.min.js
121 ms
traitement.js
570 ms
modernizr.custom.js
657 ms
jquery.imagesloaded.min.js
666 ms
cbpBGSlideshow.min.js
670 ms
head.js
304 ms
50580000.js
153 ms
dispatcher-v3.js
81 ms
yahoo-min.js
29 ms
cp-v3.js
120 ms
json-min.js
28 ms
ecart-v1.css
267 ms
navComptes.css
303 ms
menu.css
304 ms
menu2.css
345 ms
accueil.css
355 ms
page_vide.css
351 ms
page_libre.css
358 ms
liste.css
394 ms
dossiers.css
399 ms
sommaire.css
434 ms
message.css
444 ms
syndication.css
452 ms
magazine.css
487 ms
simulateur.css
489 ms
mobilite.css
526 ms
espace.css
522 ms
tarifs.css
536 ms
reseauxsociaux.css
545 ms
bottom.css
581 ms
sondage_300x260.css
237 ms
logo_creditagricole.png
100 ms
english_flag_tcm_148_98602.gif
98 ms
sprite_blocs_color.png
1909 ms
sprite_pictos.png
1907 ms
160223-credit-auto-CHF-salon-de-geneve.jpg
2298 ms
ban-salon-transfrontaliers-2016.jpg
2773 ms
banniere-VAT-2016.jpg
2287 ms
actualite_visuel.jpg
1906 ms
simulateur_picto_assurance.png
1908 ms
simulateur_picto_epargne.png
1908 ms
simulateur_picto_credit.png
1909 ms
engagement_picto_conseiller.png
1910 ms
engagement_picto_prise_en_charge.png
1910 ms
engagement_picto_fidelite.png
1911 ms
engagement_picto_frontiere.png
1915 ms
sprite_btns.png
1906 ms
sprite_vertical.png
1902 ms
flch_bourse_up.gif
2009 ms
picto_warning-cookies-2.png
2004 ms
css
24 ms
webfont.js
14 ms
menu_fond.png
1938 ms
convertisseur_fond.jpg
2018 ms
convertisseur_input_fond.png
2028 ms
pixel.gif
2025 ms
bt_facebook.png
2097 ms
bt_twitter.png
2113 ms
picto_rappel.png
2120 ms
simulator_background.png
2184 ms
picto_fleche.png
2206 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
19 ms
cm
6255 ms
css
56 ms
vivocha.js
1817 ms
jquery.fancybox.css
2127 ms
jquery.fancybox-buttons.css
2187 ms
jquery.fancybox-thumbs.css
2192 ms
taux-display.php
248 ms
logo.png
501 ms
bt_navigation.png
501 ms
bt_agence.png
515 ms
bt_telephone.png
566 ms
bt_formulaire.png
579 ms
bt_sos.png
586 ms
bt_client.png
587 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
33 ms
bt_parrainage.png
607 ms
vivocha.js
407 ms
cours_evolution_augmentation.png
414 ms
fetch.js
59 ms
77 ms
vivocha_data.js
11 ms
print.css
99 ms
bt_navigation_selected.png
101 ms
ca-frontalier.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ca-frontalier.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ca-frontalier.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
Document uses legible font sizes
FR
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ca-frontalier.com 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 Ca-frontalier.com main page’s claimed encoding is . 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.
ca-frontalier.com
Open Graph description is not detected on the main page of CA 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: