10.2 sec in total
428 ms
8.6 sec
1.2 sec
Visit geth38.fr now to see the best up-to-date GETH 38 content and also check out these interesting facts you probably never knew about geth38.fr
Groupement d'employeurs en Isère et Rhône, le GETH apporte des solutions d'emploi aux personnes en situation de handicap.
Visit geth38.frWe analyzed Geth38.fr page load time and found that the first response time was 428 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
geth38.fr performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value22.4 s
0/100
25%
Value35.5 s
0/100
10%
Value40,240 ms
0/100
30%
Value0.813
4/100
15%
Value52.8 s
0/100
10%
428 ms
687 ms
292 ms
423 ms
31 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Geth38.fr, 42% (40 requests) were made to Geth.fr and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.7 sec) relates to the external source Geth.fr.
Page size can be reduced by 634.0 kB (71%)
893.0 kB
259.0 kB
In fact, the total size of Geth38.fr main page is 893.0 kB. 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. HTML takes 642.7 kB which makes up the majority of the site volume.
Potential reduce by 581.3 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 581.3 kB or 90% of the original size.
Potential reduce by 23.4 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, GETH 38 needs image optimization as it can save up to 23.4 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 17.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 17.3 kB or 16% of the original size.
Potential reduce by 11.9 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. Geth38.fr needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 24% of the original size.
Number of requests can be reduced by 35 (92%)
38
3
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GETH 38. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
geth.fr
428 ms
geth.fr
687 ms
cookieblocker.min.css
292 ms
style.css
423 ms
css
31 ms
wpforms-full.min.css
319 ms
style.css
221 ms
cookies.js
300 ms
jquery.min.js
476 ms
jquery-migrate.min.js
334 ms
mediaelementplayer-legacy.min.css
284 ms
wp-mediaelement.min.css
289 ms
choices.min.css
372 ms
idle-timer.min.js
385 ms
custom.js
408 ms
scripts.min.js
733 ms
smoothscroll.js
400 ms
jquery.fitvids.js
721 ms
magnific-popup.js
723 ms
easypiechart.js
723 ms
salvattore.js
723 ms
common.js
723 ms
smush-lazy-load.min.js
725 ms
complianz.min.js
726 ms
mediaelement-and-player.min.js
821 ms
mediaelement-migrate.min.js
723 ms
wp-mediaelement.min.js
724 ms
sticky-elements.js
928 ms
choices.min.js
821 ms
jquery.validate.min.js
817 ms
mailcheck.min.js
818 ms
punycode.min.js
816 ms
utils.min.js
970 ms
wpforms.min.js
969 ms
api.js
35 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJm5wA.woff
203 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJm5ww.ttf
101 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpm5wA.woff
94 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpm5ww.ttf
121 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuSJm5wA.woff
90 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuSJm5ww.ttf
122 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulpm5wA.woff
261 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulpm5ww.ttf
124 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpi5wA.woff
197 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpi5ww.ttf
112 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ65wA.woff
109 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ65ww.ttf
116 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymu8Z65wA.woff
113 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymu8Z65ww.ttf
119 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulp65wA.woff
183 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulp65ww.ttf
119 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuv565wA.woff
186 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuv565ww.ttf
121 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ5-xQjM.woff
529 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ5-xQjA.ttf
180 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ62xQjM.woff
530 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ62xQjA.ttf
530 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ_OxQjM.woff
533 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ_OxQjA.ttf
531 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy2xQjM.woff
539 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy2xQjA.ttf
538 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ3O2QjM.woff
723 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ3O2QjA.ttf
529 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ0q2QjM.woff
548 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ0q2QjA.ttf
531 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy22QjM.woff
550 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy22QjA.ttf
548 ms
modules.ttf
531 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tpjgAcu.woff
539 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tpjgAct.ttf
538 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tpRgAcu.woff
742 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tpRgAct.ttf
539 ms
matomo.js
442 ms
monarch.ttf
161 ms
et-divi-dynamic-2978-late.css
186 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673toPgAcu.woff
660 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673toPgAct.ttf
650 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673trRgAcu.woff
647 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673trRgAct.ttf
450 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tpRgQcu.woff
625 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tpRgQct.ttf
620 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tqPhwcu.woff
636 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tqPhwct.ttf
618 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tq2hwcu.woff
616 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tq2hwct.ttf
615 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673trRhwcu.woff
626 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673trRhwct.ttf
614 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tr4hwcu.woff
677 ms
ijwAs572Xtc6ZYQws9YVwnNDZpDyNjGolS673tr4hwct.ttf
556 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
562 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
562 ms
style.min.css
208 ms
matomo.php
5666 ms
GETH-Logo-vertic-couldegrade.png
281 ms
recaptcha__en.js
561 ms
geth38.fr accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
geth38.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
geth38.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geth38.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 Geth38.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.
geth38.fr
Open Graph data is detected on the main page of GETH 38. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: