terreal.com website review

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

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

About 1.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.2 s faster on a phone.

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

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

The page has 2,347 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 third-party services load with your homepage (Google Tag Manager, Cookiebot and Adobe Tag Manager and others), adding 468 KiB and 287 ms of main-thread time.

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

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

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

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

Your largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Intégration de la marque Terreal”.

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

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

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Scripts block taps and scrolling for 228 ms in total while the page loads. Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 31 requests on a phone: scripts 1.6 MB (15), stylesheets 1.0 MB (2) and fonts 604 KiB (5). Under 2 MB keeps phones on slow connections fast.

2 images (94 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.

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

6 buttons have no accessible name, so screen readers announce just “button”.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is 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: 17 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

21 visible links have no text or label, so screen readers cannot say where they go.

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

Your title is 127 characters, so Google will cut it off around 60: “wienerberger, leader mondial de la terre cuite : mur, toiture, façade, solaire, accessoir…”.

Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: missing name”.

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

7 links have no real href, so search engines can't follow them.

The homepage links to 362 pages on terreal.com and 45 external pages.

Your Organization JSON-LD is missing name, 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 https://www.wienerberger.fr/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.wienerberger.fr/Produits/facade/terca-et-terreal-brique-apparente-terre-cuite/moteur-de-recherche-briques-et-plaquettes.html and https://www.wienerberger.fr/Produits/toiture/moteur-de-recherche-toiture.html have no <title>, so Google invents the link text in results.

https://www.wienerberger.fr/Produits/facade/terca-et-terreal-brique-apparente-terre-cuite/moteur-de-recherche-briques-et-plaquettes.html and https://www.wienerberger.fr/Produits/toiture/moteur-de-recherche-toiture.html have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.wienerberger.fr/Produits/Facade/Rechercher-un-produit, whose canonical is https://www.wienerberger.fr/Produits/facade/terca-et-terreal-brique-apparente-terre-cuite/collections-briques-de-parement-et-plaquettes.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 errors were logged to the browser console while the page loaded, for example “md is not defined”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 851 words of visible text.

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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