rtcdouala.cm website review

63 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).

16 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.6 s faster on a phone.

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

About 229 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts), adding 216 KiB and 147 ms of main-thread time.

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

Desktop scores 81 but mobile only 40. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

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

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

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

Visually, the page fills in at 6.1 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.

dgbonn.png weighs 569 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.9 MB in 71 requests on a phone: images 2.1 MB (30), scripts 496 KiB (19) and fonts 196 KiB (6). Under 2 MB keeps phones on slow connections fast.

11 images (1.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.

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 20 characters: “Accueil - RTC Douala”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 80 pages on rtcdouala.cm and 20 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://rtcdouala.cm/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.

Your homepage links to https://rtcdouala.cm/author/kaparan, https://rtcdouala.cm/2023/10/15/les-rtc-ladies-disent-stop-au-cancer-du-sein, https://rtcdouala.cm/2023/09/29/rex and https://rtcdouala.cm/2023/08/11/liste-des-beneficiaires-des-ristournes-commerciales-de-la-rtc-2022, which answer with an error. Visitors hit a dead end and search engines drop them.

https://rtcdouala.cm/blog-right-sidebar, https://rtcdouala.cm/grille-de-prix, https://rtcdouala.cm/vos-differents-formulaires, https://rtcdouala.cm/faq, https://rtcdouala.cm/equipement and https://rtcdouala.cm/nous-contacter and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://rtcdouala.cm/nous-contacter has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 22 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.

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

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