moyo.ua website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, TikTok and Google/Doubleclick Ads and others), adding 1.3 MB and 1.1 s of main-thread time.

About 1,004 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

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.

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

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

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

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

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Apple iPhone Duo 1”.

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

Your homepage downloads 4.7 MB in 217 requests on a phone: images 2.4 MB (92), scripts 1.8 MB (69) and fonts 250 KiB (10). Under 2 MB keeps phones on slow connections fast.

8 images (996 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.

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

Scrollable region must have keyboard access: 26 elements on the page fail this check, rated serious by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 141 characters, so Google will cut it off around 60: “Интернет-магазин Moyo.ua - магазин техники, электроники, инструментов, гаджетов в Украине…”.

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

No XML sitemap at https://www.moyo.ua/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 1,205 pages on moyo.ua and 62 external pages.

https://www.moyo.ua/portal_brand/apple_1 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.moyo.ua/ua/promo/novynky-apple, whose canonical is https://www.moyo.ua/ua. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.moyo.ua/status.html and https://www.moyo.ua/ua have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.moyo.ua/actions.html, https://www.moyo.ua/trade-in-obmen-staroy-tekhniki-na-novuyu.html, https://www.moyo.ua/propozytsiya-dlya-b2b-partneriv.html, https://www.moyo.ua/exchange.html and https://www.moyo.ua/status.html 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.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading '1')”.

17 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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: 56 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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