jmla.ma website review

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

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

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

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

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

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

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

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

33 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 6 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

6 KiB could be saved by minifying CSS.

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

3 third-party services load with your homepage (Bootstrap CDN, Cloudflare CDN and Google Fonts), adding 109 KiB and 3 ms of main-thread time.

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

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.

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

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner Image”. Most of its time is resource load delay (3.9 s).

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

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

The first text or image appears after 2.9 s on a phone. Good is under 1.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.

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

155 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

Headings should not be empty: 13 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is only 5 characters: “zCart”. 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 XML sitemap at https://jmla.ma/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 1,758 pages on jmla.ma and 6 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://jmla.ma/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.

/, https://jmla.ma/categories and https://jmla.ma/categorygrp/softwares all use the title “zCart”. Search engines can't tell which page to show for a search, so each competes with the others.

https://jmla.ma/categories and https://jmla.ma/categorygrp/softwares use the same meta description. A description written for each page earns more clicks.

https://jmla.ma/categories and https://jmla.ma/categorygrp/softwares have no <h1> headline, so visitors and search engines get no clear main topic.

https://jmla.ma/categorygrp/softwares took over 3 s to send its HTML from our server.

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

10 images failed to load on a phone, for example https://jmla.ma/image/images/63fde8b7bd656.webp?p=logo.

17 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

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: 4 trust badges. 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.

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

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