zouarigroup.com website review

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

Your mobile performance score is 41 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

1 image could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

2 third-party services load with your homepage (Google Maps and Google Fonts), adding 335 KiB and 107 ms of main-thread time.

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

About 43 KiB of CSS is downloaded but never applied on this page.

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

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

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

The layout shifts by 0.953 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “L’Esprit d’entreprise qui anime le Groupe nous permet d’exp…”. Most of its time is element render delay (7.4 s).

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

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

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

Your homepage downloads 7.4 MB in 48 requests on a phone: images 6.9 MB (28), scripts 325 KiB (6) and fonts 174 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

All page content should be contained by landmarks: 3 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 viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

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

Your title is only 23 characters: “Accueil | Groupe Zouari”. 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.

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 http://zouarigroup.com/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 50 pages on zouarigroup.com and 1 external page.

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.

/, https://zouarigroup.com/fr and https://zouarigroup.com/fr/accueil all use the title “Accueil | Groupe Zouari”. Search engines can't tell which page to show for a search, so each competes with the others.

https://zouarigroup.com/fr, https://zouarigroup.com/fr/accueil, https://zouarigroup.com/fr/notre-histoire, https://zouarigroup.com/fr/nos-m%C3%A9tiers, https://zouarigroup.com/fr/concessionnaire-automobile and https://zouarigroup.com/fr/concessionnaire-bus and 9 others 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://zouarigroup.com/fr, whose canonical is https://zouarigroup.com/fr/accueil. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://zouarigroup.com/fr/nos-m%C3%A9tiers, https://zouarigroup.com/fr/concessionnaire-camions, https://zouarigroup.com/fr/industrie-automobile and https://zouarigroup.com/fr/les-groupes-%C3%A9lectrog%C3%A8nes 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.

https://zouarigroup.com/fr, https://zouarigroup.com/fr/accueil, https://zouarigroup.com/fr/notre-histoire, https://zouarigroup.com/fr/nos-m%C3%A9tiers, https://zouarigroup.com/fr/concessionnaire-automobile and https://zouarigroup.com/fr/concessionnaire-bus and 9 others took over 3 s to send their HTML from our server.

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

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

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: 1 trust badge. 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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Opening the homepage sets 1 cookie (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.