chargeurs.com website review

43 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.

89 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

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

About 24 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

3 third-party services load with your homepage (JSDelivr CDN, Google Fonts and axept.io), adding 150 KiB and 78 ms of main-thread time.

5 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

4 images have no width and height attributes, so the layout jumps as each one loads.

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.

10 images (592 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

6 images are downloaded at several times the size a phone draws them, for example marque-museum-studio-nuit.png at 998 px wide, shown at 198 px. Resized copies would save about 224 KiB.

2 images further down the page (112 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 12 elements on the page fail this check, rated minor by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

The homepage links to 90 pages on chargeurs.com and 4 external pages.

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.

/nos-activites/chargeurs-pcc is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/replay-retrouvez-lassemblee-generale-extraordinaire-du-20-octobre-2026-en-video, /compte-rendu-de-lassemblee-generale-extraordinaire-du-20-octobre-2026, /mise-a-disposition-des-documents-preparatoires-a-lassemblee-generale-extraordinaire-du-20-octobre-2026, /avis-de-reunion-assemblee-generale-extraordinaire-20-octobre-2026 and /mise-a-disposition-du-rapport-financier-semestriel-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

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

14 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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

belgranogroup.com was registered in Jun 2026 through Namebay SAM. Spam filters and search engines treat brand-new domains more cautiously, so expect email and rankings to take a few months to settle.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,075 words of visible text.

DMARC is set to p=none, so mail pretending to be chargeurs.com is still delivered. Reports are on, so moving to quarantine is the next step.

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.

Opening the homepage sets 4 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.