zuty.bg website review

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

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

8 third-party services load with your homepage (Google Tag Manager, loox.io and TikTok and others), adding 983 KiB and 845 ms of main-thread time.

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

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

74 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.5 MB in 261 requests on a phone: images 2.4 MB (65), scripts 1,007 KiB (69) and other files 689 KiB (100). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example galerie-large-13.jpg at 1,500 px wide, shown at 265 px. Resized copies would save about 693 KiB.

21 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (243 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 1.29 g of CO₂e: 154.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

Your title is 80 characters, so Google will cut it off around 60: “Комплекти за рисуване по номера - създавайте зашеметяващи произведения – ZUTY BG”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Най-големият производител на рисунки по номера, д…” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 239 pages on zuty.bg 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.

https://zuty.bg/collections/%D0%BA%D0%BE%D0%BB%D0%B5%D0%B4%D0%BD%D0%B8-%D1%85%D0%B8%D1%82%D0%BE%D0%B2%D0%B5, https://zuty.bg/pages/%D0%9F%D0%BE%D0%BF%D1%83%D0%BB%D1%8F%D1%80%D0%BD%D0%B8, https://zuty.bg/collections/%D1%80%D0%B8%D1%81%D1%83%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BF%D0%BE-%D0%BD%D0%BE%D0%BC%D0%B5%D1%80%D0%B0-%D0%B2%D1%81%D0%B8%D1%87%D0%BA%D0%B8-%D0%BC%D0%BE%D1%82%D0%B8%D0%B2%D0%B8, https://zuty.bg/collections/%D0%B1%D0%B5%D1%81%D1%82%D1%81%D0%B5%D0%BB%D1%8A%D1%80%D0%B8-1, https://zuty.bg/pages/%D1%80%D0%B8%D1%81%D1%83%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BF%D0%BE-%D0%BD%D0%BE%D0%BC%D0%B5%D1%80%D0%B0-%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8 and https://zuty.bg/products/%D1%80%D0%B8%D1%81%D1%83%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BF%D0%BE-%D0%BD%D0%BE%D0%BC%D0%B5%D1%80%D0%B0-%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%B0-%D0%BF%D0%BE-%D1%81%D0%BE%D0%B1%D1%81%D1%82%D0%B2%D0%B5%D0%BD%D0%B0-%D1%84%D0%BE%D1%82%D0%BE%D0%B3%D1%80%D0%B0%D1%84%D0%B8%D1%8F and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://zuty.bg/collections/%D0%BA%D0%BE%D0%BB%D0%B5%D0%B4%D0%BD%D0%B8-%D1%85%D0%B8%D1%82%D0%BE%D0%B2%D0%B5, whose canonical is https://zuty.bg/collections/%d0%ba%d0%be%d0%bb%d0%b5%d0%b4%d0%bd%d0%b8-%d1%85%d0%b8%d1%82%d0%be%d0%b2%d0%b5. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://zuty.bg/pages/%D0%9F%D0%BE%D0%BF%D1%83%D0%BB%D1%8F%D1%80%D0%BD%D0%B8, https://zuty.bg/pages/%D1%80%D0%B8%D1%81%D1%83%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BF%D0%BE-%D0%BD%D0%BE%D0%BC%D0%B5%D1%80%D0%B0-%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8 and https://zuty.bg/collections/%D1%80%D0%B8%D1%81%D1%83%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BF%D0%BE-%D0%BD%D0%BE%D0%BC%D0%B5%D1%80%D0%B0-%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%B0-%D0%BF%D0%BE-%D1%81%D0%BE%D0%B1%D1%81%D1%82%D0%B2%D0%B5%D0%BD%D0%B0-%D1%84%D0%BE%D1%82%D0%BE%D0%B3%D1%80%D0%B0%D1%84%D0%B8%D1%8F-%D0%B1%D0%B0%D0%B7%D0%B8%D1%80%D0%B0%D0%BD%D0%B8-%D0%BD%D0%B0-ai-%D1%81%D1%82%D0%B8%D0%BB%D0%BE%D0%B2%D0%B5 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 97 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97037096&tm=gtm002&Ver=2&mid=cc042e1e-94d4-46a4-9df7-cc62132658ad&bo=1&sid=acc72c30dc7b11f194cbf7df253fa482&vid=acc73520dc7b11f1bb882143fa82fd6c&vids=1&msclkid=N&pi=91.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://apps3.omegatheme.com/cookies-notification/client/save-cookies.php' from origin 'ht…”.

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.

The homepage has only about 86 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The page uses urgency cues (a countdown or limited-time wording).

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