brauzz.fr website review

The page goes through 3 redirects before it starts loading, costing about 2.1 s. Link and advertise the final URL directly.

A phone's processor spends 7.0 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (planetb.care, Google Tag Manager and Clarity and others), adding 3.3 MB and 1.5 s of main-thread time.

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

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

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

planetb.care costs a phone 510 ms of main-thread work and 2.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.

Google Tag Manager costs a phone 393 ms of main-thread work and 520 KiB 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 425 KiB of JavaScript is downloaded but never used on this page.

The HTML itself could arrive about 350 ms sooner: redirects, a slow server response or missing compression delay everything after it.

43 KiB could be saved by minifying CSS.

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

Shopify costs a phone 108 ms of main-thread work and 394 KiB 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.

14 images could be 198 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

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

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

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

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

11 KiB could be saved by minifying JavaScript.

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.

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.

Your largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “TA ROUTINE QUOTIDIENNE,EN MIEUX”.

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

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

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

Real visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

Scripts block taps and scrolling for 275 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.

Your homepage downloads 4.4 MB in 373 requests on a phone: scripts 1.8 MB (148), fonts 795 KiB (24) and other files 691 KiB (95). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 9 characters: “BRAUZZ.FR”. 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.

There are 2 <h1> headlines (“Nettoyants clean & efficaces.” and “Nettoyants clean & efficaces.”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 39 pages on brauzz.fr and 4 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.

Your homepage links to /products/das-starter-set and /products/floor-cleaner, which answer with an error. Visitors hit a dead end and search engines drop them.

/products/waschstreifen-32-waschen and /products/feuilles-de-lessive all use the title “Feuilles de lessive (32 lavages)”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/all, /pages/de-brauzz-missie, /blogs/news, /pages/contact, /policies/privacy-policy and /policies/refund-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/products/waschstreifen-32-waschen and /products/feuilles-de-lessive use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /products/waschstreifen-32-waschen, whose canonical is /products/feuilles-de-lessive. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/contact has 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 13 pages linked from your homepage and read each the way a search engine does.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

Chrome logged issues while loading the page (“Cookie”).

2 links from your homepage to your own site are broken, for example https://brauzz.fr/products/das-starter-set (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

brauzz.fr is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

brauzz.fr 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.

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: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (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 37 cookies, 8 of them by other companies (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 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.