mnt-sa.com website review

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

salla.network costs a phone 1.1 s of main-thread work and 4.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (salla.network, Google Tag Manager and Facebook and others), adding 5.7 MB and 2.6 s of main-thread time.

About 627 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 510 ms faster on a phone.

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

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

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

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

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

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

5 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 23.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Central Water Heater (AO Smith) 80 Gallon”.

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

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

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

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

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

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

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

Your homepage downloads 10.5 MB in 328 requests on a phone: images 7.1 MB (128), scripts 2.1 MB (114) and media 674 KiB (1). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example 2246e9c8-90d1-4967-9322-42114343ac66-original.webp at 1,440 px wide, shown at 370 px. Resized copies would save about 781 KiB.

1fa34390-190f-42ee-9c81-110109b33f68-original.webp 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 further down the page (109 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.98 g of CO₂e: 357.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (23 elements).

The homepage links to 7 pages on mnt-sa.com and 0 external pages.

A phone browser shows 473 words, but the HTML your server sends has only 77. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your homepage links to https://mnt-sa.com/en/-/c793535897, https://mnt-sa.com/en/-/c2032829594 and https://mnt-sa.com/en/-/c308490215, which answer with an error. Visitors hit a dead end and search engines drop them.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mnt-sa.com/en/-/c319576551, whose canonical is https://mnt-sa.com/en/irrigation-systems-offers/c319576551. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mnt-sa.com/en/-/c319576551 has 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 4 pages linked from your homepage and read each the way a search engine does.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increa…”.

Chrome logged issues while loading the page (“Cookie”).

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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