tbwadjaz.com website review

8 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Hubspot and Google Analytics and others), adding 283 KiB and 119 ms of main-thread time.

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

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

Polyfills for old browsers add 10 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.

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nous créons, protégeons et enrichissons la réputation de vo…”.

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

The page becomes fully interactive after 7.0 s. Good is under 3.8 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 2.5 MB in 70 requests on a phone: images 1.9 MB (35), scripts 461 KiB (17) and fonts 83 KiB (1). Under 2 MB keeps phones on slow connections fast.

inauguration-geat_thumb_slider.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example vertical-white-eps-logo.png at 1,355 px wide, shown at 120 px. Resized copies would save about 124 KiB.

4 images (412 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 0.72 g of CO₂e: 86.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Interactive controls must not be nested: 25 elements on the page fail this check, rated serious by axe-core.

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

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

All page content should be contained by landmarks: 7 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.

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

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

Your title is only 10 characters: “TBWA\ DJAZ”. 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 4 <h1> headlines (“Nous créons, protégeons et enrichissons la réputa…”, “Projets” and “Expertise”). 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 XML sitemap at https://www.tbwadjaz.com/sitemap-index.xml, so Google discovers your pages only by following links.

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 44 pages on tbwadjaz.com and 7 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://tbwadjaz.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.

/ and https://tbwadjaz.com/carriere all use the title “TBWA\ DJAZ”. Search engines can't tell which page to show for a search, so each competes with the others.

https://tbwadjaz.com/services, https://tbwadjaz.com/contact, https://tbwadjaz.com/projects/2021-07-07_%E2%80%9Ce-cigarette-summit%E2%80%9D, https://tbwadjaz.com/projects/2020-12-23_ev%C3%A8nements-en-ligne, https://tbwadjaz.com/projects/2020-07-20_henkel-alg%C3%A9rie-sengage-dans-la-lutte-contre-la-covid-19 and https://tbwadjaz.com/projects/2020-08-16_gelphore-nouvelle-identit%C3%A9-visuelle 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 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.

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

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

Opening the homepage sets 4 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.