fcpartner.com website review

Your mobile performance score is 89. Pages that score under 90 lose visitors before the first paint.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 213 KiB and 103 ms of main-thread time.

About 69 KiB of JavaScript is downloaded but never used on this page.

2 long tasks block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.

39 files are served with short cache lifetimes, so returning visitors download them again (37 KiB).

2 images could be 14 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Visually, the page fills in at 13.2 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 4.0 s. Good is under 3.8 s.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

By the Sustainable Web Design model, a visit to your homepage emits about 0.17 g of CO₂e: 20.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

3 tap targets are too small or too close together to hit reliably with a finger.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

The homepage links to 36 pages on fcpartner.com and 2 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/mentions-legales and /politique-de-confidentialite have no meta description, so Google writes the search snippet from whatever text it finds.

/administration-des-fonds, /gestion-de-portefeuille, /valorisation, /services-aux-investisseurs, /monitoring-de-la-performance and /nos-services and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/administration-des-fonds, /gestion-de-portefeuille, /valorisation, /services-aux-investisseurs, /monitoring-de-la-performance and /nos-services and 3 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fcpartner.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

fcpartner.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 7 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 739 words of visible text.

DMARC is set to p=none, so mail pretending to be fcpartner.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.