Website review, no card needed

chaabilld.ma logo

chaabilld.ma website review

Visit site (opens in a new tab)Reviewed 23 October 202629 issues · 75 checks

This review found 29 issues worth fixing on chaabilld.ma, 10 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.7 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.6 s
May 9, 20262.6 s
May 16, 20262.5 s
May 23, 20262.5 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
152 ms132 msMay 2Oct 17147 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026134 ms
May 9, 2026136 ms
May 16, 2026138 ms
Aug 1, 2026144 ms
Aug 8, 2026145 ms
Sep 19, 2026149 ms
Sep 26, 2026146 ms
Oct 3, 2026150 ms
Oct 10, 2026150 ms
Oct 17, 2026147 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of chaabilld.ma (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chaabilld.ma at 0.7 s0.7 s
  2. chaabilld.ma at 1.3 s1.3 s
  3. chaabilld.ma at 2.0 s2.0 s
  4. chaabilld.ma at 2.6 s2.6 s
  5. chaabilld.ma at 3.3 s3.3 s
  6. chaabilld.ma at 3.9 s3.9 s
  7. chaabilld.ma at 4.6 s4.6 s
  8. chaabilld.ma at 5.2 s5.2 s

Speed

7 to fix63
  • Reduce unused JavaScript

    1.2 s · 471 KiB

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

  • Mobile performance score: 63

    63/100

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

  • Render-blocking requests

    850 ms

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

  • Improve image delivery

    623 KiB

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

  • 8 long tasks on the main thread

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

  • Google Tag Manager adds 271 ms

    271 ms

    Google Tag Manager costs a phone 271 ms of main-thread work and 297 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.

  • Main-thread work: 2.3 s

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 298 KiB and 271 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 29 KiB

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

  • Legacy JavaScript

    13 KiB

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

1 checks passed
  • Server response: 164 ms

    164 ms

    Your server sent the HTML in 164 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LogoLLD”.

  • Time to Interactive: 8.5 s

    8.5 s

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

  • Total Blocking Time: 631 ms

    631 ms

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

  • Real-user TTFB: 817 ms

    817 ms

    Real visitors wait 817 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 4.7 s

    4.7 s

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

7 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 147 ms

    147 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Largest content (LCP) got 28% faster for real visitors

    -28%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.009

    0.009

    The layout barely moves while loading (CLS 0.009, good is under 0.1).

Images and page weight

2 to fix80
  • 4 images in older formats

    4 images (719 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.

  • 4 images far larger than shown

    465 KiB

    4 images are downloaded at several times the size a phone draws them, for example image at 1,376 px wide, shown at 254 px. Resized copies would save about 465 KiB.

  • About 0.5 g of CO₂ per visit

    0.53 g

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

2 checks passed
  • Page weight: 1.9 MB in 39 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 39 requests on a phone: scripts 928 KiB (18), images 732 KiB (9) and fonts 104 KiB (3). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9694
  • 4 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10087
  • Meta description is long (189 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

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

  • 50 internal links, 8 external

    The homepage links to 50 pages on chaabilld.ma and 8 external pages.

5 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Chaabi LLD | Location Longue Durée Maroc |LLD Maroc”.

  • Canonical URL set

    The canonical URL is http://www.chaabilld.ma/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://chaabilld.ma/fr/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, logo, description and contact details; url and sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (670 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.chaabilld.ma/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix83
  • 1 page points its canonical at the homepage

    https://www.chaabilld.ma/fr declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.chaabilld.ma/fr all use the title “Chaabi LLD | Location Longue Durée Maroc |LLD Maroc”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages with very little text

    https://www.chaabilld.ma/fr/demander-un-devis, https://www.chaabilld.ma/fr/demande-dinformation, https://www.chaabilld.ma/fr/reclamation, https://www.chaabilld.ma/fr/nous-connaitre and https://www.chaabilld.ma/fr/nos-offres 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.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    20 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix40
  • No call to action on the first screen

    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 calls to action

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

  • No social proof

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 581 words of copy

    The homepage carries about 581 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • No consent tool detected

    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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at chaabilld.ma, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Next.js
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on chaabilld.ma, including 13 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25