mafatlals.com website review

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

About 1.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.5 s faster on a phone.

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

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

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

19 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 565 ms on a phone.

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

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

Your server takes 665 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

7 third-party services load with your homepage (Facebook, Google Tag Manager and Google/Doubleclick Ads and others), adding 510 KiB and 176 ms of main-thread time.

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

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

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.

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

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

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

Your largest element takes 26.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Business Excellence Without Compromise Our mission is to pr…”.

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

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

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

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

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

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

Your homepage downloads 9.8 MB in 112 requests on a phone: images 6.0 MB (30), scripts 1.9 MB (52) and stylesheets 1.3 MB (13). Under 2 MB keeps phones on slow connections fast.

Hygiene-Products-baby-2.webp weighs 3.7 MB. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example Hygiene-Products-baby-2.webp at 2,560 px wide, shown at 437 px. Resized copies would save about 3.5 MB.

1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

Elements with role="none" or role="presentation" have conflicts (8 elements).

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 104 pages on mafatlals.com and 16 external pages.

There is no https://www.mafatlals.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.

https://www.mafatlals.com/media-kit and https://www.mafatlals.com/in-the-news use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 20 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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 425 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 11 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.