21.1 sec in total
2.1 sec
8 sec
11.1 sec
Welcome to capcours.com homepage info - get ready to check Capcours best content right away, or after learning these important things about capcours.com
Formation professionnelle cpf et plan CAPCOURS : Formation en langues, informatique digital, management...
Visit capcours.comWe analyzed Capcours.com page load time and found that the first response time was 2.1 sec and then it took 19.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
capcours.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value8.7 s
1/100
25%
Value9.9 s
10/100
10%
Value2,690 ms
4/100
30%
Value0.004
100/100
15%
Value15.4 s
7/100
10%
2057 ms
602 ms
495 ms
214 ms
89 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Capcours.com, 26% (31 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Societe-des-avis-garantis.fr. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Capcours-abdformations.com.
Page size can be reduced by 244.4 kB (45%)
541.2 kB
296.9 kB
In fact, the total size of Capcours.com main page is 541.2 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 282.0 kB which makes up the majority of the site volume.
Potential reduce by 237.4 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 237.4 kB or 84% of the original size.
Potential reduce by 6.0 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. Capcours images are well optimized though.
Potential reduce by 939 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 60 (71%)
85
25
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capcours. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
capcours-abdformations.com
2057 ms
frontend-lite.min.css
602 ms
post-1947.css
495 ms
frontend.css
214 ms
css
89 ms
frontend-lite.min.css
555 ms
global.css
489 ms
style.min.css
556 ms
all.min.css
591 ms
simple-line-icons.min.css
805 ms
post-109.css
813 ms
post-8.css
881 ms
ekiticons.css
935 ms
widget-styles.css
1038 ms
responsive.css
897 ms
gdpr-main.css
1234 ms
widgets.css
1203 ms
jquery.min.js
1304 ms
jquery-migrate.min.js
1216 ms
js
104 ms
widget-icon-list.min.css
1209 ms
JsWidget.js
585 ms
widget-theme-elements.min.css
1462 ms
widget-icon-box.min.css
1203 ms
post-1956.css
1576 ms
post-2023.css
1578 ms
animations.min.css
1576 ms
imagesloaded.min.js
1578 ms
theme.min.js
1582 ms
drop-down-mobile-menu.min.js
1580 ms
magnific-popup.min.js
1578 ms
ow-lightbox.min.js
1991 ms
flickity.pkgd.min.js
1578 ms
ow-slider.min.js
1991 ms
scroll-effect.min.js
1991 ms
scroll-top.min.js
1994 ms
select.min.js
1994 ms
frontend-script.js
1995 ms
widget-scripts.js
2932 ms
main.js
2930 ms
webpack-pro.runtime.min.js
2341 ms
webpack.runtime.min.js
2065 ms
frontend-modules.min.js
2573 ms
regenerator-runtime.min.js
2493 ms
wp-polyfill.min.js
2479 ms
hooks.min.js
2438 ms
i18n.min.js
2949 ms
frontend.min.js
3093 ms
waypoints.min.js
2770 ms
core.min.js
2406 ms
frontend.min.js
3009 ms
elements-handlers.min.js
2953 ms
animate-circle.js
2822 ms
elementor.js
2698 ms
swiper.min.js
2678 ms
jquery.sticky.min.js
2650 ms
lazyload.min.js
2649 ms
gtm.js
196 ms
photo_centre.jpg
2747 ms
analytics.js
381 ms
js
382 ms
loader.js
382 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
548 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
1127 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
1125 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
1126 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
1325 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
1335 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
1335 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
1325 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
1332 ms
elementskit.woff
2205 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
1326 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
1328 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
1335 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
1350 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
1339 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
1342 ms
L0xoDF4xlVMF-BfR8bXMIjhOsXG-q2oeuFoqFrlnANW6Cpw.ttf
1351 ms
L0xoDF4xlVMF-BfR8bXMIjhOsXG-q2oeuFoqFrlVANW6Cpw.ttf
1362 ms
L0xoDF4xlVMF-BfR8bXMIjhOsXG-q2oeuFoqFrk5ANW6Cpw.ttf
1373 ms
L0xoDF4xlVMF-BfR8bXMIjhOsXG-q2oeuFoqFrnnANW6Cpw.ttf
1401 ms
L0xoDF4xlVMF-BfR8bXMIjhOsXG-q2oeuFoqFrlnAdW6Cpw.ttf
1390 ms
L0xoDF4xlVMF-BfR8bXMIjhOsXG-q2oeuFoqFrm5B9W6Cpw.ttf
1400 ms
L0xoDF4xlVMF-BfR8bXMIjhOsXG-q2oeuFoqFrmAB9W6Cpw.ttf
1352 ms
L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vq_ROW9.ttf
1364 ms
L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_7Pq_ROW9.ttf
1372 ms
L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_gPq_ROW9.ttf
1377 ms
L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_Xvq_ROW9.ttf
1380 ms
L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vu_ROW9.ttf
1391 ms
L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_AP2_ROW9.ttf
1383 ms
L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_Of2_ROW9.ttf
1384 ms
collect
1078 ms
call-tracking_7.js
362 ms
collect
644 ms
logo2022-CapcoursFP-RVBpetit-300x76.jpg
791 ms
logo-qualiopi-minmin-min-300x95.jpg
717 ms
logo-qualiopi-minmin-min.jpg
718 ms
telechargement-valide-datadock.png
716 ms
telechargement.png
712 ms
telechargement-4.png
791 ms
telechargement-3-300x72.png
792 ms
telechargement-2.png
838 ms
telechargement-1-300x86.png
840 ms
Logo_Groupe_ADP.svg-300x254.webp
839 ms
daimler-2-300x199.jpg
791 ms
Celio-1-min.png
929 ms
Castorama-1-min-1.jpg
788 ms
Burberry-1-min.jpg
926 ms
Air-france-3-min.jpg
788 ms
gdpr-logo.png
831 ms
ga-audiences
702 ms
7082.html
332 ms
wcm
660 ms
css
282 ms
classic.png
237 ms
guard_stars.png
243 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
3 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
88 ms
capcours.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
capcours.com 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
capcours.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capcours.com 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 Capcours.com 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.
capcours.com
Open Graph data is detected on the main page of Capcours. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: