Tools & Wizards About Us
prelys-courtage.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

prelys-courtage.com

Courtier spécialiste en prêt immobilier, rachat de crédit et assurance-prêt

Page Load Speed

6 sec in total

First Response

693 ms

Resources Loaded

4.2 sec

Page Rendered

1.2 sec

prelys-courtage.com screenshot

About Website

Visit prelys-courtage.com now to see the best up-to-date Prelys Courtage content for France and also check out these interesting facts you probably never knew about prelys-courtage.com

Pour votre demande de prêt immobilier, de rachat de crédit immobilier et d'assurance-crédit, contactez-nous au 09 80 80 04 01 et obtenez le meilleur taux en moins de 4 semaines...

Visit prelys-courtage.com

Key Findings

We analyzed Prelys-courtage.com page load time and found that the first response time was 693 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

prelys-courtage.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value1,800 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.289

41/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

www.prelys-courtage.com

693 ms

css

40 ms

style.min.css

242 ms

cff-style.min.css

398 ms

public-main.css

326 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 87% of them (76 requests) were addressed to the original Prelys-courtage.com, 5% (4 requests) were made to Api.cr.econnect-prelys.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Api.cr.econnect-prelys.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 591.1 kB (30%)

Content Size

2.0 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Prelys-courtage.com main page is 2.0 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 514.2 kB

  • Original 592.5 kB
  • After minification 588.9 kB
  • After compression 78.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 514.2 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 76.9 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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. Prelys Courtage images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 25.9 kB
  • After minification 25.9 kB
  • After compression 25.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. Prelys-courtage.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (29%)

Requests Now

84

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.prelys-courtage.com

www.prelys-courtage.com

693 ms

css

css

40 ms

style.min.css

style.min.css

242 ms

cff-style.min.css

cff-style.min.css

398 ms

public-main.css

public-main.css

326 ms

bootstrap.min.css

bootstrap.min.css

408 ms

all.css

all.css

43 ms

js_composer.min.css

js_composer.min.css

495 ms

pix-essentials-style-2.css

pix-essentials-style-2.css

415 ms

staff-list.css

staff-list.css

333 ms

v4-shims.css

v4-shims.css

55 ms

jquery.min.js

jquery.min.js

415 ms

public-main.js

public-main.js

435 ms

carousel-2.min.css

carousel-2.min.css

317 ms

circles.min.css

circles.min.css

324 ms

base.min.css

base.min.css

330 ms

cff-scripts.min.js

cff-scripts.min.js

518 ms

popper.min.js

popper.min.js

519 ms

bootstrap.min.js

bootstrap.min.js

532 ms

core.min.js

core.min.js

530 ms

essentials-5.min.js

essentials-5.min.js

530 ms

index.bundle-4.js

index.bundle-4.js

530 ms

js_composer_front.min.js

js_composer_front.min.js

530 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

529 ms

lazyload.min.js

lazyload.min.js

684 ms

gtm.js

gtm.js

322 ms

ratio

ratio

1161 ms

ratio

ratio

1162 ms

ratio

ratio

1157 ms

ratio

ratio

1154 ms

logo-white-S.png

logo-white-S.png

264 ms

5-2.png

5-2.png

262 ms

1-2.png

1-2.png

262 ms

3-2.png

3-2.png

264 ms

2-2.png

2-2.png

264 ms

google_avatar.png

google_avatar.png

344 ms

logo-2-0.png

logo-2-0.png

681 ms

Banner-2.png

Banner-2.png

576 ms

18-1.png

18-1.png

642 ms

13.png

13.png

575 ms

17.png

17.png

576 ms

16.png

16.png

573 ms

img-st-pierre.jpg

img-st-pierre.jpg

793 ms

15.png

15.png

708 ms

6.png

6.png

640 ms

14.png

14.png

643 ms

8.png

8.png

641 ms

5-1.png

5-1.png

706 ms

7.png

7.png

768 ms

19.png

19.png

858 ms

nantes.png

nantes.png

882 ms

2-460x460.png

2-460x460.png

808 ms

5-460x460.png

5-460x460.png

807 ms

4-460x460.png

4-460x460.png

842 ms

3-460x460.png

3-460x460.png

872 ms

Glassdoor.png

Glassdoor.png

944 ms

lbp-2.webp

lbp-2.webp

885 ms

societe-generale.webp

societe-generale.webp

920 ms

LCL.png

LCL.png

937 ms

caisse-epargne.jpg

caisse-epargne.jpg

953 ms

credit-agricole.png

credit-agricole.png

963 ms

Credit-Agiricole-Run.webp

Credit-Agiricole-Run.webp

964 ms

logo-cfcal.webp

logo-cfcal.webp

998 ms

credit-mutuel1.webp

credit-mutuel1.webp

1016 ms

sofider.webp

sofider.webp

1023 ms

logo-cepac.jpg

logo-cepac.jpg

1033 ms

bnp.png

bnp.png

1043 ms

logo-creditlift.webp

logo-creditlift.webp

1043 ms

bred.webp

bred.webp

1076 ms

bfc-3.webp

bfc-3.webp

1095 ms

banque-populaire.jpg

banque-populaire.jpg

1100 ms

2.webp

2.webp

1114 ms

Voir.png

Voir.png

553 ms

allianz.jpg

allianz.jpg

555 ms

April.png

April.png

585 ms

axa.jpg

axa.jpg

606 ms

cardif.jpg

cardif.jpg

554 ms

css2

css2

72 ms

logo-afi-esca.jpg

logo-afi-esca.jpg

559 ms

logo-cnp.jpg

logo-cnp.jpg

564 ms

logo-generalli.jpg

logo-generalli.jpg

566 ms

logo-swisslife.jpg

logo-swisslife.jpg

536 ms

logo-utwin.jpg

logo-utwin.jpg

553 ms

metlife.jpg

metlife.jpg

496 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

43 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

44 ms

cncef.png

cncef.png

491 ms

Accessibility Review

prelys-courtage.com accessibility score

91

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

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.

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

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

prelys-courtage.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

prelys-courtage.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 Prelys-courtage.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 Prelys-courtage.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

prelys-courtage.com

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