leoceramika.com website review

5 images could be 662 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

Your mobile performance score is 71 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 956 KiB and 707 ms of main-thread time.

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

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

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

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

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

31 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Гаряча пропозиція плитка жовтень - Зображення”.

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

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

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

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

Your homepage downloads 2.6 MB in 88 requests on a phone: images 1.2 MB (39), scripts 1.0 MB (21) and fonts 180 KiB (7). Under 2 MB keeps phones on slow connections fast.

300.jpg 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 is downloaded at several times the size a phone draws it, for example logo-leoceramica-int-new.png at 1,359 px wide, shown at 191 px. Resized copies would save about 47 KiB.

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

9 elements use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

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.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

Your title is 84 characters, so Google will cut it off around 60: “Інтернет-магазин сантехніки, плитки, освітлення, підлогового покриття - Лео Кераміка”.

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

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

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

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

The homepage links to 338 pages on leoceramika.com and 8 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.

There is no https://leoceramika.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://leoceramika.com/about, https://leoceramika.com/outlet/keramichna-plytka_300, https://leoceramika.com/outlet/santekhnika_200, https://leoceramika.com/outlet/pidlogovi-pokryttja_100, https://leoceramika.com/outlet/osvitlennja_500 and https://leoceramika.com/outlet/elektrotovary_1100 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://leoceramika.com/about, https://leoceramika.com/outlet/keramichna-plytka_300, https://leoceramika.com/outlet/santekhnika_200, https://leoceramika.com/outlet/osvitlennja_500, https://leoceramika.com/catalog/keramichna-plytka_300 and https://leoceramika.com/catalog/vanna-kimnata_301 have no <h1> headline, so visitors and search engines get no clear main topic.

https://leoceramika.com/payments-and-deliveries, https://leoceramika.com/news and https://leoceramika.com/contacts 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.

https://leoceramika.com/payments-and-deliveries, https://leoceramika.com/news, https://leoceramika.com/news/category/akciyi, https://leoceramika.com/outlet/santekhnika_200, https://leoceramika.com/outlet/pidlogovi-pokryttja_100 and https://leoceramika.com/outlet/osvitlennja_500 and 1 other took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static.salesdrive.me/chat-widget/assets/css/widget.css?498035' from origin 'https:…”.

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 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 21 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.

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