maisonpyramide.com website review

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

5 third-party services load with your homepage (Google Tag Manager, Google Analytics and datocms.com and others), adding 47.8 MB and 97 ms of main-thread time.

DatoCMS costs a phone 0 ms of main-thread work and 44.6 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 68 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

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

About 95 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

Cloudinary costs a phone 0 ms of main-thread work and 3.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 27 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.

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

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Visually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 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.

Your homepage downloads 60.6 MB in 71 requests on a phone: images 53.9 MB (46), media 6.0 MB (1) and scripts 339 KiB (12). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

5 images (3.0 MB) 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.

2 images are downloaded at several times the size a phone draws them, for example client1.1.52106e5a.jpeg at 1,000 px wide, shown at 155 px. Resized copies would save about 139 KiB.

2 images further down the page (160 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 17.17 g of CO₂e: 2060.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 images have no alt text, which hurts accessibility and image search.

[aria-*] attributes do not have valid values (1 element).

1 button has no accessible name, so screen readers announce just “button”.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is only 15 characters: “Maison Pyramide”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 15 characters: “Maison Pyramide”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Our Expertise” and “<img src="https://www.maisonpyramide.com/_next/static/media/logowhite.beade208.…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.maisonpyramide.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at maisonpyramide.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 16 pages on maisonpyramide.com and 10 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.maisonpyramide.com/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.

/, https://www.maisonpyramide.com/services, https://www.maisonpyramide.com/expertise, https://www.maisonpyramide.com/clients, https://www.maisonpyramide.com/group and https://www.maisonpyramide.com/news and 1 other all use the title “Maison Pyramide”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.maisonpyramide.com/services, https://www.maisonpyramide.com/expertise, https://www.maisonpyramide.com/clients, https://www.maisonpyramide.com/group, https://www.maisonpyramide.com/news and https://www.maisonpyramide.com/contact use the same meta description. A description written for each page earns more clicks.

https://www.maisonpyramide.com/services, https://www.maisonpyramide.com/expertise, https://www.maisonpyramide.com/clients, https://www.maisonpyramide.com/news and https://www.maisonpyramide.com/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

The homepage has only about 208 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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