mova.tech website review

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.0 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 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

26 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Klaviyo and others), adding 1.7 MB and 1.5 s of main-thread time.

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

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

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

ZenDesk costs a phone 146 ms of main-thread work and 354 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.

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

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.

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.

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

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

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

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

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

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

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-31, real Chrome visitors' tap response (inp) went from 176 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 129.8 MB in 443 requests on a phone: media 114.1 MB (38), images 12.4 MB (160) and scripts 2.2 MB (75). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example CES-Blog1.png at 2,880 px wide, shown at 265 px. Resized copies would save about 131 KiB.

1 image (142 KiB) is 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.

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

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

205 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

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

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

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

Your title is 71 characters, so Google will cut it off around 60: “MOVA: Innovative Smart Living Solutions for a Better Life – MOVA-GLOBAL”.

28 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

Your <h1> is empty.

The homepage links to 315 pages on mova.tech and 5 external pages.

/collections/all, /pages/return-and-refund-policy, /pages/contact-us, /collections/robot-lawn-mower, /pages/user-manuals-and-faqs and /collections/robot-vacuum have no meta description, so Google writes the search snippet from whatever text it finds.

/products/mova-1000-robot-lawn-mower and /products/mova-600-and-1000-robot-lawn-mower use the same meta description. A description written for each page earns more clicks.

/collections/all, /products/mova-1000-robot-lawn-mower, /products/mova-v50-ultra-robot-vacuum, /pages/return-and-refund-policy, /pages/contact-us and /collections/robot-lawn-mower and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

mova.tech's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

DMARC is set to p=none, so mail pretending to be mova.tech is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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