Tools & Wizards About Us
capitecorpus.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

capitecorpus.com

Capite Corpus, organisme de formations professionnelles

Page Load Speed

7.6 sec in total

First Response

295 ms

Resources Loaded

7 sec

Page Rendered

291 ms

capitecorpus.com screenshot

About Website

Click here to check amazing Capite Corpus content for Morocco. Otherwise, check out these important facts you probably never knew about capitecorpus.com

Des formations professionnelles centrées sur les compétences comportementales et relationnelles : management, relation client, communication.

Visit capitecorpus.com

Key Findings

We analyzed Capitecorpus.com page load time and found that the first response time was 295 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

capitecorpus.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.052

98/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

www.capitecorpus.com

295 ms

gtm.js

80 ms

webfont.js

40 ms

style.min.css

67 ms

cookieblocker.min.css

205 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 82% of them (54 requests) were addressed to the original Capitecorpus.com, 8% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (433 ms) belongs to the original domain Capitecorpus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 318.4 kB (75%)

Content Size

425.8 kB

After Optimization

107.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Capitecorpus.com main page is 425.8 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. 75% 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 364.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 317.8 kB

  • Original 364.5 kB
  • After minification 360.2 kB
  • After compression 46.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. 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 317.8 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 140 B

  • Original 50.1 kB
  • After minification 50.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. Capite Corpus images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 461 B

  • Original 11.2 kB
  • After minification 11.2 kB
  • After compression 10.7 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 36 (65%)

Requests Now

55

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.capitecorpus.com

www.capitecorpus.com

295 ms

gtm.js

gtm.js

80 ms

webfont.js

webfont.js

40 ms

style.min.css

style.min.css

67 ms

cookieblocker.min.css

cookieblocker.min.css

205 ms

style.css

style.css

119 ms

style.css

style.css

119 ms

flaticon.css

flaticon.css

141 ms

v4-shims.min.css

v4-shims.min.css

134 ms

all.min.css

all.min.css

136 ms

swipebox.min.css

swipebox.min.css

139 ms

main.css

main.css

163 ms

js_composer.min.css

js_composer.min.css

190 ms

jquery.min.js

jquery.min.js

186 ms

jquery-migrate.min.js

jquery-migrate.min.js

137 ms

script.js

script.js

136 ms

jquery.swipebox.min.js

jquery.swipebox.min.js

186 ms

5e87e8924a.js

5e87e8924a.js

104 ms

css

css

89 ms

font-awesome.css

font-awesome.css

172 ms

css

css

112 ms

rs6.css

rs6.css

306 ms

rbtools.min.js

rbtools.min.js

308 ms

rs6.min.js

rs6.min.js

309 ms

theme-addons.js

theme-addons.js

308 ms

theme.js

theme.js

306 ms

complianz.min.js

complianz.min.js

421 ms

js_composer_front.min.js

js_composer_front.min.js

308 ms

jquery.appear.js

jquery.appear.js

417 ms

slick.min.js

slick.min.js

420 ms

lazyload.min.js

lazyload.min.js

417 ms

css

css

102 ms

js

js

90 ms

dummy.png

dummy.png

120 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

109 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

109 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

110 ms

fa-brands-400.woff

fa-brands-400.woff

433 ms

Flaticon.svg

Flaticon.svg

216 ms

Flaticon.woff

Flaticon.woff

213 ms

fa-solid-900.woff

fa-solid-900.woff

215 ms

fa-regular-400.woff

fa-regular-400.woff

213 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

286 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff

170 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e4.woff

175 ms

logo_cc_baseline_crop_web.png

logo_cc_baseline_crop_web.png

190 ms

solimut_logo-4.png

solimut_logo-4.png

191 ms

ellisphere_logo-1.png

ellisphere_logo-1.png

192 ms

alixio_logo.png

alixio_logo.png

193 ms

logo_amex_gbt.png

logo_amex_gbt.png

190 ms

camille_albane_logo.png

camille_albane_logo.png

219 ms

cushman_logo.png

cushman_logo.png

221 ms

oreal_logo.png

oreal_logo.png

253 ms

trescal_logo.png

trescal_logo.png

249 ms

Sodiaal_logo.png

Sodiaal_logo.png

277 ms

ista_logo.png

ista_logo.png

278 ms

dessange_logo.png

dessange_logo.png

324 ms

alliade_logo.png

alliade_logo.png

372 ms

afpa_logo.png

afpa_logo.png

342 ms

rockwool_logo.png

rockwool_logo.png

357 ms

cpam_logo.png

cpam_logo.png

367 ms

logo_blanc-capite-corpus.png

logo_blanc-capite-corpus.png

377 ms

icon_tools.png

icon_tools.png

329 ms

icon_flask.png

icon_flask.png

324 ms

icon_plant.png

icon_plant.png

353 ms

icon_search.png

icon_search.png

348 ms

Accessibility Review

capitecorpus.com accessibility score

83

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

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

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

capitecorpus.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

capitecorpus.com SEO score

100

Search Engine Optimization Advices

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

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

Social Sharing Optimization

capitecorpus.com

Open Graph data is detected on the main page of Capite Corpus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: